Repository navigation
docs: add ship follow-through gate and prune agent context - #1177
Merged
Merged
Conversation
Record the gem-pickup and Bump Version sequence so agents stop and ask which version to ship after work lands on main.
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
AGENTS.mdadds## Ship follow-throughwith thehtml2rssgem-pickup sequence (release gemworkflow check,origin/mainbranch,bundle update html2rss+make readyin Dev Container, required CI checks, squash-merge only when asked) and thebump-version.ymlgate (ask before dispatching, require--ref main, keep the draft GitHub release unpublished unless asked).AGENTS.mdencodes the explicit execution posture (Time matters. Reduce LOC when possible. No legacy code, no backward compatibility, no shims.) and drops duplicated verification, response-format, and UI prose in favor of single pointers todocs/README.md,CONTEXT.md, anddocs/design-system.md(104 → 46 lines).CONTEXT.md(56 → 19 lines) and.github/copilot-instructions.md(16 → 8 lines) are compressed into dense domain definitions and canonical file pointers without changing any contract or seam owner.Why
The gem pin and the app version bump are separate PRs that Mergify does not queue; dispatching
bump-version.ymlwithout a user-named bump or before the gem PR lands onmainships the wrong commit. At the same time, repeated rules acrossAGENTS.md,CONTEXT.md, and.github/copilot-instructions.mdconsumed context tokens on every load without changing model decisions.Risk
Review map
Review map: whole PR is small — start at
AGENTS.md. No test delta.Validation
make ready— RuboCop, Zeitwerk, YARD, frontend lint, and RSpec (357 examples, 0 failures)