Repository navigation
docs(qa): wave-3 accuracy slice S2 — studio-authoring.json - #28351
Conversation
Twenty-two studio-authoring items re-read against the code and re-pointed to what it does today, from the checklist-accuracy findings of QA runs #27392, #27438, #27441 and #27481 parked on wave anchor #27377. Each item takes revision +1 and one history row citing its run record; main's history stays an exact prefix. No clause is weakened. Claude-Session: https://claude.ai/code/session_01QSeKYmTYfaPbLQD4BJfomW Co-Authored-By: Claude <noreply@anthropic.com>
|
domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW 席位核对 — ACCEPT · domain:devx#2 · head
|
Part of #27377
Clause-②: no
Metadata-protocol: none
维护者速读
docs/qa/platform-checklist/areas/studio-authoring.json里 22 个测试项按今天的代码重写了过时的步骤、夹具和判据文字(只改清单文本,不动产品代码)。studio-authoring.json中draft-publish-lifecycle的 acceptance10、record-page-roundtrip(Kind = full 前提)、multi-package-item-rows的 acceptance3。pnpm check:platform-checklist,应输出check-platform-checklist: OK — 16 areas, 352 items,退出码 0。What changes
Wave-3 accuracy slice S2: every census STALE row for
docs/qa/platform-checklist/areas/studio-authoring.json, re-verified against the code at basea0f865491d(later merged up to3fd803379) and edited to what the code does today. Each touched item takesrevision+1, keeps main'shistoryas an exact prefix, and gains one history row citing the run record the finding came from and #27377. No clause is weakened. Where a clause changed, it became more precise or stronger (draft-publish-lifecycle A10, multi-package-item-rows A3, removed-key-save-door-refusal A0, flow-edge-type-authoring A0, record-page-roundtrip A0 and N0). No product code is touched.refreshIntervalSeconds… Rename the key"); an aged-out key is reported by unrecognized_keys at the PARENT path, with the key namedshowcase.restricted_ops); the gated action is inline on OBJ's actions[]; knownGaps[0] "launcher half FAILS TODAY" → no longer a gap (since #27021 the launcher reads /me/apps)allowExportdropped (a per-object key; set-level is 422)buttons"never rendered" → renders (submit label, hidden cancel)Skipped by order (the census holds them out of the slices):
studio-authoring.expression-editors(rows 71, 89, 165, 222, 223), the SCOPE-negatives sweep (rows 80, 167), andstudio-authoring.validation-rules-authoringA3 (rows 160, 225, UNCLEAR). Not edited: row 94 (FIXED upstream at r3) and row 75 (GAP: the no-entry matrix needs a re-run, not a fixture-text edit).Tests
No code changed, so the only measurement is the ledger's own gate and the derived gate families, taken on the final head.
pnpm check:platform-checklist
A shape check over the parsed file, against the base copy: 22 items changed, each with
revision+1,history[:-1]equal to the base history, and the new last row's revision equal to the item's. No other item and no area-level key moved.Acceptance notes
useDraftAutoSave.ts, the same at the run subject c4c515a), and the step uses the source.actionitem with objectName rendering on no surface. The item now authors the action inline. The rendering gap itself goes to the seat in the report; it is not edited here.sys_metadata_auditobject's field doc lists the denied codes not_overridable, not_creatable, invalid_metadata and destructive_change, and nothing inpackages/writes them at this base. This is documentation drift with no consumer, noted here and not filed.ui/e2e/live/studio-editor.spec.tsis now titled "… and the added block is stored". It may also reach acceptance[2]. The ref is not widened here.triggerType: 'schedule'with no cadence, so the rail shows the flow as Autolaunched. The ledger states this as authoring guidance only; no defect is claimed.Verification
Derived gate families (dispatch-gates --commands, final head), each exit captured before any pipe
Changeset: none.
docs/qa/publishes nothing, so this PR carriesskip-changeset.Generated by Claude Code