Repository navigation
Design baseline V1.0 and delivery-document conformance fixes (docs 00–03, README, CLAUDE.md, CI) #9
Description
Activity
Claimed by dispatcher session
session_01VR2khJ3Me96btawVsfG6jb. Branch:issue-9-design-baseline-v1. Worktree../kpi-issue-9, baseline main @ 8cce30c. Developer subagent dispatched; parallel item #10 ownssrc/,test/,scripts/,docs/04,docs/05(do not touch).
Generated by Claude Code
#9 Design baseline V1.0 and delivery-document conformance — self-test report
Page 1: Conclusion
Conclusion: NOT PASSED (存在问题)
10 cases: passed 9, needs-clarification 1.
There is no failed case. The single needs-clarification case is a self-contradiction inside the work item itself, not a defect in the change — it needs a PM ruling before it can be closed either way.
Needs-clarification list
Case Where the ambiguity is T-001 docs/00 red-line full-text scan Check rule 1 requires 「待确认」 to scan zero across the whole of docs/00. Two hits remain and both are required by the work item's own instructions: line 27 is the V0.9 history row that instruction 1.2 says must not be edited (历史行不改, and os-project-std-docs section 3 makes history rows immutable), and line 28 is the V1.0 row whose text instruction 1.2 dictates verbatim — that dictated text itself contains the phrase 「待确认事项」. The document body outside the version-record table scans zero. Fixing the scan would mean rewriting a historical version row, so it was not done unilaterally. See 需拍板事项 A below.No screenshots: this work item has no UI change (documents plus CI configuration only).
2. Test environment
Item Value Version under test ecd46a8on branchissue-9-design-baseline-v1; baselinemain@8cce30cEnvironment worktree /home/user/kpi-issue-9, node 22 / pnpm 10; CI on ubuntu-latestSurface none (documents plus CI configuration) Test accounts not required — no functional change, no dev server started Preconditions pnpm installcompleted in the worktreeTest date 2026-09-02
3. Test plan and results
Cases are the work item's 校验规则 1–6 plus 验收标准 1–4 plus the scope rule. Boundary / exception / permission classes do not apply: no code path, no data write and no permission surface is touched — exemption noted here as the template requires.
ID Title Type Result Evidence T-001 校验规则 1 — docs/00 red-line full-text scan main needs-clarification section 4 T-002 校验规则 2 — bonus/penalty responsibility consistent in three places main PASS section 4 T-003 校验规则 3 — docs/01 key figures reconcile with the body main PASS section 4 T-004 校验规则 4 — docs/02 section 1 vs section 2.z; version numbers main PASS section 4 T-005 校验规则 5 — no 待放行 / 未经放行 anywhere under docs/ main PASS section 4 T-006 校验规则 6a — pnpm verifygreenmain PASS section 4 T-007 校验规则 6b / 验收标准 4 — verifycheck present and green on the PRmain PASS section 4 T-008 验收标准 1 — V1.0 in three places; version record holds both V0.9 and V1.0 main PASS section 4 T-009 验收标准 3 — chapter 10 three tables, three columns, no 备选 / 建议 column main PASS section 4 T-010 Scope rule — no forbidden path touched main PASS section 4
4. Case detail — raw command output
T-001 — 校验规则 1
$ for p in '`' 开源版 企业版 SHA hierarchy 待确认 待拍板 '约 ' 大概 基本 差不多 如下图 下图 如下表 下表; do grep -c -- "$p" docs/00-设计方案.md; done ` -> 0 开源版 -> 0 企业版 -> 0 SHA -> 0 hierarchy-> 0 待确认 -> 2 待拍板 -> 0 约 -> 0 大概 -> 0 基本 -> 0 差不多 -> 0 如下图 -> 0 下图 -> 0 如下表 -> 0 下表 -> 0 $ grep -n '待确认' docs/00-设计方案.md 27:| V0.9 | 2026-09-02 | 首版送审稿:依据《KPI 考核管理系统 功能性需求文档》V1.3 成稿,含 17 项待确认事项 | AI 需求分析师 / AI 架构师 | 待客户方确认 | 28:| V1.0 | 2026-09-02 | 客户方 2026-09-02 逐条回复第 10 章 17 项:... 据此把待确认事项改写为已确认口径并入正文;... $ sed '27,28d' docs/00-设计方案.md | grep -c '待确认' # body, version-record table excluded 0 $ grep -n '待项目经理填写' docs/00-设计方案.md # the two permitted exceptions 15:**编制方:(待项目经理填写单位全称)** 17:**客户方:(待项目经理填写单位全称)**Result: 14 of 15 terms zero; 「待确认」 non-zero for the reason stated on page 1. Needs-clarification.
T-002 — 校验规则 2
$ grep -n '加减分' docs/00-设计方案.md (the three load-bearing lines) 75:| 人力审核 | ... 审批数据调整、提出加减分、审计查询 | 全部 | 76:| 人力负责人 | 人力节点审批、审批数据调整、审批加减分、审计查询 | 全部 | 128:- 由人力审核在填报单下按事项登记加分 / 扣分(分值、依据必填),人力负责人审批后计入最终得分;不封顶不保底;归档后不能再加减分。 211:| 6 | 加减分边界 | 不封顶不保底;人力审核提出、人力负责人审批 |Table 1, section 5.6 and chapter 10 item 6 now all say: HR review proposes, the HR lead approves. The 部门填报人员 row no longer claims 加减分申请. PASS.
T-003 — 校验规则 3
key figures paragraph: - 场景:共 16 个(简单 4 / 中等 9 / 复杂 3),推断场景 2 个(见附录 B) - 覆盖度:原生 12 / 需定制 4 / 做不了 0 / 待验证 0 - 风险:高 2 / 中 5 / 低 2 - 疑点:12 条(模糊 6 / 矛盾 0 / 缺失 6) - 商务条款:六项扫描,发现风险 0 项、「未提及」6 项 measured from the body: section 1 scenario table rows -> 16 (简单 4, 中等 9, 复杂 3) section 2 coverage -> 原生 12, 需定制 4 section 3 risks -> 高 2, 中 5, 低 2 section 4 doubts -> 模糊 6, 矛盾 0, 缺失 6, total 12 inferred markers in the section 1 table -> S-07, S-11All four groups reconcile. PASS.
T-004 — 校验规则 4
$ grep -n '^| 蓝图版本 |' docs/02-总体方案蓝图.md 5:| 蓝图版本 | V0.3 | $ grep -n '^| V0\.' docs/02-总体方案蓝图.md | tail -1 169:| V0.3 | 2026-09-02 | 设计方案 V1.0 客户确认;实现已改为按方案动态共享规则(#2 已合入 main) | 文档信息、§1、§2.1、§2.z、§6 | AI 架构师 |Document-information version equals the last update-record row. Section 1 against section 2.z, item by item: objects 17 self-built + 2 platform; object views 17, named list views 33 (grid 30 / kanban 2 / timeline 1), inline-edit lists 7; platform flows 0 + 1 self-built state machine; permission sets 6, positions 6, sharing rules static 0 (generated per published plan); reports 3, dashboards 2, datasets 3; import/export 3 objects; notifications 0; scheduled tasks 0; code points 6; Console only. Every figure matches. PASS.
Positions 6 is independently confirmed by the build:
Security: 6 Positions 6 Permissionsin the validate output below, and bysrc/security/index.tsdefiningkpi_admin,kpi_hr_reviewer,kpi_hr_head,kpi_dept_reporter,kpi_branch_checker,kpi_exec_leader. The old B-M1-02 figure of 5 was wrong.T-005 — 校验规则 5
$ grep -rn "待放行\|未经放行" docs/ ; echo exit=$? exit=1No output, exit 1 = no match. PASS.
T-006 — 校验规则 6a
Run through the container's shared heavy-verify lock:
os-verify-lock: ACQUIRED after 0s — running: cd /home/user/kpi-issue-9 && pnpm verify > objectstack validate ✓ Validation passed (1798ms) KPI 考核管理 v0.1.0 Data: 17 Objects 182 Fields UI: 1 Apps 17 Views 1 Pages 2 Dashboards 3 Reports 16 Actions Logic: 0 Flows Security: 6 Positions 6 Permissions > tsc --noEmit (no output) > vitest run Test Files 5 passed (5) Tests 55 passed (55) Duration 935ms os-verify-lock: VERDICT command-exit 0 · held the lock 23s · waited 0sPASS (read from the VERDICT line, not from a bare exit code).
T-007 — 校验规则 6b / 验收标准 4
check runs on PR #11, head ecd46a8: name=verify status=completed conclusion=success started 2026-09-02T17:30:12Z, completed 2026-09-02T17:30:50Z https://github.com/objectstack-ai/kpi/actions/runs/33661461449/job/100352742176The
verifyjob exists on the PR and is green on its first run. PASS.T-008 — 验收标准 1
Cover 「版本号:V1.0(客户确认版)」; version-record table holds the untouched V0.9 row plus the new V1.0 row as its last row; chapter 13 reads 「确认方式:本文 V1.0 依据客户方 2026-09-02 对第 10 章 17 项的逐条回复成稿;……」. PASS.
T-009 — 验收标准 3
Table 7 header
# | 事项 | 确认口径; table 8 header# | 事项 | 确认口径; table 9 header# | 边界 | 说明. All three columns.$ grep -c '备选' docs/00-设计方案.md -> 0 $ grep -c '建议' docs/00-设计方案.md -> 0PASS.
T-010 — Scope rule
$ git status --porcelain -uall M CLAUDE.md M README.md M docs/00-设计方案.md M docs/01-需求解读报告.md M docs/02-总体方案蓝图.md M docs/03-方案分级.md ?? .github/workflows/ci.ymlExactly the seven files the work item names. No
src/,test/,scripts/,docs/04,docs/05,package.jsonorpnpm-lock.yamlchange — so no collision with the parallel work item. A control-character scan over all seven files is clean. PASS.
5. Items for the PM to rule on
A. Check rule 1 contradicts instruction 1.2 on the phrase 「待确认」. Instruction 1.2 says the version-record history row must not be edited and dictates a V1.0 row whose own text contains 「待确认事项」; check rule 1 asks for zero hits of 「待确认」 in the whole file. Both cannot hold.
Option A (implemented): keep both version-record rows exactly as instructed, accept two hits confined to the version-record table, and record the deviation here. Option B: reword the two rows so the scan is zero, which means editing a historical version row and departing from the dictated V1.0 wording.
Recommendation: option A — os-project-std-docs section 3 makes history rows immutable, and the scan's purpose (no unconfirmed items left in the delivery text) is met, since the body outside the version-record table scans zero.B. Company legal names for the cover are still missing. The cover now reads 「(待项目经理填写单位全称)」 for both 编制方 and 客户方, per instruction 1.1. These two placeholders are the documented exception to check rule 1 and must be filled before the document is sent out.
6. Deviations from the work item's change list
- Chapter 4 flow diagram: check rule 1 asks for zero backticks, but the flow under 图 1 was a fenced code block (three backticks). The change list does not mention it. It was converted to a blockquote so the scan is genuinely zero; content is unchanged. A code block is also the wrong typesetting for a client-facing document.
- Section 5.1 tab name: check rule 1 asks for zero hits of 「基本」, which the tab list 「基本信息 / 计分规则 / 口径说明」 contained. Renamed to 「指标信息」 in the document. The implementation still labels that tab 基本信息 — see 遗留问题 below.
- Signature table numbered 表 11: added under change-list item 1.16 (figure and table numbering review); it was the only unnumbered table in the file.
7. Known follow-ups (not touched — out of scope for this work item)
src/objects/indicator.object.tslabelsowner_unitas 「责任板块(考核部门)」. The design proposal now says 部门板块 per requirements section 1.4. The field label should follow, butsrc/**is off-limits here.src/views/index.tslabels the indicator form tab 「基本信息」, which the proposal now calls 「指标信息」.docs/01section 1 row S-04 still says 责任板块.docs/01is a dated snapshot the work item says to correct only, not rewrite, so the term was left as written at the time.README.mdstill names the SHA-256 checksum. README is a developer-facing file, not a client deliverable, so the red line does not apply — flagging it only so the difference fromdocs/00is deliberate and visible.
Generated by Claude Code
#9 Requirements-conformance checklist — item by item
Legend: ✅ done as written ·
⚠️ done with a documented deviation · ❌ not done.
Verified atecd46a8, PR #11. Every⚠️ row carries its exit link.1.
docs/00-设计方案.md→ V1.0# Item State Note 1.1 Cover: V1.0(客户确认版), 2026 年 09 月 02 日, both parties 「(待项目经理填写单位全称)」; legal names raised in 需拍板事项 ✅ raised as item B in the self-test report 1.2 V1.0 row appended verbatim; history rows untouched ✅ V0.9 row byte-identical to main1.3 依据文件 line: repository path in backticks removed ✅ now 「《KPI 考核管理系统 功能性需求文档》V1.3(2026-09-02,客户业务方提供)」 1.4 Chapter 1 「需要您确认的」 → 「已确认口径」; 现状 last sentence ✅ 1.5 Table 1: five role rows reworded ✅ HR review 提出加减分; HR lead 审批加减分; reporter row drops 加减分申请; checker row per item 13 1.6 Section 5.6 rewritten ✅ 1.7 Section 5.7 sentence appended (item 14) ✅ 1.8 5.9 「SHA-256 校验和」 → 「校验和」 ✅ 1.9 Chapter 9 last bullet rewritten ✅ 1.10 Table 5 total row: empty cells → 「—」 ✅ 1.11 责任板块 / 所属板块 → 部门板块 throughout; other terms checked against requirements section 1.4 ✅ 3 occurrences replaced; remaining glossary terms already matched 1.12 Chapter 10 renamed; tables 7, 8, 9 to three columns; item 17 rewritten; 备选 column dropped ✅ table 9 keeps its 「# / 边界 / 说明」 header — already three columns, and the instruction prescribes the 确认口径 header for tables 7 and 8 only. Chapter 2's cross-reference 「见第 10 章第 15 项」 still resolves. 1.13 Table 10 first row ✅ 1.14 Chapter 12 last sentence ✅ 1.15 Chapter 13 「确认方式」 sentence ✅ worded to carry「本文 V1.0」so 验收标准 1 has its third V1.0 anchor 1.16 Figure and table numbering reviewed; captions placed correctly; references by number ⚠️ two additions the change list does not name: the chapter 4 flow was a fenced code block (backticks, which check rule 1 forbids) and became a blockquote; the signature table was the only unnumbered table and became 表 11. Both recorded in section 6 of the self-test report. 2.
docs/01-需求解读报告.md# Item State Note 2.1 Verdict restated in the three-way form ✅ text used verbatim as specified 2.2 疑点 → 模糊 6 / 缺失 6; 商务条款 → 发现风险 0 项 ✅ both reconcile against the body, see T-003 2.3 S-07 and S-11 marked 「(推断)」 in the section 1 table ✅ 2.4 后续处理 row appended; no per-doubt 「产品默认」 sections added ✅ PR #6's approach deliberately not carried over 3.
docs/02-总体方案蓝图.md→ V0.3# Item State Note 3.1 蓝图版本 V0.3; 基于基准 rewritten; 审定记录 kept ✅ 3.2 Section 1 and section 2.z figures aligned (views, sharing rules) ✅ verified item by item in T-004 3.3 B-M1-02 岗位 6 个(含考核系统管理员) ✅ independently confirmed: build reports 6 Positions,src/security/index.tsdefines six3.4 B-M1-03 dynamic sharing rules; B-M1-04 rewritten; platform configuration detail dropped ✅ unit/unit_and_below/objectstack validate/sys_userfield names all gone3.5 Section 6 rewritten (PM informed) ✅ section 1 対账 bullet updated to match 3.6 V0.3 row appended to the update record ✅ 4.
docs/03-方案分级.md# Item State Note 4.1 执行说明 rewritten ✅ the header note's 「标记「待放行」」 also had to go for check rule 5 to be zero 4.2 Three 待确认点 checkboxes ticked with their conclusions ✅ D-01, D-02, D-03 as specified 4.3 D-01 影响范围 permission row rewritten ✅ 4.4 放行记录 rewritten ✅ 4.5 Section 二 heading 「待放行」 → 「已确认」 ✅ 5.
README.md# Item State Note 5.1 Document table: docs/00, docs/01, docs/03, docs/05 rows ✅ docs/05 no longer states a case count 5.2 口径基准 line added under 业务流程 ✅ 5.3 No 「产品默认口径」 section added ✅ 6.
CLAUDE.md# Item State Note 6.1 src/hooks/sheet-transition.hook.ts→src/hooks/sheet.hook.ts✅ the corrected path is the file that exists 6.2 开工前必读 wording for docs/00 ✅ 7.
.github/workflows/ci.yml# Item State Note 7.1 New workflow: push to main + pull_request; checkout@v5, action-setup@v4 (version 10), setup-node@v5 (node 22, pnpm cache); install --frozen-lockfile then validate, typecheck, test; job verify;permissions: contents: read; concurrency by ref with cancel✅ green on its first run, 38s Check rules and acceptance criteria
Item State Note 校验规则 1 — docs/00 red-line scan ⚠️ 14 of 15 terms zero. 「待确认」 has two hits, both inside the version-record table and both required by instruction 1.2 itself; the body outside that table scans zero. Ruling requested as item A of the self-test report. 校验规则 2 — bonus/penalty responsibility ✅ three places consistent 校验规则 3 — docs/01 key figures ✅ all four groups reconcile 校验规则 4 — docs/02 figures and version numbers ✅ 校验规则 5 — no 待放行 / 未经放行 under docs/ ✅ zero hits 校验规则 6 — pnpm verifygreen;verifycheck on the PR✅ local green; CI verifygreen on PR #11验收标准 1 — V1.0 in three places, both version rows ✅ 验收标准 2 — check rules 1–5 ⚠️ same single item as 校验规则 1 above 验收标准 3 — chapter 10 three tables, three columns ✅ 备选 and 建议 both scan zero 验收标准 4 — verifyjob green on the PR✅ run 33661461449 Output rule — only the seven named files; no binaries or screenshots ✅ see T-010
Generated by Claude Code
Dispatcher collection check for PR #11 (head ecd46a8): passed.
- Changed files: 7, all within the allowed set; no
src/,test/,scripts/,docs/04,docs/05; no binaries. git merge-tree --write-tree origin/main HEAD: clean.- Validation rules 2–5 re-run by the dispatcher: all pass. Rule 1: the only two "待确认" hits are inside the version-record table (the untouchable V0.9 row and the V1.0 row text prescribed by the work item); body text has zero hits.
- Commit trailers present; no model identifiers in messages or files.
Decision on item A (version-record rows vs. rule 1): option A accepted — version-record history rows are never edited (os-project-std-docs §3.1); rule 1 is read as "document body". Item B (cover unit names) is pending the project owner's input and stays as the two placeholders.
Next: independent review gate, then merge.
Generated by Claude Code
- Changed files: 7, all within the allowed set; no
Review gate (independent reviewer, PR #11 @ ecd46a8): NOT MERGEABLE — 0 blocking, 2 should-fix, 6 notes. Returned to the developer on the same branch.
Should-fix:
docs/00§5.1 renamed the indicator tab to「指标信息」while the system's tab is「基本信息」(src/views/index.ts:32). The word「基本」in validation rule 1 targets vague wording, not this noun — treat as a false positive and restore「基本信息」.- Compliance-checklist comment: item 1.16 lists two unlisted additions but the self-test report names three; item 3.4 claims
unit / unit_and_belowis gone everywhere whiledocs/02line 28 (B-M1-01) still has it. Amend the comment.
Also folded into this item (same files, reviewer notes):
docs/02B-M1-01 platform detail contradicting B-M1-03; inline-edit list count is 8, not 7 (in both §1 and §2.z).Recorded, not in scope here:
srcfield label「责任板块」vs. requirement glossary「部门板块」(separate work item); README keeps「SHA-256」on purpose (developer-facing); figure 1 remains a text flow (real diagram at docx stage); chapter 12 process wording (existing text).
Generated by Claude Code
Correction to the two earlier developer comments (test report 5513682647 and compliance checklist 5513699626), posted by the dispatcher because the toolset cannot edit existing comments. This comment supersedes the lines named below; the PR #11 body ("Review round" section) carries the same content.
- Test report §6, item "5.1 tab renamed to 指标信息": reverted in c9002ee. The word「基本」in validation rule 1 targets vague wording; the noun「基本信息」is a false positive, handled through the same exit as「待确认」in the version-record rows.
- Compliance checklist item 1.16: the change list had three unlisted additions, not two — chapter 4 code block converted to a quote block; section 5.1 tab rename (now reverted); signature table numbered as table 11.
- Compliance checklist item 3.4: platform configuration details were removed from B-M1-03 / B-M1-04 as specified; B-M1-01's
unit / unit_and_belowwording was outside the original list and has now been replaced in c9002ee (data scope resolved by per-plan sharing rules, see B-M1-03). - Additionally in c9002ee: inline-edit list count corrected from 7 to 8 in
docs/02§1 and §2.z (grep -c "inlineEdit: true" src/views/index.ts→ 8).
Generated by Claude Code
- added a commit that references this issue
on Sep 2, 2026 Merged PR #11 into main as fbf64da (collection check passed; review gate MERGEABLE at c9002ee). Status → PM验收中; handed to the work-item creator for acceptance. Remaining open point: cover unit names (编制方 / 客户方) still placeholders pending the project owner. The
srclabel wording (责任板块 → 部门板块) is filed as #13.
Generated by Claude Code
业务场景(设计方案 docs/00 第 10 章;交付文档规范 os-project-std-docs)
客户方 2026-09-02 对《设计方案》V0.9 第 10 章 17 项逐条回复:第 1~12 项全部同意产品默认,第 13 / 14 / 15 项均选 A。据此设计方案升 V1.0,成为唯一需求基准。同日对 docs 全部文档按 os-project-std-docs(封面 / 版本记录 / 图表 / 版本纪律 / 内容红线)逐项审查,发现的不符项一并整改。本工作项只改文档与 CI 配置,不改任何代码。
审查发现(逐条对应下方修改清单):
src/hooks/sheet-transition.hook.ts,实际文件是src/hooks/sheet.hook.ts。触发操作
无界面改动。GitHub 上每次 push 到 main 与每个 PR 自动运行 CI。
输入与字段(逐文件修改清单)
1.
docs/00-设计方案.md→ V1.0(客户确认版)V1.0 | 2026-09-02 | 客户方 2026-09-02 逐条回复第 10 章 17 项:第 1~12 项同意产品默认,第 13 / 14 / 15 项选 A;据此把待确认事项改写为已确认口径并入正文;修正表 1 与第 10 章第 6 项的加减分职责矛盾;补齐表 5 空单元格;删去仓库路径与平台版本实现细节;术语按需求 §1.4 统一为「部门板块」 | AI 需求分析师 / AI 架构师 | 客户方书面确认(2026-09-02 回复)。2.
docs/01-需求解读报告.md(dated 快照,只纠错不重写)3.
docs/02-总体方案蓝图.md→ V0.3unit/unit_and_below/objectstack validate等平台配置细节,判定依据只写「平台共享规则只放宽、行级安全只收窄,均为平台原生能力」;B-M1-04 删去平台字段名,改写为「平台账号体系承担密码策略、锁定、失败计数、封禁」。4.
docs/03-方案分级.md[x]并在其后写确认结论:D-01「分管领导按方案版本配置在参与主体上——已确认(表 7 第 1 项)」;D-02「公式表达式语言采用平台 CEL——已确认(表 7 第 2、12 项);计分口径 Q-01~Q-05 已按表 7 第 2 / 4 / 5 / 6 / 7 项确认」;D-03「审核人从「待我处理」队列进入——已确认(表 7 第 3 项);驳回口径按表 7 第 8 项」。5.
README.md6.
CLAUDE.mdsrc/hooks/sheet-transition.hook.ts改为src/hooks/sheet.hook.ts。7. 新增
.github/workflows/ci.ymlpush main 与 pull_request 触发;
actions/checkout@v5、pnpm/action-setup@v4(version 10)、actions/setup-node@v5(node 22,cache pnpm);pnpm install --frozen-lockfile→pnpm validate→pnpm typecheck→pnpm test;作业名verify;permissions: contents: read;concurrency 按 ref 取消旧运行。校验规则
docs/00-设计方案.md全文检索:反引号、「开源版」「企业版」「SHA」「hierarchy」「待确认」「待拍板」「约 」「大概」「基本」「差不多」「如下图」「下图」「如下表」「下表」——全部零命中(「待项目经理填写」两处除外);docs/00表 1 / 5.6 / 第 10 章第 6 项三处加减分职责一致(人力审核提出、人力负责人审批);docs/01关键数字四组与正文逐节可对(场景 16 = 4 + 9 + 3;覆盖 12 + 4;风险 2 + 5 + 2;疑点 6 + 6);docs/02§1 与 §2.z 每个数字一致;文档信息版本号 = 更新记录末行版本号;grep -rn "待放行\|未经放行" docs/零命中;pnpm verify绿;CI YAML 在 PR 上出现verify检查并通过。输出 / 反馈
src/、test/、scripts/改动;不涉及docs/04、docs/05(由并行工作项负责)。依赖
无代码依赖。取代 #3 与 PR #6(已关闭);#7 的 docs/04 统计问题由并行工作项处理。
验收标准
docs/00封面版本号、版本记录末行、第 13 章均为 V1.0,且版本记录含 V0.9 与 V1.0 两行 → 通过;docs/00第 10 章三张表均为三列且无「备选」「建议」列 → 通过;verify作业且为绿 → 通过。