fix(cli/docs): close CLI↔doc friction surfaced by a playbook dogfood#446
Merged
Conversation
A walkthrough of guild→gate→agora→ctx→devil (and 'what if guild is the entry point?') surfaced gaps between the docs and the running CLI. Fixed: - gate issues promote gains --format json|text (was a write verb with no --format — a schema-as-contract gap, principle 10). Shares the unified write envelope via emitWriteResponse; resolved-issue id rides in message (records-outlive-writers). Decided in agora play promote-format-impl with devil (shape integrity) + noir (principle 04) review. - guild --help now discloses the four passages with --help pointers and a newcomer path to gate (orientation-disclosure, principle 09). guild was member-mgmt-only, leaving guild-entry agents with no path to the passages. - playbook: gate review --comment → --note (--comment is a deprecated alias). - playbook/AGENT.md: 'solo profile' → 'standard' (valid profiles are standard|swarm; 'solo' is the situation, not a config value). - playbook X2: ctx chain only walks links between ctx facts; a breadcrumb naming an agora/gate id is found by its tag, not by chain (was overclaimed). Tests: issuePromoteFormat (envelope + back-compat), guildHelpPassages. Full suite 1865/1865 green. Note: the originally-suspected 'promote --reason required' was a misread (it's optional) — dropped, not a bug.
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
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.
What
A walkthrough of
guild → gate → agora → ctx → devil(and "what if the entry point isguild, notgate?") surfaced gaps between the docs and the running CLI. Each fix was decided on the substrate (gate request + agora play + principle-grounded review), not by desk reasoning.Changes (with the principle each is grounded in)
gate issues promotegains--format json|text— it was a write verb with no--format, so an agent couldn't receive the created request id as JSON. That's a schema-as-contract gap (principle 10): every other write verb returns the unifiedok/id/state/message/suggested_nextenvelope. promote now shares it viaemitWriteResponse; the resolved-issue id rides inmessageso both ids stay greppable (records-outlive-writers, principle 04). Text output unchanged; no--format→ text (back-compatible). Decided in agora playpromote-format-implwith devil (shape integrity) + noir (principle 04).guild --helpdiscloses the four passages — guild was member-management-only, leaving a guild-entry agent with no in-CLI path to the passages where work happens (orientation-disclosure, principle 09). Now names gate/agora/devil/ctx with<passage> --helppointers and a newcomer path togate --help+ AGENT.md.gate review --comment→--note(--commentis a deprecated alias).standard | swarm; "solo" is the situation, not a config value.ctx chainonly walks links between ctx facts; a breadcrumb naming anagora/gateid is found by its tag, not bychain(was overclaimed in the prior chain PR — corrected per principle 03 legibility-costs: don't pad the docs).Not a bug (dropped after schema-first check)
The walkthrough first suspected "
gate issues promoterequires--reason". Verified on the real CLI:--reasonis optional (the handler defaults it). The original error was a misreadunknown flag: --format. Dropped — the playbook's[--reason]was already correct.Filed as follow-up issues (different layer)
ctx chaincross-passage walk (#5b), play-id game collision needing--game(#9),gate voicesvs agora-move channel boundary docs (#10).Verification
node tests/run.mjs, exit 0).issuePromoteFormat(envelope keys + back-compat),guildHelpPassages(passage disclosure + member-mgmt retained).🤖 Generated with Claude Code