docs: document input-propagation fail-loud behavior and add Publishing section#93
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
…g section - Expand the "Input propagation" gotcha in catalog/agent-team/README.md to describe the concrete guard introduced in d688265: unresolved-literal detection, the exact state:blocked + comment written, and manual re-dispatch recovery steps. - Add ## Publishing section to README.md to fix a broken internal link in CONTRIBUTING.md (line 115 has pointed to README.md#publishing since the initial commit, but the section never existed). Co-Authored-By: Claude Sonnet 4.6 <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
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 changed
Two documentation gaps addressed:
1.
catalog/agent-team/README.md— Input propagation gotcha (mirrors d688265)The "Limits and gotchas" entry for Input propagation previously said agents "must fail loudly if required inputs are missing" without explaining what that means in practice. Commit d688265 hardened all three dispatched agents (planner, implementer, reviewer) to:
$\{\{ github.event.inputs.issue_number }})state:blocked+ comment whenissue_numberis availablemissing_data/report_incompletewhenissue_numberis itself absentThe updated gotcha documents all three behaviors and adds a concrete recovery path (
gh workflow run <next-agent>.lock.yml -f issue_number=<N> -f iteration=<N>).2.
README.md— Add## PublishingsectionCONTRIBUTING.md:115has pointed atREADME.md#publishingsince the initial commit, but the section never existed — a dead internal link for any maintainer following the publish checklist. The new section documents the three-step release flow: bump version, create GitHub release, update external listings.Testing
CONTRIBUTING.md#publishinglink now resolves to the new section in README.md.