chore(agents): batch graphify doc updates instead of per-PR - #109
Merged
Conversation
Doc/spec edits no longer owe a by-hand /graphify --update on every PR: the update is batched — run once ~10 PRs have landed since the last one, or when a graph query visibly misses recent docs. The post-commit hook still rebuilds for code changes on its own. Co-Authored-By: Claude Opus 5 (1M context) <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.
What
AGENTS.md's graphify rule required a by-hand/graphify --updateafter everyspec/doc edit. In practice sessions either forgot it (the #103 logo sat
unindexed for a week) or paid a multi-minute update at the tail of every
doc-touching PR (the retire-invites wrap-up). User call, 2026-08-07: batch it.
New rule: never per-PR — run
/graphify --updateonce ~10 PRs have landedsince the last update, or when a graph query visibly misses recent docs. The
post-commit hook still rebuilds for code changes automatically; nothing else
changes.
Verified
pnpm test45 files / 594 passed;tsc --noEmitclean; oxlint clean(doc-only change — gates run as ritual).
code".
AI coding brief
Original request — "改改 CLAUDE.md……不要每次都去 update，起码过了 10 个 PR
再走 update" via
/murmur-ship. The why: the per-PR manual update was observedcosting minutes at the end of a doc-heavy PR while ALSO being silently skipped
by other sessions — a rule that is both expensive and unenforced is a bad rule.
Manual interventions — none beyond the request itself.
Retro — trivially scoped ship; the only judgment was wording the trigger
("~10 PRs or a visibly stale query") so the next agent can act on it without
counting commits precisely.
🤖 Generated with Claude Code