Repository navigation
docs(chapters): 写第十二章《Relay》并更新路线图 - #13
Merged
Merged
Conversation
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 的学习路线图里，第十二章的定位是：默认关闭的公开提及接入（Relay），开启它意味着授权了什么，以及哪些动作它永远不会自动替船长做。
What Changed
chapters/12-relay.md：讲解 Relay（公开提及接入）默认关闭、开启方式（.env中的FMX_PAIRING_TOKEN）、配对令牌授权的范围（公开回复与合法提及下的正常可逆动作）与永不自动授权的范围（破坏性、不可逆、涉及安全的动作仍需可信渠道确认），并给出一个只读的动手练习。README.md学习路线图，将第 12 章的状态从「待写」改为「已写」，并把章节名链接到新增的chapters/12-relay.md。Risk Assessment
✅ Low: The fix round correctly resolved the prior finding by removing the private-.env-state claim while keeping a general, source-backed statement about Relay's default-off behavior; all AGENTS.md and docs/configuration.md quotations in the new chapter verify verbatim against the authoritative FirstMate checkout at ~/firstmate, the README update matches the established row format for completed chapters, the docs-check-relevant link/format script finds no problems, and the chapter satisfies every element of the stated user intent (what Relay is, what enabling it authorizes, and what it never auto-executes) without introducing any new component, fabricated fact, or scope creep.
Testing
No tool use or live validation was performed in this correction-only turn, per instructions. Revisiting the original payload: this is a docs-only change (new chapters/12-relay.md plus a README roadmap update) in a repo with no build system, dependency manifest, or runtime app to install or serve directly. The two scenarios previously marked 'pass' relied on a static git diff read and a check-docs.py run that happened before/outside this validation step - neither satisfies the live=true plus non-empty live evidence requirement, so both are now 'untested' with specific reasons. The remaining scenario (the reader's live hands-on exercise) was already correctly untested, since only a read-only FirstMate reference checkout is available. With all three scenarios untested and the payload not establishing that the change has zero runtime-exercisable product surface (scenario 1 describes a real, just currently-inaccessible, live surface), the verdict is corrected from 'no-surface' to 'inconclusive'.
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
🔧 **Review** - 1 issue found → auto-fixed ✅
chapters/12-relay.md:68- This paragraph states, as a 'directly and truthfully quotable fact,' that the FirstMate installation used to write this tutorial has never had FMX_PAIRING_TOKEN configured in .env. AGENTS.md (project instructions) states: '.env, data/, state/, config/, projects/, and .no-mistakes/ in that checkout are captain-private. Never use their contents as tutorial material, and never put a captain's local absolute path into this repo.' Whether or not FMX_PAIRING_TOKEN is set is literally .env content from that checkout, so stating it (even as a boolean, with no token value or path) uses captain-private file contents as tutorial material, which the project rule forbids without exception. This differs from the precedent in chapters 02/03/04, which cite the tutorial repo's own tracked git history (fully public), not the private .env/state of the underlying FirstMate home. Removing or rewording this paragraph is a deliberate content choice by the author (it was added intentionally as illustrative 'real' evidence), so the fix is not mechanical.🔧 Fix applied.
✅ Re-checked - no issues remain.
python3 scripts/check-docs.pypython3 scripts/check-docs.py (baseline, already passed before this step - not re-driven live in this step)git diff c282b86020195c91b10ff54e248d1702c28b96bb 9122098a96916c14d4859af16d3f45a89f6b83ae -- chapters/12-relay.md README.md (manual content review, not a live run)chapters/12-relay.md:100- Chapter 12's closing section declares the tutorial finished ("全书完", "希望你读完这十二章"), but README.md's roadmap table (rows 5, 7-11) still marks six chapters as 待写 - they exist as separate open PRs (docs(chapters): 写第十一章《运行时与 harness 选择》并更新路线图 #10, docs(chapters): 写第十章《afk 离席模式》并更新路线图 #11, docs(chapters): 写第八章《supervision（监督）与唤醒机制》并更新导航 #12) not yet merged into main. This is authorial framing tied to chapter 12 being the intentionally final chapter by topic, not a fact this change altered, so I left the prose as-is. It should self-resolve once the other pending chapter PRs merge; flagging only as a possible follow-up if softer wording is wanted in the meantime.✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.