feat: branch-default statuses — board never blank (0.15.0)#82
Merged
Conversation
…15.0) Field truth: every record on the ctx bus had NO status field — even today's 0.15-era sessions. The nudge only asks agents to declare, and (same lesson as registration) advisory loses to the user's actual task. Two-sided fix — the "Both" the user chose: - Mechanical default: the session-start and digest hooks set status to "on <branch>" when the agent has none (or only a prior branch default), NEVER clobbering a real declared status; it follows branch switches. Non-prompt, always-populated — the live board now shows where every session is even before anyone declares. Uses symbolic-ref so unborn branches work too. - Stronger order: session-start makes declaring a real status the agent's explicit FIRST action, and the digest nudge now also fires to upgrade a branch default to a real task. Test: fresh session → "on feat-auth"; a declared status survives later hooks and branch switches. 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.
Every ctx-bus record had no status (advisory nudge ignored, same as the old register problem). Fix (user chose Both): hooks set a mechanical 'on ' default that never clobbers a real declaration + a stronger first-action order to upgrade it. Board shows where every session is immediately. Tested: default set, real status preserved across hooks and branch switches.