Repository navigation
Session Handoff [auto-3638]: Split the Prompt-Command Rule So a Session-Prompt Command Never Sits in a Blocking Dialog (#3638) #3645
Description
Next steps, in priority order
- Fix A Command the User Runs at the Session Prompt Cannot Sit in a Dialog That Blocks the Prompt #3638. Split the
GOVERNANCE.md"Communicating with the User" bullet "Put a command the user must run in the question's own text" by where the command runs. A command the user runs somewhere else, such as a password prompt in another terminal, stays in the question text as now. A command the user runs at this session's own prompt goes in a plain message as a fenced block, and the turn ends with no dialog open. The agent then checks the result on the user's next message. Reconcile the change with the neighboring bullet "Ask every question through the interface's prompt, never in prose", so the two do not contradict each other. Regenerate theagent-conductandsession-handoffinclude copies withscripts/build_dist.py. Done looks like a pull request intodevelopcarryingCloses on promotion: #3638, merged as far as the run's scope allows.
External blockers
None known at pick time.
Internal dependencies
None. This lane holds one issue.
State
- No branch, worktree, or pull request exists yet for this lane. Work on
feature/auto-3638, based ondevelop. - The rule text lives in
GOVERNANCE.md, and generated copies sit in theagent-conductandsession-handoffskills under.agents/skills/,.github/skills/, and.claude-plugin/. Re-derive this with a search before editing. - The change edits carried canonical content, so it is worked at the
frontiertier.
The parked decision queue
Count: 0.
What the last round did
The unattended picker opened this lane from the open backlog. No work has been done on it.
What not to repeat
Nothing yet.
New learnings
Nothing yet.
Activity
ptr727 commentedon Oct 30, 2026
Outcome
Done at scope
develop.developas d15cbf8. It splits theGOVERNANCE.md"Communicating with the User" command bullet by where the command runs. A command the session's input line cannot run or cannot hold stays in the question text. A command run at the input line, a!line on Claude Code, goes in a plain message that ends the turn with no interactive prompt open. The neighboring prompt bullets and thesession-handoffskill's own steps 4 and 5 name that turn as their exception, and theagent-conductandsession-handoffinclude copies were regenerated.develop -> mainpromotion merges, carryingCloses on promotion: #3638.origin/develop.Learned
The local strict-review pass on carried rule text kept raising new
introducedfindings against each previous round's fix wording, across five pushes. Every one was fixed except the last, which was declined with evidence in the pull request body. Copilot's three findings on the first head were all answered and resolved.