docs(agents): record the agent working rules — slot dates, ≤5 concurrent agents, browser-verify before merge - #154
Draft
hotlong wants to merge 2 commits into
Draft
docs(agents): record the agent working rules — slot dates, ≤5 concurrent agents, browser-verify before merge#154hotlong wants to merge 2 commits into
hotlong wants to merge 2 commits into
Conversation
Follow-up to #84 / PR #105. Two maintainer instructions from 2026-09-02 and two standing ones from 2026-08-26, written down where an agent will read them instead of living in a dispatch message. Publishing cadence gains one sentence making the existing rule explicit for an agent that writes a post: its `date` is the slot it will occupy, it never stacks onto a day another post holds, and it merges on that day. The new "Working in this repo with agents" subsection records the concurrency ceiling of five worktrees, browser verification at real viewports before a content or visual PR merges (including the SVG `fill` trap, where a presentation attribute loses to a stylesheet class and dark-on-dark text passes every gate), that a visual defect is work rather than a note, and that merge time is publish time. 13 new lines, AGENTS.md only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FeA1nwBz1ohH65dvffUGKr
…er-verify rule The browser-verify bullet named only the pattern where a `fill` presentation attribute is shadowed by a stylesheet class. Finding #140 measured a second, distinct one on the same surface: a `text` node carrying neither a class nor an inline colour inherits the house `text{fill:#173a36}` default, so text on a dark card renders dark-on-dark too. Both reach the reader the same way and both are invisible to every gate, so they belong in one clause. One line, taking the diff to 14 insertions — 12 content lines plus the two blank separators a markdown heading requires (the earlier message's "13 new lines" counted the pre-fold state). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FeA1nwBz1ohH65dvffUGKr
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.
Fixes #132
Writes four maintainer instructions into
AGENTS.md, where an agent will read them, instead of leaving them in dispatch messages.AGENTS.mdis the only file touched.What changed
Publishing cadence gains one sentence making the existing rule explicit for an agent that writes a post: its
dateis the slot it will occupy, it never stacks onto a day another post already holds, and it merges on that day. The surrounding bullets already carry "two slots a week" and the merge-day rule, so the sentence points at them rather than restating them.New
## Working in this repo with agents, placed after Publishing cadence (and its two###subsections) and before Localization, with four bullets:dateis rewritten only by an explicit maintainer ruling recorded on the card.Two deliberate calls, for the reviewer
The SVG clause names two traps, not one. The card specified the pattern where a
fillpresentation attribute is shadowed by a stylesheet class (#125 / #133). Finding #140 measured a second one on the same surface: atextnode carrying neither a class nor an inline colour inherits the housetext{fill:#173a36}default, so text on a dark card renders dark-on-dark that way too. Both reach the reader identically and both are invisible to every gate, so the clause covers both in one sentence rather than describing a check that catches half the cases.Line budget. The card asked for ≤ 12 new lines; the diff is 14 insertions. Twelve of those are content lines — the other two are the blank separators a markdown
##heading requires and cannot be written without. Under that reading the change sits exactly at the ceiling, and folding #140 in was what took it from 11 content lines to 12. Flagging the arithmetic rather than asking you to take it on trust: if you read the budget as raw inserted lines, the #140 clause is the one line to drop.Gates
Run once through the shared verify lock at head
a1dd0a8, each gate's own verdict line quoted:pnpm content:lint✓ content lint passed (334 files checked)pnpm check- 0 errors/- 0 warnings/- 0 hintspnpm build[build] 866 page(s) built in 76.28s·[build] Complete!pnpm seo:smokeSEO smoke test passed (865 HTML pages checked)Wrapper:
os-verify-lock: VERDICT command-exit 0 · held the lock 97s (1m37s) · waited 0s.git status --porcelainempty afterwards —gen:zh-hantproduced no changes.AGENTS.mdis a governed surface, so this stays a draft for a human merge; review requested from @os-zhuang.🤖 Generated with Claude Code
Generated by Claude Code
Generated by Claude Code