@loomhelm/multi-task-flow 0.0.0-stage → 0.2.1

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/HISTORY.md

@@ -0,0 +1,86 @@
+# Shared UI visual evidence gate 演进历史
+
+> 这里记录会影响 Agent 理解“为什么一步步变成现在这样”的关键演进；单次任务流水账不放这里，规范正文仍以 `./SPEC.md` 为准。
+
+## Decision Trace
+
+- Visual evidence compares normalized candidates with the locked base commit's Same-Path Baseline before interrupting the owner. Unchanged inner UI reuses canonical assets; changed or unavailable comparisons require only a clear natural-language screenshot confirmation. Feedback Drafts remain outside convergence until their feedback completes this comparison.
+
+- The multi-pair `reg-cli` report keeps source snapshots as symlinks, locks the complete npm dependency tree, confines writes and ephemeral npm state to report staging, separates networked installation from offline comparison, seals staging before validation, audits its exact artifact inventory, and fails closed outside the supported macOS sandbox. The durable rationale and constraints are in [ADR 0022](../../adr/0022-sandboxed-reg-cli-report-execution.md).
+
+- Report inputs are restricted to independent files matching the snapshot generator's repo/date/timestamp layout; report-output rejection is case-insensitive, and hashes are rechecked across final publication with identity-bound rollback. This closes derived-file aliases and narrows the successful-publication race without copying source images.
+
+- Report audit now rejects hard-linked generated artifacts and applies the canonical snapshot repo-scope syntax to report paths. Input paths remain caller-selected across valid scopes; the manifest audit is consistency checking, not authentication against coordinated same-user rewrites.
+
+- PR 发布选择与视觉比较改为任务级合同：Phase A 只接收当前任务显式声明的 Task Evidence Set，Phase B 只读取可见受管 PR section，比较只读取锁定 base SHA 的同路径图片。该决定和取舍见 [ADR 0003](../../adr/0003-task-scoped-pr-visual-evidence.md)。
+
+- `e8d633b` feat(workflow): add ui visual evidence gate
+- `43a545f` fix(workflow): unify visual evidence section
+- `3ccadcb` fix(workflow): repair visual evidence continuation
+- `ce9708d` fix(flow): reroute stale ui evidence
+- `47f117b` fix(workflow): harden visual evidence contracts
+- `2162cfc` fix(workflow): preserve visual evidence sources
+- `eba6468` fix(flow): align screenshot continuation
+- `6ccbb70` fix(workflow): finalize visual evidence migration
+- `6a086cb` fix(workflow): relax visual evidence reuse
+- `afeddc2` fix(workflow): preserve legacy screenshot migration
+- `f6e92bb` fix(workflow): close visual evidence gates
+- `2d32ba1` fix(workflow): tighten visual evidence convergence
+- `9fcf407` fix(workflow): retire stale visual evidence
+- `d5a96b3` fix(spec): use absolute validator paths
+- `686dbcc` fix(workflow): tighten visual evidence freshness
+- `cc02cff` fix(workflow): align evidence helper rules
+- `66a17b9` fix(workflow): preserve explicit no-image PRs
+- `b4b24bf` fix(workflow): support canvas-only storybook
+- `fcc3d87` fix(workflow): route visual gate through step 4b
+- `7fcd6fc` fix(workflow): persist pr evidence state
+- `5c424ce` fix(workflow): persist step-4b resume state
+- `77fb1ed` fix(workflow): tighten visual evidence readiness
+- `5f91ac6` fix(workflow): restore screenshot approval guards
+- `a20d386` fix(workflow): align step-4b pr gates
+- `b39a914` docs(specs): adopt topic-level spec model
+
+## Legacy Change Log
+
+- 2026-03-24: 新建规格，锁定 shared UI visual evidence gate、Storybook 前置门禁与统一视觉证据契约。
+- 2026-03-24: 完成 shared workflow、flow skills、Storybook skills、spec 模板与新 `$ui-visual-evidence` skill 的联动更新。
+- 2026-03-24: 根据 local-merge proof 反馈补上 `聊天回图` 恢复门禁、PR 证据子集选择器，以及 legacy `PLAN.md` 持久化兼容。
+- 2026-03-24: 根据第二轮 local-merge proof 反馈补上“PR 阶段 UI fix 使视觉证据 stale 时必须回 Step 4B 重清”的续推路由。
+- 2026-03-24: 根据终版 local-merge proof 把 `PR: include` 收紧为显式白名单，并允许 canvas-only Storybook 仓库在稳定 story 入口下通过 Step 3F。
+- 2026-03-24: 根据后续 proof 补上“spec 关联 UI 在 Step 4 必须已落盘”与“新 section 无 PR 标记时仍可回退旧 `## Visual Evidence (PR)`”两条兼容门禁。
+- 2026-03-24: 根据续推 proof 补上 `证据落盘` 的恢复门禁，并把 Storybook 截图区分为 local-review-only 与 PR-bound 两种后续动作。
+- 2026-03-24: 根据最新 proof 把 `PR: include` 固定为新 section 内的唯一 PR 白名单，并允许选择器与图片之间保留一行说明文字。
+- 2026-03-24: 根据收尾 proof 放宽“已提交本地验收图”的 PR 复用路径，并把 legacy fallback 收紧为“仅新 section 为空时兜底”，避免误丢图或误带图。
+- 2026-03-24: 根据最终 proof 把 legacy `## Visual Evidence (PR)` 明确收窄为“迁移期 PR 旧源”，禁止 owner-only 图片写回该 block，并要求在没有 `PR: include` 之前继续从 legacy block 兜底 PR 图片。
+- 2026-03-24: 根据末轮 proof 补上“非 UI 任务也必须经由 `$ui-visual-evidence` 落 `不适用`”以及“local-merge proof 产新提交后需回 Step 4B 重清视觉证据”的收口约束。
+- 2026-03-24: 根据追加 proof 补上“主人拒绝 PR 放图时 legacy fallback 也必须停用”“PR 同回合 fix commit 也要回 Step 4B 重清证据”以及“Step 4B 对非 UI 任务同样是必经清门禁”三条一致性约束。
+- 2026-03-25: 根据重试 proof 补上 legacy `PLAN.md` 资产路径修正，并要求历史 `## Visual Evidence (PR)` 在出现新截图后必须同步退役或刷新，避免继续发布旧图。
+- 2026-03-25: 根据最新 proof 把 stale 规则收紧为“仅渲染面/输入变更或真正修复提交才使证据失效”，并允许纯证据落盘提交把同一批图片重新绑定到新 `latest_sha`。
+- 2026-03-25: 根据最新 proof 补上 `pr-create` 的成功条件约束，要求 `UI-affecting` PR run 在当前 `PR.head.sha` 上仍保持 Step 4B clear 后才能宣告 `Step 5C Ready`。
+- 2026-03-25: 根据后续 proof 把 `$ui-visual-evidence` 的 stale 规则与 shared workflow 对齐，并为 legacy `PLAN.md` 明确 `./assets` 资产落盘目录，避免元数据提交误触发重采或 legacy plan 截图路径悬空。
+- 2026-03-25: 根据后续 proof 区分“显式无图 PR”与“Spec视觉证据缺失”，要求 PR 路径保留 `PR截图原因=显式无图PR` 的单独语义。
+- 2026-03-25: 根据后续 proof 补上高风险 run 在纯证据落盘提交后也要刷新最终 `HEAD` 的 `pre-PR local proof`，避免 Step 4 用过期 proof 收口。
+- 2026-03-25: 根据后续 proof 放宽 AGENTS 顶层 Storybook 前置表述以兼容 canvas-only 仓库，并为 `pr-create` 明确 legacy `PLAN.md` 的 PR 截图资产目录。
+- 2026-03-25: 根据后续 proof 修正 Step 4 的门禁顺序，明确视觉证据 hard gate 只能在 `Step 4B` 生效，避免在进入 4B 前被 4A 提前阻断。
+- 2026-03-25: 根据后续 proof 补上 merge-path 在真正 merge 前也要复核 Step 4B freshness，并要求 PR 阶段停靠时持久化 Step 4B 状态字段供续推恢复。
+- 2026-03-25: 根据后续 proof 为 `视觉证据=不适用` 的非 UI spec/plan PR 单独保留 `PR截图原因=视觉证据不适用`，避免误报缺图。
+- 2026-05-05: 根据 PR #20 暴露的问题补上 PR body 图片规范化失败态：裸文件名、repo-relative 图片路径或 fenced code block 路径列表不能算有效截图，必须改写成 GitHub blob Markdown image。
+- 2026-05-29: 将 Web UI 视觉证据来源改为对象分流：组件/片段继续走 Storybook 前置门禁，完整页面/流程默认走合格 `ui_demo`，缺少 `ui_demo` 时才 fallback 到完整页面级 Storybook。
+- 2026-05-29: 同步 `pr-create` 截图 metadata 合同，允许 PR 证据保留 `source_type=ui_demo`，避免完整页面 demo 证据被迫伪装成 `mock_ui`。
+- 2026-05-29: 修正 Step 3F 通过条件，允许缺少合格 `ui_demo` 的页面级 Storybook fallback 使用 `storybook_docs` 或 `storybook_canvas` 作为证据目标源。
+- 2026-06-21: 根据 thread `019ee3e9-5cef-7b62-9d4d-8a484d03e278` 暴露的偏航，补上“主人显式要求 `web demo` / `ui_demo` 后不得被 Storybook 顶替”的锁定合同，并把整页/流程 Storybook fallback 收紧为“先明确缺少合格 `ui_demo`”后的合法兜底路径。
+- 2026-07-20: 根据 PR 图片坏链路复盘，把 `PR: none` 固定为 preferred `## Visual Evidence` section 唯一合法的显式无图语义，并收紧为“有图却无 selector 一律阻断”；自然语言 `Recommended PR subset...` 不再兼容解析。
+- 2026-07-20: 新增 `skills/github-pr-body-images/scripts/pr_body_image_gate.py`、单元测试与 contract-check，要求 Phase A / Phase B 都以 helper + GitHub `bodyHTML` 为最终验证面；Phase B 失败只记 `PR图片最终化=失败`，不回滚 merged PR。
+- 2026-08-04: 根据 Chat 图片不显示复盘，补上 owner-facing Chat Markdown/HTML 图片 Stop hook 门禁，并明确 Chat snapshot path 与 PR GitHub URL 只能复用同一逻辑资产集，不能复用同一 Markdown URL。
+
+## References
+
+- `./SPEC.md`
+- `./IMPLEMENTATION.md`
+- `../../adr/0003-task-scoped-pr-visual-evidence.md`
+
+## Related Changes
+
+- [ADR 0004](../../adr/0004-scope-authority-and-topic-spec-boundaries.md) records the boundary between normative visual assets and ephemeral task evidence.
+- PR and commit associations for this topic are retained here rather than in `SPEC.md`.
+- The canonical topic-Spec checker now rejects execution, status, PR-list, command-list, and unresolved-decision section headings while preserving workflow prose as requirements context.

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/IMPLEMENTATION.md

@@ -0,0 +1,133 @@
+# Shared UI visual evidence gate 实现状态
+
+> 当前有效规范仍以 `./SPEC.md` 为准；这里记录实现覆盖、交付进度与 rollout 相关事实，避免这些细节散落到 PR / Git 历史里。
+
+## Current Status
+
+- Implementation: 已实现
+- Lifecycle: active
+- Catalog note: UI 证据门禁与任务级 PR 图片链路已实现，并由标准库测试与 replay contract check 覆盖。
+- Adopted target contract: Phase A 接收 Task Evidence Set 或 `--no-evidence`，生成可见受管 PR `## Visual Evidence` section；Phase B 只从该 section 重绑 merge SHA URL。
+- PR body image normalization: Phase A receives explicit Task Evidence Set paths or `--no-evidence`; Phase B strictly parses the one managed PR section and verifies live `bodyHTML`.
+- Comparison lifecycle: candidates pair with Git blobs at the same destination path in `FlowLedger.base_sha`; RGBA-safe decoding and heatmaps remain, while current-only or unreadable pairs require confirmation.
+- Owner comparison report: `bin/create_reg_cli_report.py` uses explicitly supplied existing chat snapshots as symlinked inputs to one multi-pair `reg-cli` report. Sources may come from any valid repo scope; the output report follows the current repository's repo/date asset layout and canonical slug/hash scope. It records dependency paths and hashes for audit; no input image is copied into a report. Inputs must match the snapshot generator's repo/date/timestamp path layout, be independent regular files, and not resolve through any casing of `reg-cli-reports`. Source hashes are checked after rendering, immediately before publication, and immediately after the final atomic rename; a failed post-rename check removes only the report directory whose inode identity was recorded before publication. Report HTML, JSON, manifest, and diff files must also be independent regular files; audit enforces one link per generated artifact. Audit repeats snapshot-layout and hard-link checks, and detects later content changes, but does not authenticate a coordinated same-UID rewrite of a report and manifest. Creation rejects symlinked report-path components, unsafe report tokens, and replaced staging directories; creation and audit reject misplaced reports, extra snapshot inputs, incomplete HTML entries, symlinked generated outputs, unexpected diff or top-level artifacts, and manifest paths outside the asset root. Audit checks dependency path components before applying `..`, so a symlink-plus-parent traversal cannot normalize away an escape; relative audit paths retain their cwd-relative CLI semantics. Result lists must be unique and partition every pair. Diff artifacts are checked against pinned `reg-cli` `diffItems` semantics, including JPEG-to-PNG diff filenames; owner confirmation still shows the applicable baseline/current images and heatmaps in chat, with HTML as an additional view.
+- Sandbox boundary: committed package and lock files pin `reg-cli` and transitive integrity. npm installs with scripts disabled from the official registry in a private staging-local home/cache, with network available only during install; that phase cannot read comparison inputs or source snapshots. The report phase is offline. The Seatbelt profile confines forked renderer workers to the same executable, network, read, and staging-write rules, and inherited custom CA path variables are not passed into the sandbox. It denies file-content reads and directory enumeration under user homes, `/private/tmp`, `/private/var/tmp`, other temp stores, mounted volumes, keychains, and non-runtime third-party tool roots, then reopens exact runtime paths and, only for offline comparison, staging and snapshot paths; metadata needed to resolve allowlisted paths remains readable. After the runner exits, staging is atomically renamed. Validated report, JSON, and diff outputs are APFS copy-on-write cloned into a fresh publication directory outside the runner's writable scope; original input snapshots remain symlinks. The clone set and snapshot hashes are validated before publication, while sandbox hard-link creation to source images remains denied. The sandbox staging is removed. The runner fails closed unless macOS `/usr/bin/sandbox-exec` and filesystem cloning are available. This macOS-only implementation and its tradeoffs are recorded in [ADR 0022](../../adr/0022-sandboxed-reg-cli-report-execution.md).
+
+## Historical Rollout Snapshot
+
+- Legacy status snapshot: 已实现
+- Legacy created: 2026-03-24
+- Legacy last-tracked: 2026-03-24
+- Current lifecycle: active
+- Catalog note: 为 UI-affecting 工作新增组件/片段 Storybook 前置门禁、`ui_demo` 整页证据分流与本地视觉证据回传/落盘契约
+
+## Delivery Milestones
+
+- [x] M1: 建立 `docs/specs/shared-ui-visual-evidence-gate/SPEC.md` 规格并登记索引
+- [x] M2: 为 shared workflow 与 flow skills 增加 Storybook/视觉证据门禁
+- [x] M3: 新增 `$ui-visual-evidence` 并升级 Storybook 相关 skill 契约
+- [x] M4: 更新 spec 模板、技能索引与 PR 证据晋升规则
+- [x] M5: 增加 owner-facing Chat Markdown/HTML 图片 Stop hook 与 replay/单元测试
+- [x] M6: 在 Chat 视觉证据与 PR 证据复用规则中明确“同资产集、不同 Markdown URL”
+- [x] M7: 实现任务级 PR gate、同路径比较器、touched-file 文档迁移器与 PostToolUse hook
+
+## Rollout Artifacts
+
+### Docs touched
+
+- `AGENTS.md`
+- `skills/project-engineering-workflow/SKILL.md`
+- `skills/normal-flow/SKILL.md`
+- `skills/fast-flow/SKILL.md`
+- `skills/local-merge-flow/SKILL.md`
+- `skills/flow-continue/SKILL.md`
+- `skills/storybook-stories/SKILL.md`
+- `skills/storybook-stories/agents/openai.yaml`
+- `skills/storybook-screenshots/SKILL.md`
+- `skills/storybook-screenshots/agents/openai.yaml`
+- `skills/ui-visual-evidence/SKILL.md`
+- `skills/ui-visual-evidence/agents/openai.yaml`
+- `skills/topic-spec/SKILL.md`
+- `skills/topic-spec/templates/SPEC.md`
+- `skills/topic-spec/templates/legacy/PLAN.md`（legacy compatibility only）
+- `skills/project-engineering-workflow/references/pr-publication-procedure.md`
+- `skills/project-engineering-workflow/references/pr-merge-procedure.md`
+- `skills/ui-visual-evidence/SKILL.md`
+- `skills/ui-visual-evidence/scripts/pr_body_image_gate.py`
+- `skills/ui-visual-evidence/scripts/test_pr_body_image_gate.py`
+- `skills/ui-visual-evidence/replay/cases.json`
+- `skills/README.md`
+- `docs/specs/README.md`
+- `bin/visual_evidence_replay_check.py`
+- `docs/specs/pr-skill-diagnosis-thinning/replay/*`
+- `bin/pr_body_image_contract_check.py`
+- `docs/specs/shared-ui-visual-evidence-gate/replay/*`
+- `bin/owner_facing_image_gate.py`
+- `bin/test_owner_facing_image_gate.py`
+- `docs/specs/local-chat-image-snapshots/replay/cases.json`
+- `hooks.json`
+
+### Plan assets
+
+- Directory: `docs/specs/shared-ui-visual-evidence-gate/assets/`
+- In-plan references: None
+- Visual evidence source: not used for this docs/skill change
+
+### Asset promotion
+
+None
+
+## Related Changes
+
+- `e8d633b` feat(workflow): add ui visual evidence gate
+- `43a545f` fix(workflow): unify visual evidence section
+- `3ccadcb` fix(workflow): repair visual evidence continuation
+- `ce9708d` fix(flow): reroute stale ui evidence
+- `47f117b` fix(workflow): harden visual evidence contracts
+- `2162cfc` fix(workflow): preserve visual evidence sources
+- `eba6468` fix(flow): align screenshot continuation
+- `6ccbb70` fix(workflow): finalize visual evidence migration
+- `6a086cb` fix(workflow): relax visual evidence reuse
+- `afeddc2` fix(workflow): preserve legacy screenshot migration
+- `f6e92bb` fix(workflow): close visual evidence gates
+- `2d32ba1` fix(workflow): tighten visual evidence convergence
+- `9fcf407` fix(workflow): retire stale visual evidence
+- `d5a96b3` fix(spec): use absolute validator paths
+- `686dbcc` fix(workflow): tighten visual evidence freshness
+- `cc02cff` fix(workflow): align evidence helper rules
+- `66a17b9` fix(workflow): preserve explicit no-image PRs
+- `b4b24bf` fix(workflow): support canvas-only storybook
+- `fcc3d87` fix(workflow): route visual gate through step 4b
+- `7fcd6fc` fix(workflow): persist pr evidence state
+- `5c424ce` fix(workflow): persist step-4b resume state
+- `77fb1ed` fix(workflow): tighten visual evidence readiness
+- `5f91ac6` fix(workflow): restore screenshot approval guards
+- `a20d386` fix(workflow): align step-4b pr gates
+- `b39a914` docs(specs): adopt topic-level spec model
+- Current policy update: route full-page visual evidence through `ui_demo`
+- Current policy update: allow PR screenshot metadata to preserve `source_type=ui_demo`
+- Current policy update: allow page-level Storybook fallback to report Storybook evidence sources only when no qualified `ui_demo` exists and an existing explicit page-level exception authorizes it
+- Current policy update: owner-explicit non-Storybook evidence sources stay locked; Storybook cannot masquerade as a satisfied `web demo` / `ui_demo` requirement
+- Current policy update: full-page/page-flow Storybook fallback requires both an explicit “no qualified `ui_demo`” outcome and an existing explicit page-level exception, not just Storybook availability
+- Current policy update: focused replay coverage now guards owner-locked non-Storybook replacement, full-page Storybook chosen before `ui_demo` availability is resolved, and full-page fallback without an explicit exception
+- Legacy policy update: PR image publishing runs through `pr_body_image_gate.py`, with selectors and `bodyHTML` as its final render gate; selector discovery is replaced by the adopted task-scoped contract.
+- Legacy policy update: Phase A binds open-PR image URLs to `headRepository + headRefName`; Phase B binds merged-PR URLs to `baseRepository + mergeCommit.oid` with a bounded `0s` / `10s` / `30s` retry only for recoverable finalization failures
+- Accepted target contract: task-scoped PR visual evidence is recorded in ADR 0003 and implemented by the listed helpers and hooks
+- Current policy update: owner-facing Chat Markdown/HTML images now require readable immutable snapshot paths; the Stop hook retries one repair and then blocks instead of falling back to remote images
+- Current policy update: Chat and PR reuse the same logical visual asset set only, with Chat snapshot paths and PR GitHub URLs kept separate
+
+## Remaining Gaps
+
+- Runtime installation still requires the owner-approved `/hooks` trust activation; until then, the final PR document check remains the hard gate.
+- Live GitHub Phase A/Phase B execution requires the normal PR flow credentials and an available open/merged PR.
+
+## Contract Checker Coverage
+
+- `bin/spec_contract_check.py` validates the canonical visual workflow Spec while allowing normative PR/Phase language.
+- Current Task Evidence Set membership, PR body selections, and Phase A/B receipts remain runtime facts owned by the existing visual and PR skills.
+
+## References
+
+- `./SPEC.md`
+- `./HISTORY.md`
+- `../../adr/0003-task-scoped-pr-visual-evidence.md`

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/SPEC.md

@@ -0,0 +1,80 @@
+# Shared UI visual evidence gate
+
+## Context and Scope
+
+This topic defines the durable separation between owner-facing visual assets, task evidence, and PR image publication. It covers the shared workflow from Storybook or UI evidence collection through PR Phase A and merged-PR Phase B. It does not define unrelated UI implementation or a current task's evidence set.
+
+## Terms and Interfaces
+
+- `Task Evidence Set`: deduplicated repo-relative image paths explicitly selected for one task; it is ephemeral Phase A input.
+- `Managed PR Evidence Section`: the single visible `## Visual Evidence` section generated in a PR body and consumed by Phase B.
+- `Same-Path Baseline`: the image blob at the same repo-relative path in the locked base commit; absence is reported as current-only.
+- Interfaces: `$ui-visual-evidence`, the `pr_body_image_gate.py` Phase A/B helper, and `bin/visual_evidence_document.py migrate`.
+
+## Requirements
+
+### REQ-UIEVIDENCE-001
+
+The workflow MUST keep `SPEC.md` `Visual Evidence` limited to normative owner-facing assets. A Task Evidence Set MUST remain an ephemeral task input and MUST NOT become a persistent Spec grouping or PR selector.
+
+### REQ-UIEVIDENCE-002
+
+Phase A MUST accept exactly one explicit selection form: repeated `--evidence <repo-relative-image-path>` or `--no-evidence`. It MUST reject missing, mixed, empty, non-normalized, or non-current image selections and MUST generate or replace the one managed PR `## Visual Evidence` section.
+
+### REQ-UIEVIDENCE-003
+
+Phase B MUST read only the existing managed PR `## Visual Evidence` section, bind its URLs to `baseRepository + mergeCommit.oid`, and MUST NOT rediscover images from Specs, Plans, history, or hidden metadata.
+
+### REQ-UIEVIDENCE-004
+
+Visual comparison MUST pair candidate images only with the same repo-relative path in the locked base commit, report RGBA differences and heatmaps, and preserve `current-only` or unreadable facts without guessing an unrelated baseline.
+
+### REQ-UIEVIDENCE-005
+
+The workflow PR publication and merge procedures MUST call the shared image gate for Phase A/B. Retired `PR: include/none` selectors and `## Visual Evidence (PR)` headings MUST be migrated only in documents already modified by the current task, without deleting assets or creating a migration-only task.
+
+### REQ-UIEVIDENCE-006
+
+When a meaningful visual change needs owner confirmation and readable same-path baselines exist, the workflow MUST provide one `reg-cli` HTML report covering all comparable pairs. Report inputs MUST be symlinks to existing immutable chat snapshots rather than additional image copies. A source MUST match the snapshot generator's `<repo-scope>/YYYY/MM/DD/<UTC-timestamp>-<name>-<token>` layout, with the filename date matching its date directory; arbitrary files under the asset root MUST NOT be accepted. Snapshot files MUST be independent regular files, not hard-link aliases. Files under any case spelling of a generated `reg-cli-reports` subtree MUST NOT be accepted as snapshot inputs. Each explicitly supplied source MAY come from a different valid repo scope; the output report's canonical repo scope is derived from the current repository directory using the snapshot generator's slug-and-hash format. Reports MUST live under the existing `$CODEX_HOME/user-inline-assets/<repo-scope>/YYYY/MM/DD/` layout with a dependency manifest and an audit path for detecting missing or modified snapshots. Creation and audit MUST enforce the repository/date layout and reject symlinked report-path components. The HTML report MUST include every comparable pair. Creation MUST verify every source snapshot still matches its captured SHA-256 digest after rendering, immediately before publication, and immediately after the atomic publication rename. If the post-rename check fails, creation MUST remove the just-published report only when its directory identity still matches the identity recorded before publication, then fail. Audit MUST continue to detect later snapshot modifications. Generated report, JSON, manifest, and diff artifacts MUST be independent regular files with one hard link, not symlinks or hard-link aliases; diff outputs MUST match the `diffItems` manifest and contain no unlisted files. Audit MUST reject report directories, dependency paths, and manifest filenames that resolve outside the asset root. The report does not replace the RGBA/heatmap facts or owner-facing image set required by `REQ-UIEVIDENCE-004`: before confirmation, show applicable baseline images, current images, and every available heatmap in chat, with the HTML report as an additional inspection view. Removing or modifying a referenced snapshot invalidates the report. The pinned `reg-cli` package and every transitive dependency MUST be version- and integrity-locked in a committed npm lockfile. Installation MUST use `npm ci`, the official npm registry, and disabled lifecycle scripts. Both phases MUST run inside an OS sandbox whose canonical writable scope is limited to report staging; network access MUST be denied during report generation and may be enabled only for installation. The install phase MUST NOT read staging inputs or source snapshots. Sandbox reads MUST deny file contents and directory enumeration under user home directories, temporary stores, mounted volumes, keychains, and non-runtime third-party tool roots, with explicit data access restored only for the private install runtime or, during comparison, staging, source snapshots, and required Node/npm runtime paths. Metadata reads needed to resolve allowlisted paths may remain available. Temporary files, npm cache, and process logs MUST stay in staging. The sandbox may allow process-fork when required by the pinned renderer, but all descendants MUST remain under the same filesystem, executable, and network restrictions. After the runner exits, staging MUST be atomically renamed before validation. Generated regular-file outputs MUST be APFS copy-on-write cloned into a fresh publication directory outside the sandbox write scope, then validated and published from that independent inode set; input snapshots MUST remain symlinks, and unsupported filesystems MUST fail closed rather than copy them. Creation and audit MUST reject any unexpected top-level report artifact. Unsupported platforms or missing sandbox support MUST fail closed without running `reg-cli` unsandboxed.
+
+## Verification
+
+### VER-UIEVIDENCE-001
+
+- Method: visual-evidence gate unit/replay tests and `python3 bin/visual_evidence_document.py migrate` fixtures.
+- covers: `REQ-UIEVIDENCE-001`, `REQ-UIEVIDENCE-005`
+- Pass condition: normative Spec assets remain separate from task/PR selection and touched-file migration preserves legacy compatibility.
+
+### VER-UIEVIDENCE-002
+
+- Method: `skills/ui-visual-evidence/scripts/test_pr_body_image_gate.py` and Phase A/B contract checks.
+- covers: `REQ-UIEVIDENCE-002`, `REQ-UIEVIDENCE-003`
+- Pass condition: explicit selection, managed-section replacement, merge URL rebinding, and no fallback discovery are enforced.
+
+### VER-UIEVIDENCE-003
+
+- Method: `skills/ui-visual-evidence/scripts/compare_visual_evidence.py` fixtures.
+- covers: `REQ-UIEVIDENCE-004`
+- Pass condition: same-path RGBA comparison reports dimensions, heatmap, current-only, and unreadable outcomes without crashing.
+
+### VER-UIEVIDENCE-004
+
+- Method: On macOS with `/usr/bin/sandbox-exec`, Node, and npm, run `REG_CLI_INTEGRATION=1 python3 bin/test_create_reg_cli_report.py` with the pinned `reg-cli` package.
+- covers: `REQ-UIEVIDENCE-006`
+- Pass condition: multiple snapshot pairs produce one readable HTML report containing every pair through symlink inputs, no input images are copied into the report, derived report files are rejected as future inputs, changed source hashes prevent publication, the complete npm dependency graph has integrity lock data, install and offline report execution are separately sandboxed, writes outside staging and through source symlinks or hard links are denied, directory enumeration under sensitive roots including `/Users` and `/private/var/tmp` is denied, detached writers cannot mutate published output inodes, unsupported platforms or filesystems fail closed, invalid report layouts, noncanonical repo scopes, symlinked paths or outputs, hard-linked report artifacts, duplicate result items, and unlisted input/diff/top-level artifacts are rejected, and audit detects missing or modified dependencies.
+
+## Related ADRs
+
+- [Task-scoped PR visual evidence](../../adr/0003-task-scoped-pr-visual-evidence.md)
+- [Scope authority and topic Spec boundaries](../../adr/0004-scope-authority-and-topic-spec-boundaries.md)
+- [PR Lifecycle Workflow Ownership](../../adr/0016-pr-lifecycle-workflow-ownership.md)
+- [Sandboxed reg-cli report execution](../../adr/0022-sandboxed-reg-cli-report-execution.md)
+
+## Visual Evidence
+
+- None. This section is reserved for normative owner-facing assets; current task selections are supplied to Phase A explicitly.
+
+## References
+
+- `./IMPLEMENTATION.md`
+- `./HISTORY.md`

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/cases.txt

@@ -0,0 +1,64 @@
+fail negative-owner-locked-web-demo-replaced-by-storybook.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-owner-lock-survives-blocker-before-storybook.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-owner-locked-english-ui-demo-replaced-by-storybook.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-before-ui-demo-check.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-mixed-component-then-full-page-storybook.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+pass positive-component-storybook-allowed.jsonl -
+fail negative-full-page-storybook-fallback-without-explicit-exception.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+pass positive-user-allows-storybook-after-no-ui-demo.jsonl -
+pass positive-project-documentation-page-storybook-exception.jsonl -
+pass positive-active-spec-page-storybook-exception.jsonl -
+pass positive-full-page-storybook-current-approval-supersedes-denial.jsonl -
+pass positive-full-page-storybook-with-unqualified-ui-demo.jsonl -
+fail negative-full-page-storybook-exception-does-not-leak.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-after-qualified-ui-demo.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-not-authorized.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-exception-before-route-does-not-leak.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-generic-page-request-does-not-leak.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-not-yet-approved.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-question-about-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-english-not-yet-approved.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-english-question-about-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-mixed-ui-demo-state.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-double-negated-ui-demo.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-unrelated-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-conditional-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-chinese-unrelated-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-long-negation.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-unrelated-release-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-page-scoped-authorization.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-page-state-resets-with-component.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-disallowed-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-disapproved-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-unapproved-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-only-after-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+pass positive-full-page-storybook-can-use-grant.jsonl -
+pass positive-full-page-storybook-owner-lock-is-page-scoped.jsonl -
+pass positive-full-page-storybook-owner-lock-revoked.jsonl -
+fail negative-full-page-storybook-unrelated-fallback-revocation.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-other-page-source-revocation.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-page-absence-does-not-leak.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-ambiguous-multi-page-route.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-cross-sentence-condition.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-denial-is-page-scoped.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+pass positive-component-only-page-context.jsonl -
+fail negative-full-page-storybook-owner-lock-after-component.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-no-exception-after-component.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+pass positive-owner-locked-page-component-storybook.jsonl -
+fail negative-full-page-storybook-multiple-owner-locks.jsonl LOCKED_NON_STORYBOOK_SOURCE_REPLACED_BY_STORYBOOK
+fail negative-full-page-storybook-conditional-exception-followup.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+pass positive-full-page-storybook-qualified-ui-demo-unavailable.jsonl -
+fail negative-full-page-storybook-conditional-ui-demo-absence.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-conditional-ui-demo-absence-chinese.jsonl FULL_PAGE_STORYBOOK_BEFORE_UI_DEMO_CHECK
+fail negative-full-page-storybook-after-owner-approval.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-trailing-page-denial.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-full-page-storybook-multi-page-grant-inherits.jsonl FULL_PAGE_STORYBOOK_FALLBACK_WITHOUT_EXPLICIT_EXCEPTION
+fail negative-local-pr-before-owner-confirmation.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+fail negative-confirmation-invalidated-by-candidate-change.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+fail negative-implementation-approval-is-not-visual-confirmation.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+fail negative-visual-rejection-is-not-acceptance.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+fail negative-mixed-visual-status-cannot-clear-confirmation.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+fail negative-same-event-visual-request-and-pr-route.jsonl UI_PR_CONVERGENCE_BEFORE_VISUAL_RESPONSE
+pass positive-local-confirmation-before-pr.jsonl -
+pass positive-unchanged-visual-evidence-before-pr.jsonl -
+pass positive-legacy-card-is-ignored.jsonl -

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-confirmation-invalidated-by-candidate-change.jsonl

@@ -0,0 +1,4 @@
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉比较=需确认，已展示当前截图与差异热图。这些截图准确反映了本次改动吗？"}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"这些截图准确反映了当前改动。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"候选渲染已变化，需要重新比较。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"开始 PR 收敛。"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-after-owner-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; this full page can use Storybook fallback after owner approval."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-after-qualified-ui-demo.jsonl

@@ -0,0 +1,4 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"先确认当前页面的验收范围。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=ui_demo"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前有合格 ui_demo，但仍使用完整页面级 Storybook fallback。"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-ambiguous-multi-page-route.jsonl

@@ -0,0 +1,2 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"The owner requires checkout page evidence to come from ui_demo. Also update the settings page."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"Using Storybook fallback for the requested pages.\n视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-before-ui-demo-check.jsonl

@@ -0,0 +1,4 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"请刷新这个完整页面的最终视觉证据。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"这是整页 page-flow 取证。"}]}}
+{"type":"response_item","payload":{"type":"function_call","name":"exec_command","arguments":"{\"cmd\":\"sed -n '1,220p' skills/storybook-screenshots/SKILL.md\"}"}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"我先走 Storybook，把整页图补出来。"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-chinese-unrelated-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前没有合格 ui_demo；项目文档不允许该页面使用 Storybook fallback，但发布已获批准。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-conditional-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; the full page is approved for Storybook fallback only if the owner approves it."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-conditional-exception-followup.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists. This full page is allowed to use Storybook fallback. This exception is conditional on owner approval."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-conditional-ui-demo-absence-chinese.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"如果没有合格 ui_demo，请先检查项目。项目文档明确允许这个完整页面使用 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-conditional-ui-demo-absence.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"If no qualified ui_demo exists, check the project. The owner explicitly allows this full page to use Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-cross-sentence-condition.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; this full page is allowed to use Storybook fallback. This approval takes effect only after the owner approves it."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-denial-is-page-scoped.jsonl

@@ -0,0 +1,2 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; the checkout page is approved for Storybook fallback, but the settings page is not authorized to use fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"settings page uses Storybook fallback.\n视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-disallowed-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; this full page is disallowed from using Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-disapproved-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; this full page is disapproved for Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-double-negated-ui-demo.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"并非没有合格 ui_demo；项目文档允许这个完整页面走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前页面直接使用完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-english-not-yet-approved.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo；this full page is not yet approved for Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-english-question-about-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo；can the full page be approved for Storybook fallback?"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-exception-before-route-does-not-leak.jsonl

@@ -0,0 +1,5 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"先整理这个完整页面的状态与验收路径。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"另一个完整页面需要最终视觉证据。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"直接使用完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-exception-does-not-leak.jsonl

@@ -0,0 +1,6 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"另一个完整页面需要最终视觉证据。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-fallback-without-explicit-exception.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"这个完整页面需要最终视觉证据。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-generic-page-request-does-not-leak.jsonl

@@ -0,0 +1,5 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"先整理这个完整页面的状态与验收路径。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"请检查账户设置页面。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"直接使用完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-long-negation.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; The owner will not, after reviewing the evidence in detail, allow this full page to use Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-mixed-ui-demo-state.jsonl

@@ -0,0 +1,4 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以走 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"先确认当前页面的验收范围。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前曾缺少合格 ui_demo，但现在存在合格 ui_demo，视觉证据目标源=ui_demo。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前仍使用完整页面级 Storybook fallback。"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-multi-page-grant-inherits.jsonl

@@ -0,0 +1,2 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists for both the checkout page and the settings page; the checkout page is approved for Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"Using Storybook fallback for both requested pages, including the checkout page.\n视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-multiple-owner-locks.jsonl

@@ -0,0 +1,2 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"The owner requires checkout page evidence to come from ui_demo. The owner requires settings page evidence to come from ui_demo. No qualified ui_demo exists for the settings page; the settings page is approved for Storybook fallback."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"settings page uses Storybook fallback.\n视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-no-exception-after-component.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists for the checkout page."}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"For the checkout page, update only the reusable header component."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"checkout page uses Storybook fallback. 视觉证据目标源=storybook_canvas; 视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-not-authorized.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面可以不使用 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-not-yet-approved.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"当前缺少合格 ui_demo，这个完整页面未批准使用 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-only-after-approval.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists; this full page is allowed to use Storybook fallback only after the owner approves it."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"当前缺少合格 ui_demo，需要完整页面级 Storybook fallback。"}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"视觉证据目标源=storybook_canvas\n视觉证据=存在"}]}}

package/toolkit/skills/docs/vendor/dot-codex/specs/shared-ui-visual-evidence-gate/replay/negative-full-page-storybook-other-page-source-revocation.jsonl

@@ -0,0 +1,3 @@
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"The owner requires checkout page evidence to come from ui_demo."}]}}
+{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":"No qualified ui_demo exists for checkout page; the checkout page is approved for Storybook fallback. I withdraw the settings page ui_demo source requirement."}]}}
+{"type":"response_item","payload":{"type":"message","role":"assistant","content":[{"type":"output_text","text":"checkout page uses Storybook fallback. 视觉证据目标源=storybook_canvas; 视觉证据=存在"}]}}