docs(qa): close out D1 in the platform checklist + name the run-record home - #6777
Merged
Conversation
…home D1 (saved-report schedule routes) was fixed in #6683, so this reconciles the checklist and the follow-up register with the fixed state: - dashboards.saved-report-ownership: flip the known-gap probe clause from an expected-FAIL probe to a positive deny-as-404 assertion (revision 1->2, history entry ref #6683); drop the expected-FAIL language in negative/source. - FOLLOW-UPS.md: mark D1 fixed in #6683 and remove the exploit detail. - runs/README.md: name the canonical home for run records — one "[sweep] vN release test sweep" tracking issue per release (resolves the open archival question in #6681). Docs only; check:platform-checklist green (178 items, 27 mapped / 2 waived). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L8aEBrJVxRnA5XVRkeVft9
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
qq9340100
enabled auto-merge
August 8, 2026 17:05
github-actions
Bot
added
the
documentation
12 tasks
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
2 participants
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.
Docs-only closeout of the platform-checklist follow-ups (#6681), now that both #6557 (the checklist) and #6683 (the D1 fix) have merged.
Changes
areas/dashboards.json—dashboards.saved-report-ownership: the schedule-route clause was an expected-FAIL known-gap probe (D1:unschedule/listSchedulesweren't owner-gated). fix(reports): owner-gate the saved-report schedule routes (#2980) #6683 fixed that, so the clause is flipped to a positive deny-as-404 assertion (B's schedule list is empty, B's schedule delete is 404). Itemrevision1→2 with a history entry (ref fix(reports): owner-gate the saved-report schedule routes (#2980) #6683); thenegativeandsourcenotes drop the expected-FAIL language.FOLLOW-UPS.md— D1 marked FIXED in fix(reports): owner-gate the saved-report schedule routes (#2980) #6683 and the exploit detail removed (it was a live-vuln description; now it's a one-line fixed note).runs/README.md— names the canonical home for run records: one[sweep] vN release test sweeptracking issue per release (successor to the v16.0 browser test checklist — exercise every 16.0 feature in the running app #3358 model) — body hosts the human-readable verdict table, run-record JSON attaches there, eachfailbecomes its own linked issue. Resolves the open "where do run records live" question in tracking: 平台测试清单(PR #6557)merge 后跟进 — 首次执行验收、FOLLOW-UPS 决策清单、#3358 交接 #6681.Validation
node scripts/check-platform-checklist.mjs→ OK (15 areas, 178 items; 27 mapped / 2 waived). Docs only — no changeset.Refs #6681, #6683.
🤖 Generated with Claude Code
https://claude.ai/code/session_01L8aEBrJVxRnA5XVRkeVft9
Generated by Claude Code