Repository navigation
docs(chapters): 写第八章《supervision(监督)与唤醒机制》并更新导航 - #15
Merged
Merged
Conversation
…ils in ch8 case study"}
…tudy as hypothetical"}
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.
Intent
继续 Learn FirstMate 教程,写第八章。前七章已写完或正在走质检流水线。README 的学习路线图里,第八章的定位是:大副怎么在不烧 token 的前提下盯住整支队伍,什么事件会把它叫醒,什么时候才该轮到船长被打扰。第八章是路线图里「从单件活扩展到一支队伍要处理的事」这条线(第 6 到 8 章)的最后一章。
What Changed
chapters/08-supervision-and-wakeups.md, a new chapter covering how firstmate supervises a whole crew of crewmates without burning tokens while idle, the four wake-event types (signal,stale,check,heartbeat) and how each is handled, why a status line is a wake event rather than current state, and a hypothetical case study illustrating a stale-wake misjudgment.README.md's roadmap table to link chapter 8 to the new file and change its status from "待写" to "已写".Risk Assessment
✅ Low: Docs-only change: the README edit is exactly the single-row link/status update the user specified during the rebase, and the new chapter's quoted material from AGENTS.md, docs/architecture.md, and the bin/ script headers all verified verbatim against the read-only FirstMate checkout; the docs-check script passes and the two prior fix rounds' targeted ellipsis edits are correctly and minimally applied.
Testing
Verified the change is confined to two markdown files (README.md roadmap row 8, and new chapters/08-supervision-and-wakeups.md), re-ran the repo's only check (scripts/check-docs.py, clean), and manually confirmed both prior review-round decisions landed correctly in the diff. The chapter's hands-on exercise (running it against a live FirstMate session) was not exercised here since that session/checkout lives outside this docs repo and outside what these three checks stood up.
python3 scripts/check-docs.pyoutput: 'checked 14 markdown file(s): no problems found'Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
🔧 **Rebase** - 1 issue found → auto-fixed ✅
README.md- merge conflict rebasing onto origin/main🔧 Fix applied.
✅ Re-checked - no issues remain.
🔧 **Review** - 1 issue found → auto-fixed ✅
chapters/08-supervision-and-wakeups.md:32- The four-item wake-handling blockquote is introduced as '原文' (the original text), and item 3 correctly signals its truncation with a trailing '...'. Item 2, however, silently drops the second clause of the actual AGENTS.md sentence ('; a deep-inspection reason also requires current-state and validation-log inspection.') without any ellipsis or truncation marker, so it reads as a complete verbatim quote when it isn't. A reader relying on this section for the full authoritative rule on stale-wake handling would miss the deep-inspection requirement. Fix is mechanical: either quote the full sentence or add '...' like item 3 does.🔧 Fix applied.
✅ Re-checked - no issues remain.
✅ **Test** - passed
✅ No issues found.
python3 scripts/check-docs.pyoutput: 'checked 14 markdown file(s): no problems found'python3 scripts/check-docs.pypython3 scripts/check-docs.py (baseline, already run: 14 markdown files, no problems found)git diff 6b1f56e..a3f523d -- README.md (confirmed only row 8 changed, matching rebase decision)grep -n "unresponsive worker" chapters/08-supervision-and-wakeups.md (confirmed ellipsis fix present)✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.