Make intent precedence state aware #40
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/zara!40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/zara-007-intent-precedence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What changed
resolve/4with explicit passive, conversation, and dictation statestop,end,hello,search, andfindKB routespending(...)results for missing open, text, and schedule slotsWhy
Duplicate Prolog clauses relied on source order, and wake mode treated compound Python skill terms as implementation-dependent strings. State controls and missing arguments could therefore resolve incorrectly or falsely execute.
Impact
Stop/end behavior follows interaction state, todo search cannot be shadowed by web search, every registered Python skill can cross the wake boundary, and incomplete commands return clarification instead of execution.
Validation
scripts/test-*.sht/fixtures/intents.expectedCloses #8