feat: status precedence — explicit sticky, task-auto yields (0.16.1)#84
Merged
Conversation
… yields (0.16.1) "That narrative status is really nice — will we still see it?" Yes, and now guaranteed: an explicit `register --status "..."` is marked non-auto and STICKS — the task list (via --status-auto from the TaskCreated/TaskCompleted hook) fills in only when no explicit status stands, and updates among other autos. So rich human-readable statuses you declare survive task churn; terse task subjects are the automatic floor when you haven't declared. Heartbeats preserve either. AgentRecord gains statusAuto; register takes a statusAuto arg; CLI gets --status-auto (the task hook uses it). Test: explicit survives a TaskCreated; autos still update each other. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explicit register --status is sticky (statusAuto=false); task-list auto-status (--status-auto) fills only when no explicit one stands and updates among autos. Rich declared statuses survive task churn; task subjects are the automatic floor. Tested.