tracking: 平台测试清单(PR #6557)merge 后跟进 — 首次执行验收、FOLLOW-UPS 决策清单、#3358 交接

[qq9340100]

承接 PR #6557(15 域 · 标准测试清单账本 + 覆盖棘轮 + CI 门禁)merge 前后的全部后续工作。清单本体的作者/执行契约见 docs/qa/platform-checklist/README.md / RUNNER.md;待决事项的完整上下文见同目录 FOLLOW-UPS.md。

进展:#6557(账本)与 #6683(D1 修复)均已合并;收尾 docs PR #6777(探针翻转 + 抹除细节 + 归档约定)已提。

Merge 前(先决)

• 处理 FOLLOW-UPS §1 D1 —— 代码修复 已合并(fix(reports): owner-gate the saved-report schedule routes (#2980) #6683);dashboards.saved-report-ownership 的 known-gap 探针已翻转为正常 deny-as-404 断言、FOLLOW-UPS 的 D1 细节已抹除并标记 FIXED(均在 docs(qa): close out D1 in the platform checklist + name the run-record home #6777,待合并)。
• 更新 feat(qa): AI 可执行的平台功能标准测试清单 — 15 域 178 项 + 能力覆盖 ratchet + CI 门禁 #6557 描述中已过期的统计数字 —— 已改为 178 项 / 995 条款 / 27 mapped(标题 + 正文)。

Merge 后:首次执行验收

• 跑 priority:P0(15 项)作为对清单本身的首次验收 —— 预期会产生一批条目 revision(steps 过时、fixture 不足等),这是账本机制正常工作的信号,不是失败。
• 验收后把 surface:api(49 项,免 console 构建)纳入常规节奏。
• 约定 run record 的唯一归档位置 —— 已定:每个发版一个 [sweep] vN release test sweep tracking issue(正文放人读汇总表,run-record JSON 附在旁边,每个 fail 单独 linked issue);已写进 runs/README.md(docs(qa): close out D1 in the platform checklist + name the run-record home #6777)。

旧体系交接

• 关闭 v16.0 browser test checklist — exercise every 16.0 feature in the running app #3358(v16.0 清单,被本账本取代);关闭前确认其未勾完的项均已被新条目覆盖,缺的补进 areas/*.json。

FOLLOW-UPS 决策清单

• §1 D2–D8 逐个决定立案/搁置(D2/D3/D7 标了 safe-to-file;D8 需要"声明 ≠ 强制还是文档化礼貌"的设计裁决)。
• §2 文档虚假宣传各开 docs issue:enable.trash / enable.mru / display pages / 数据深度五档(PD#10)。
• §3 fixture 清单择优补齐,解锁 8 个 blocked 条目(publicSharing 对象、OIDC IdP、gantt 依赖字段、审批 SLA 时钟 harness、种子第二用户等)。

校验脚本改进

• enumSource 从"成员数量比较"改为"成员集合比较"(数量不变的改名/成员替换类漂移目前检测不到)。
• 为其余矩阵条目补 enumSource pin(现仅 5/68;内联匿名 enum 无法 pin 的记录在案即可)。

首个正式 release sweep

• since:v17 + priority:P0 各出一份 run record,跑通"发版即过滤账本"的完整流程,并按上面约定归档到该版的 [sweep] issue。

[os-zhuang]

Maintainer ruling (2026-08-08): partial batch — ripe items ruled now; everything premised on the merge stays parked until PR #6557 actually merges.

Premise check first: the card's framing ("post-merge follow-ups") is not yet true — #6557 was kicked from the merge queue today (13:03Z) by a pre-existing, unrelated red (dogfood teardown hookTimeout, per the queue steward's reading). Per the freshness discipline, unverified-premise items are not ruled today.

Ruled now (independent of the merge):

1. D2 / D3 / D7 — approved for filing. They are marked safe-to-file and filing is cheap. File as unassigned issues; triage routes them.
2. Run-record archive location — tracking issue (one per P0 execution run), written into runs/README. CI artifacts expire with retention and an external QA store would be a second tracker; a GitHub issue keeps run history where all state lives. Run records are append-only history, not state — this does not conflict with the comments-carry-no-state rule.
3. v16.0 browser test checklist — exercise every 16.0 feature in the running app #3358 handover — proceed as described: confirm every unchecked item is covered by new ledger entries, backfill gaps into areas/*.json, then close v16.0 browser test checklist — exercise every 16.0 feature in the running app #3358.

Explicitly NOT ruled: D8 (declared-vs-enforced or documented courtesy) — it returns as its own decision card once #6557 merges and the first P0 execution provides data.

Bookkeeping already overtaken by events: D1's code fix merged today as PR #6683 — the card text should be refreshed by its owner accordingly.

State: needs-user-decision removed — with the ripe decisions made, this drops back to a plain tracking card; nothing left on it is dispatch-queue work today.

Maintainer directive (verbatim, covering this batch of 6 inbox cards): 「接受你的建议」. Recorded by PM session session_01JaVVMrSxt7Tgi1uwEuDtH7.

---

Generated by Claude Code