@dailephd/my-frontend-observer 0.9.0 → 0.10.0

package/docs/reports/v0.10-batch7-correction-review-acceptance.md

@@ -0,0 +1,145 @@
+# v0.10 Batch 7 Correction, Review, and Acceptance
+
+## Verdict and correction history
+
+PASS. The initial result remained `NEEDS_CORRECTION` because production was green but the frozen acceptance evidence was incomplete. This continuation preserved that implementation and added the missing canonical, browser, identity, and governance proofs. No production redesign was required.
+
+- Repository: `C:\Users\daile\Projects\my-frontend-observer`
+- Starting commit: `5db4d93bc5e39812da694aedbbc4f51de152114e`
+- Branch: `feature/v0.10-full-visual-workflow`
+- Package remains `0.9.1`.
+- my-dev-kit: `1.12.4`, pinned and CLI-verified under `.my-dev-kit-workflow/tools/v0.10-batch7-correction/`.
+- Fresh correction index: `.my-dev-kit-context/indexes/my-frontend-observer-v0.10-batch7-correction-20260922`; `src viewer/src tests scripts`, call graph, 317 files, 2,559 symbols, 4,979 edges, zero top-level warnings/errors. Data-model/classification were partial (872/2,509 warnings); frontend analyzers were complete.
+
+## Result
+
+The pure cycle owner derives initial, review-required, correction-requested, accepted, and abandoned without schema persistence. Check and handoff share it. Review owns `decidedAt`, changes only the latest review in an immutable child, preserves request/attempt/candidate/check identity, uses active-scope readiness for correction and acceptance, and accepts only the latest canonical PASS. Abandon is terminal without requiring active acceptance. Restore remains separately explicit.
+
+Applicable reference checks reuse `buildReferenceCorrectionReviewIdentity` and `buildReferenceCorrectionAttemptIdentity`; `checkProject` runs once and `reviewReferenceCorrectionAttempt` is not called. Orchestrator metadata is non-authoritative.
+
+Governance records only already-persisted canonical results after acceptance. The baseline proof calls `approveAndPersistBaseline` for the exact accepted candidate before recording it. The reference proof imports a successor and calls `approveExternalReference` with the exact frozen predecessor before recording it. Both create immutable workflow children, reject mismatch/overwrite, preserve parents, and leave project configuration unchanged. Acceptance itself leaves governance absent and calls no approval or restore owner.
+
+The independent Chromium ACCEPTANCE GATE owns a mutable loopback frontend. External edit 1 passes the requested shrink but fails protected rail width, so canonical checking records FAIL and pending review blocks check/handoff/Accept. Request correction creates an immutable child. External edit 2 produces distinct candidate/attempt IDs, immediate lineage, PASS, and acceptance. The original active manifest bytes remain unchanged; governance remains absent; acceptance is not restored; continuation becomes terminal.
+
+Canonical reference precedence is proved by `Proof B: the external actor satisfies the reference but introduces a protected regression - overall FAIL`. The reference visual-workflow test then proves one check per candidate, common deterministic v0.7 review identity, distinct reference attempt identities, lineage, and PASS-only acceptance. Existing Proof C independently exercises two real canonical reference candidates.
+
+## TST-B7-001..087 responsibility ledger
+
+Abbreviations: `service` = `tests/unit/visualChangeAgentHandoffService.test.ts`; `viewer` = `tests/unit/viewerVisualChangeAuthoring.test.ts`; `actual-gate` = `tests/browser/visualChangeCorrectionAcceptance.test.ts`; `reference-proof` = `tests/browser/referenceCorrectionWorkflow.test.ts`.
+
+- TST-B7-001 — service — “derives the canonical cycle and rejects review with zero attempts” — existing-covered — no-attempt review rejected.
+- TST-B7-002 — service — “enforces terminal transitions and permits abandonment…” — existing-covered — pending FAIL to correction.
+- TST-B7-003 — service — “accepts only the latest canonical PASS…” — existing-covered — pending PASS to correction.
+- TST-B7-004 — service — “accepts only the latest canonical PASS…” — existing-covered — pending PASS accepted.
+- TST-B7-005 — service — “rejects non-PASS acceptance…” — existing-covered — FAIL rejected.
+- TST-B7-006 — service — “rejects non-PASS acceptance…” — existing-covered — BLOCKED rejected.
+- TST-B7-007 — service — “rejects non-PASS acceptance…” — existing-covered — REVIEW_REQUIRED rejected.
+- TST-B7-008 — service — “enforces terminal transitions…” — existing-covered — pending abandoned.
+- TST-B7-009 — service — “enforces terminal transitions…” — existing-covered — correction abandoned.
+- TST-B7-010 — service — “enforces terminal transitions…” — existing-covered — correction cannot accept.
+- TST-B7-011 — service — “runs the explicit FAIL -> correction -> PASS loop…” — existing-covered — accepted terminal.
+- TST-B7-012 — service — “enforces terminal transitions…” — existing-covered — abandoned terminal.
+- TST-B7-013 — service — “accepts only the latest canonical PASS…” — existing-covered — server decidedAt.
+- TST-B7-014 — service — same test — existing-covered — attempt ID unchanged.
+- TST-B7-015 — service — same test — existing-covered — candidate/check/recordedAt unchanged.
+- TST-B7-016 — service — same test — existing-covered — fresh workflow ID.
+- TST-B7-017 — service — same test — existing-covered — request ID preserved.
+- TST-B7-018 — service — same test — existing-covered — child supersedes parent.
+- TST-B7-019 — service — “runs the explicit FAIL -> correction -> PASS loop…” — existing-covered — parent bytes unchanged.
+- TST-B7-020 — actual-gate — “ACCEPTANCE GATE: external FAIL edit…” — newly-covered — first check allowed.
+- TST-B7-021 — service — “blocks check and handoff while pending…” — existing-covered — second check blocked.
+- TST-B7-022 — service — same test — existing-covered — handoff blocked.
+- TST-B7-023 — service — same test — existing-covered — correction enables handoff.
+- TST-B7-024 — actual-gate — ACCEPTANCE GATE — newly-covered — correction enables check.
+- TST-B7-025 — service — explicit loop — existing-covered — immediate prior ID.
+- TST-B7-026 — actual-gate — ACCEPTANCE GATE — newly-covered — candidate IDs differ.
+- TST-B7-027 — actual-gate — ACCEPTANCE GATE — newly-covered — attempt IDs differ.
+- TST-B7-028 — actual-gate — ACCEPTANCE GATE — newly-covered — request ID stable.
+- TST-B7-029 — service — explicit loop — existing-covered — new attempt pending.
+- TST-B7-030 — service — explicit loop — existing-covered — accepted blocks check.
+- TST-B7-031 — service — explicit loop — existing-covered — accepted blocks handoff.
+- TST-B7-032 — service — terminal-transition test — existing-covered — abandoned blocks check.
+- TST-B7-033 — service — terminal-transition test — existing-covered — abandoned blocks handoff.
+- TST-B7-034 — service — “runs the reference two-candidate correction gate…” — newly-covered — canonical review builder.
+- TST-B7-035 — service — same test — newly-covered — canonical attempt builder.
+- TST-B7-036 — viewer — “keeps every POST project-aware…closed…” — existing-covered — browser supplies no trace ID.
+- TST-B7-037 — service — reference two-candidate test — newly-covered — one check per attempt/no second evaluator.
+- TST-B7-038 — service — same test — newly-covered — distinct reference attempt IDs.
+- TST-B7-039 — service — same test — newly-covered — common review request ID.
+- TST-B7-040 — service — “projects canonical reference fidelity…not-applicable…” — existing-covered — omitted when inapplicable.
+- TST-B7-041 — actual-gate — ACCEPTANCE GATE — newly-covered — requested PASS/protected FAIL stores FAIL and blocks Accept.
+- TST-B7-042 — reference-proof — “Proof B: … protected regression - overall FAIL” plus service reference loop — newly-covered — fidelity PASS/contract FAIL/accept rejected.
+- TST-B7-043 — service — latest-PASS test — existing-covered — earlier PASS cannot authorize latest FAIL.
+- TST-B7-044 — service — latest-PASS test — existing-covered — only latest PASS accepted.
+- TST-B7-045 — service — non-PASS/orchestrator test — existing-covered — coordination cannot authorize.
+- TST-B7-046 — service — same test — existing-covered — no orchestrator invocation.
+- TST-B7-047 — actual-gate — ACCEPTANCE GATE — newly-covered — no baseline approval on accept.
+- TST-B7-048 — actual-gate — ACCEPTANCE GATE — newly-covered — no reference approval on accept.
+- TST-B7-049 — service — canonical governance tests — existing-covered — acceptance/config separation.
+- TST-B7-050 — actual-gate — ACCEPTANCE GATE — newly-covered — no automatic restore.
+- TST-B7-051 — service — governance tests — existing-covered — pre-acceptance record rejected.
+- TST-B7-052 — service — “records only a canonically approved candidate-matching baseline…” — newly-covered — approval service succeeds first.
+- TST-B7-053 — service — same test — newly-covered — matching approval recorded.
+- TST-B7-054 — service — same test — newly-covered — unrelated observation rejected.
+- TST-B7-055 — service — same test — newly-covered — baseline overwrite rejected.
+- TST-B7-056 — service — “records a canonically approved superseding reference…” — newly-covered — approval owner succeeds first.
+- TST-B7-057 — service — same test — newly-covered — exact successor recorded.
+- TST-B7-058 — service — same test — newly-covered — unrelated successor rejected.
+- TST-B7-059 — service — same test — newly-covered — reference overwrite rejected.
+- TST-B7-060 — service — same test — existing-covered — actual mode rejects reference result.
+- TST-B7-061 — service — governance tests — existing-covered — immutable child.
+- TST-B7-062 — service — governance tests — existing-covered — parent unchanged.
+- TST-B7-063 — service — governance tests — newly-covered — config unchanged.
+- TST-B7-064 — service — governance tests — newly-covered — recording performs no approval.
+- TST-B7-065 — actual-gate — ACCEPTANCE GATE — newly-covered — Request correction shown.
+- TST-B7-066 — actual-gate — ACCEPTANCE GATE — newly-covered — Abandon shown.
+- TST-B7-067 — actual-gate — ACCEPTANCE GATE — newly-covered — PASS Accept enabled.
+- TST-B7-068 — actual-gate — ACCEPTANCE GATE — newly-covered — FAIL Accept disabled.
+- TST-B7-069 — viewer — closed POST test — existing-covered — decision-only request.
+- TST-B7-070 — actual-gate — ACCEPTANCE GATE — newly-covered — exact child reselection.
+- TST-B7-071 — actual-gate — ACCEPTANCE GATE — newly-covered — correction continuation UI.
+- TST-B7-072 — actual-gate — ACCEPTANCE GATE — newly-covered — accepted terminal UI.
+- TST-B7-073 — viewer — Viewer workflow test — existing-covered — abandoned terminal UI.
+- TST-B7-074 — actual-gate — ACCEPTANCE GATE — newly-covered — no auto restore.
+- TST-B7-075 — viewer — Viewer workflow test — existing-covered — accepted governance section.
+- TST-B7-076 — viewer — closed POST test — existing-covered — exact evidence handle.
+- TST-B7-077 — viewer — Viewer workflow test — existing-covered — governance exact reselection.
+- TST-B7-078 — viewer — secured closed POST test — existing-covered — no token/path leak.
+- TST-B7-079 — `tests/unit/visualChangeWorkflow.test.ts` — workflow identity suite — shared-regression-covered.
+- TST-B7-080 — `tests/unit/visualChangeProjectWorkflowService.test.ts` — activation/check suite — shared-regression-covered.
+- TST-B7-081 — `tests/unit/viewerAuthoringSecurity.test.ts` — Viewer/security suite — shared-regression-covered.
+- TST-B7-082 — `tests/browser/visualChangeActualEntry.test.ts` — actual entry gate — shared-regression-covered.
+- TST-B7-083 — `tests/browser/visualChangeReferenceEntry.test.ts` — reference entry gate — shared-regression-covered.
+- TST-B7-084 — `tests/browser/visualChangeHandoff.test.ts` — handoff acceptance — shared-regression-covered.
+- TST-B7-085 — `tests/unit/projectBoundedAgentContext.test.ts` — bounded-context suite — shared-regression-covered.
+- TST-B7-086 — reference-proof — Proof A/B/C suite — shared-regression-covered.
+- TST-B7-087 — `tests/unit/viewerProtocol.test.ts` — protocol 1.3.0 — shared-regression-covered.
+
+Every responsibility has a named passing test; none is implementation-only coverage.
+
+## Validation
+
+- Focused actual gate: PASS, 1/1.
+- Focused canonical project/reference files: PASS, 2 files / 11 tests.
+- Focused service/review/governance/reference identity: PASS, 15/15.
+- `npm run typecheck`: PASS.
+- `npm run lint`: PASS.
+- `npm test`: PASS, 99 files / 1,524 tests.
+- `npm run test:browser`: PASS after additions, 31 files / 281 tests.
+- `npm run test:security`: PASS (168 unit security tests, 77 browser tests, nested hard gate PASS).
+- `npm run test:pwa-hard-gate`: PASS independently. The state-based active/scope/controller/precache/no-API-cache/server-down/offline/no-stale-evidence/cleanup proof remains intact.
+- `npm run build`: PASS; PWA 1.3.0, 10 precache entries.
+- `npm run check:docs`: PASS after this update.
+- `git diff --check`: PASS after this update.
+
+Visual-change and bounded-agent-context schemas remain `1.0.0`; all other governed schemas are unchanged; Viewer protocol remains `1.3.0`.
+
+## Full-file read accounting
+
+Full source/test file reads: none. Retrieval used my-dev-kit search, lookup, slices/exact source, dependency expansion, and bounded ranges.
+
+Correction-run additional full source/test file reads: none.
+
+## Batch 8 exclusion and handoff
+
+No Batch 8 integrated matrix, packaging, release reconciliation, version bump, readiness, PR, merge, tag, or publication work was performed. Exact next action is separately authorized Batch 8 execution from the committed Batch 7 result.

package/docs/reports/v0.10-batch8-integrated-acceptance.md

@@ -0,0 +1,109 @@
+# v0.10 Batch 8 Integrated Acceptance
+
+## 1. Verdict and repository
+
+`IMPLEMENTATION_COMPLETE` / PASS. This is not a release-readiness verdict.
+
+- Repository: `C:\Users\daile\Projects\my-frontend-observer`
+- Branch: `feature/v0.10-full-visual-workflow`
+- Starting commit: `325ae3eebc8f3b6f6a828615c6970c1aee0c9dd0`
+- Package version: `0.9.1`
+- v0.10 release state: unreleased
+- my-dev-kit: `1.12.4`
+- Fresh index: `.my-dev-kit-context/indexes/my-frontend-observer-v0.10-batch8-20260922`; 318 files, 2,567 symbols, 4,989 edges, zero top-level warnings/errors. Data-model/classification were partial with 872/2,517 warnings; frontend analyzers were complete.
+
+No production behavior changed. Batch 8 added integration aggregation, installed-package proof, CI wiring, and implementation documentation.
+
+## 2. Integrated scenario matrix
+
+1. Actual-frontend visual entry: PASS in `runtimeAnnotationContractPromotion.test.ts` ACCEPTANCE GATE.
+2. Reference-driven visual entry: PASS in `referenceAnnotationMaterialization.test.ts` ACCEPTANCE GATE.
+3. Measurable reference failure: PASS in `referenceCorrectionWorkflow.test.ts` Proof A/B and `projectCheckWorkflow.test.ts` fidelity mapping.
+4. Requested success plus protected regression: PASS in `visualChangeCorrectionAcceptance.test.ts`.
+5. Fidelity PASS plus contract FAIL: PASS in `referenceCorrectionWorkflow.test.ts` Proof B.
+6. Two-attempt immutable correction: PASS in `visualChangeCorrectionAcceptance.test.ts` and reference Proof C.
+7. Explicit latest-PASS acceptance: PASS in the correction ACCEPTANCE GATE.
+8. Governance separation: PASS in Batch 7 service integration and the correction ACCEPTANCE GATE.
+9. Optional orchestrator correlation: PASS in handoff service tests and the packed workflow smoke; it does not change request identity or acceptance.
+10. Standalone Viewer read-only: PASS in `visualChangeWorkspace.test.ts` and the packed smoke.
+11. v0.7-v0.9.1 regression safety: PASS through the normal unit/browser/security/PWA suites and the three legacy packed smokes.
+
+`tests/browser/v010IntegratedAcceptance.test.ts` is the single Batch 8 entrypoint. It composes the existing independently owned fresh-state gates and passed 20/20 tests.
+
+## 3. Packed pre-version-bump implementation candidate
+
+- Filename: `dailephd-my-frontend-observer-0.9.1.tgz`
+- Version: `0.9.1`
+- SHA-256: `282a240790c65344c539fb9d1650bd6d6cc4efca4e43ad6d7a6432b4da5ce9f2`
+- Location: `.my-dev-kit-workflow/v0.10-batch8/packed-candidate/`
+- Exactly one `npm pack` created the candidate. The hash was independently checked before each smoke.
+- Packed observation smoke: PASS.
+- Packed Viewer smoke: PASS.
+- Packed v0.9 annotation smoke: PASS.
+- Packed v0.10 workflow smoke: PASS.
+- Summaries: `observation-summary.json`, `viewer-summary.json`, `v09-summary.json`, and `v010-summary.json` under the generated candidate directory.
+
+The new smoke installed only the exact tarball into a clean consumer. Its programmatic imports resolve from consumer `node_modules`, not the source checkout. It exercised installed public constants/validators/readers, actual workflow creation and activation, handoff serialization, FAIL rejection, correction, a linked PASS attempt, acceptance, reference workflow creation with persisted bindings, real-Chromium Visual changes discovery, standalone read-only behavior, and parent/evidence immutability. The summary asserts absence of authoring tokens, note text, absolute project/temp paths, and orchestrator paths.
+
+## 4. CI same-candidate wiring
+
+The candidate job remains the only `npm pack` owner. `matrix-smoke` still downloads that tarball and verifies the candidate SHA before installed-package work. It now runs `runPackedV010WorkflowSmoke.mjs` after the v0.9 smoke and uploads `v010-workflow-smoke-summary.json` in the existing `smoke-summary-${{ matrix.os }}` artifact. No second candidate, artifact family, or matrix was added. Wiring exists; formal cross-platform v0.10 readiness has not been run or claimed.
+
+## 5. Published orchestrator compatibility
+
+Published `@dailephd/my-dev-kit-orchestrator@1.4.1` was resolved dynamically and CLI-verified. Disposable run `20260922T143421-batch8-proof` referenced the generated Observer handoff. Status honestly remained at request-brief with 0/10 artifacts and a blocked final report. Export retained run/request identity. Handoff bytes were unchanged. Observer imports no orchestrator runtime, reads no run directory, and grants no acceptance from orchestrator state.
+
+## 6. Documentation and release state
+
+CURRENT_STATE, ROADMAP, README, WORKFLOWS, COMMANDS, ARCHITECTURE, CONTRACTS, CI/CD, RELEASE guidance, and CHANGELOG `[Unreleased]` now distinguish implementation completion from release. The published package remains 0.9.1. v0.10 is not released. Hardened documentation/implementation-completeness reconciliation, formal cross-platform/security readiness, release preparation, version bump, tag, and publication remain pending.
+
+## 7. Validation
+
+Responsibility mapping:
+
+- TST-B8-001..018: the runtime/reference entry ACCEPTANCE GATEs, correction
+  ACCEPTANCE GATE, handoff service suite, and Batch 7 governance suite.
+- TST-B8-019..024: reference-correction Proof A/B/C, project-check fidelity
+  mapping, persisted reference-attempt identity test, and non-PASS review tests.
+- TST-B8-025..026: visual-change workspace standalone inspection tests and the
+  installed standalone Viewer proof.
+- TST-B8-027..042: `runPackedV010WorkflowSmoke.mjs`, including clean install,
+  installed exports/owners, actual/reference creation, activation, two attempts,
+  PASS-only acceptance, immutable bytes, Viewer modes, and leakage assertions.
+- TST-B8-043..052: the one recorded candidate/hash, four same-hash smoke
+  summaries, and additive same-candidate workflow wiring.
+- TST-B8-053..064: documentation reconciliation plus `check:docs` and the
+  `[Unreleased]`/package-version assertions.
+- TST-B8-065..074: normal reference-correction, Viewer, project-check,
+  annotation, isolated PWA, full Batch 1-7 suites, protocol/schema tests, and
+  installed public-contract checks.
+- TST-B8-075..079: dynamically resolved orchestrator 1.4.1, disposable run
+  `20260922T143421-batch8-proof`, status/export, dependency audit, and unchanged
+  Observer handoff identity.
+
+All TST-B8-001..079 responsibilities have passing named owners or generated
+proof evidence. No formal cross-platform readiness result is inferred from CI
+wiring.
+
+Focused integrated suite: PASS, 20/20. `npm run typecheck`, `npm run lint`,
+`npm test` (99 files, 1,524 tests), `npm run test:browser` (32 files,
+301 tests), `npm run test:security` (168 unit/security tests, 77 browser tests,
+and its isolated PWA tail), standalone `npm run test:pwa-hard-gate`, build,
+documentation check, and `git diff --check` passed. One locator capture failed
+once in the first security invocation immediately after the long browser run;
+the exact test passed alone and the complete canonical security command then
+passed, with no source change. This was classified as a transient Chromium
+lifecycle anomaly rather than a product defect.
+
+`npm pack --dry-run` passed and listed compiled v0.10 application/domain/viewer
+owners plus Viewer assets. It included no tests, generated workflow/tool state,
+consumer/profile state, smoke summaries, or nested tarball. The four
+same-candidate packed smokes and published-orchestrator compatibility passed.
+
+## 8. Full-file read accounting
+
+Authoritative documentation and historical reports were required whole-file reads. Source/test inspection used retrieval-first search, bounded source, continuation, dependency expansion, and bounded ranges. Full source/test file reads: none.
+
+## 9. Exact next action
+
+Run the separate hardened documentation and implementation-completeness reconciliation for v0.10.

package/docs/reports/v0.10-implementation-completeness-documentation-reconciliation.md

@@ -0,0 +1,344 @@
+# v0.10 Implementation Completeness and Documentation Reconciliation
+
+## 1. Verdict
+
+`PASS_V0_10_IMPLEMENTATION_COMPLETE_DOCS_RECONCILED_READY_FOR_PRERELEASE`
+
+This verdict means the frozen v0.10 implementation is complete, current
+documentation is reconciled to repository evidence, and local validation is
+green. It does not mean release-ready, publish-ready, or cross-platform-ready.
+
+## 2. Repository state
+
+- Repository: `C:\Users\daile\Projects\my-frontend-observer`
+- Branch: `feature/v0.10-full-visual-workflow`
+- Starting HEAD: `d164886dd665a140a9fc783f25c87f57cbc01ebb`
+- Ending HEAD: the documentation-reconciliation commit created after this
+  report; the final task response records its exact identity.
+- Local package: `@dailephd/my-frontend-observer@0.9.1`
+- Latest npm-published package: `0.9.1`
+- `v0.10.0` local/remote tag: absent
+- Latest GitHub Release: `v0.9.1`; no v0.10 release exists
+- v0.10 release state: implemented and documentation-reconciled, unreleased
+
+## 3. Retrieval and audit index
+
+- Resolved `@dailephd/my-dev-kit`: `1.12.4`; CLI identity matched.
+- Install: `.my-dev-kit-workflow/tools/v0.10-documentation-reconciliation/`
+- Index: `.my-dev-kit-context/indexes/my-frontend-observer-v0.10-doc-reconciliation-20260922T145706`
+- Command: `my-dev-kit index --root . --src src --src viewer/src --src tests --src scripts --language typescript --out <index> --call-graph --progress --json`
+- Result: 319 files, 2,567 symbols, 4,989 edges, zero top-level warnings/errors.
+- Partial analyzers: data-model (872 warnings) and classification (2,517
+  warnings). Syntax, call graph, frontend semantic, and frontend reachability
+  completed. Android analyzers were inapplicable; model-view lineage did not
+  run.
+
+Retrieval-first search, symbol lookup, bounded source, continuation, and local
+dependency inspection established the v0.10 owners and public surface. No
+whole source/test fallback was required.
+
+## 4. Evidence inspected
+
+All eight v0.10 implementation reports were inspected. The frozen v0.10 plan,
+documentation preservation policy, durable project description/milestones,
+all canonical current documents, README, CHANGELOG, release guidance, the two
+v0.7/v0.8 completeness-audit precedents, package metadata, Git tags, npm state,
+built CLI help, public exports, Viewer routes, tests, packed-smoke scripts, and
+the readiness workflow were inspected. Current source/tests/package evidence
+was used over historical report text wherever relevant.
+
+## 5. Package and script inventory
+
+- Package: `@dailephd/my-frontend-observer`, ESM, Node `>=24`.
+- Runtime dependency: `playwright ^1.62.1`; no my-dev-kit or orchestrator
+  runtime dependency.
+- Public bin: `my-frontend-observer -> dist/cli.js`.
+- Public export: package root -> `dist/index.js`.
+- Package allowlist: `dist`, README, CHANGELOG, `docs`, LICENSE.
+- Current scripts: prebuild, build, typecheck, lint, unit tests, browser tests,
+  security tests, isolated PWA hard gate, and documentation check.
+- Test inventory before this docs-only change: 101 unit files and 32 browser
+  files.
+
+## 6. CLI command inventory
+
+Built help exposes exactly twelve top-level commands:
+
+1. `init`
+2. `capture <alias>`
+3. `check [baseline]`
+4. `view`
+5. `observe`
+6. `compare`
+7. `approve-baseline`
+8. `save-change-contract`
+9. `evaluate-contract`
+10. `import-reference`
+11. `approve-reference`
+12. `evaluate-reference-fidelity`
+
+`--version` reports `0.9.1`. v0.10 adds no command. Visual Change actions are
+project-aware Viewer/API operations. `check <baseline> --json` remains the
+post-edit machine operation. A stale `view --help` description was corrected
+to describe the implemented guarded Visual Change mutations and explicit
+reference approval without changing behavior or flags.
+
+## 7. Viewer action and API inventory
+
+The top-level Viewer modes are Evidence, Bounded context, and Visual changes.
+Standalone `view --root` permits inspection only. Project-aware sessions may
+save annotations, promote runtime intent, materialize reference intent,
+approve an imported reference, create actual/reference workflows, activate,
+run a check, restore acceptance, prepare a handoff, review, and record an
+already-completed governance result.
+
+The v0.10 routes are:
+
+- `GET /api/visual-changes/:handle/view`
+- `POST /api/visual-changes`
+- `POST /api/visual-changes/:handle/activate`
+- `POST /api/visual-changes/:handle/check`
+- `POST /api/visual-changes/:handle/restore-acceptance`
+- `POST /api/visual-changes/:handle/prepare-handoff`
+- `POST /api/visual-changes/:handle/review`
+- `POST /api/visual-changes/:handle/governance`
+- `POST /api/annotations/:handle/start-visual-change`
+- `POST /api/references/:handle/approve`
+- `POST /api/references/:handle/start-visual-change`
+
+They reuse exact Host/Origin, memory-only token, JSON content type, compression,
+body-bound, closed-shape, containment, serialization, and no-store controls.
+
+## 8. Public programmatic API
+
+`src/index.ts` publicly exports the workflow contract/constants/validator and
+identity helpers; workflow writer/reader/persistence; project creation,
+activation, restore, snapshot, and check; handoff contract/validator/serializer
+and preparation; cycle derivation; review; and governance recording. Viewer
+adapters, HTTP handlers, route matching, and React hooks/components remain
+internal/Viewer-only. The public API is programmatic; it is not a hidden CLI
+command family.
+
+## 9. Schema and protocol inventory
+
+| Contract | Kind | Version | Source owner | Changed in v0.10 |
+|---|---|---:|---|---|
+| Observation | persisted artifact | 1.2.0 | `domain/schema.ts` | No |
+| Comparison | persisted artifact | 1.0.0 | `domain/comparison.ts` | No |
+| Frontend contract | persisted artifact | 1.0.0 | `domain/frontendContracts.ts` | No |
+| Contract evaluation | persisted artifact | 1.0.0 | `domain/frontendContractEvaluationArtifact.ts` | No |
+| Bounded agent context | transfer artifact | 1.0.0 | `domain/boundedAgentContext.ts` | No |
+| External reference | persisted artifact | 1.0.0 | `domain/externalReference.ts` | No |
+| Visual annotation | persisted artifact | 1.0.0 | `domain/visualAnnotation.ts` | No |
+| Visual change workflow | persisted artifact | 1.0.0 | `domain/visualChangeWorkflow.ts` | Yes, new |
+| Agent handoff | non-persisted transfer contract | 1.0.0 | `domain/visualChangeAgentHandoff.ts` | Yes, new |
+| Viewer protocol | HTTP/UI protocol | 1.3.0 | `viewerServer/httpServer.ts` | No |
+
+The workflow kind is
+`my-frontend-observer/visual-change-workflow`. The handoff kind is
+`my-frontend-observer/visual-change-agent-handoff`. No other persisted v0.10
+evidence family was introduced.
+
+## 10. v0.10 implementation-completeness matrix
+
+Each row gives requirement, owner/source witness, test witness, interface/docs,
+and status.
+
+| # | Requirement | Implementation/source witness | Test witness | Interface/document witness | Status |
+|---:|---|---|---|---|---|
+| 1 | Workflow artifact foundation | workflow domain, reader/writer, persistence | `visualChangeWorkflow.test.ts` | public API, CONTRACTS | IMPLEMENTED |
+| 2 | Request/workflow/attempt identities | workflow identity owner | workflow identity tests | public API, CONTRACTS | IMPLEMENTED |
+| 3 | Immutable workflow revisions | persistence service | workflow/project/review immutability tests | Visual changes, WORKFLOWS | IMPLEMENTED |
+| 4 | Project-contained activation | project workflow service | project workflow service tests | Activate action | IMPLEMENTED |
+| 5 | Canonical check attempt recording | project workflow service -> `checkProject` | project workflow/correction tests | Run check | IMPLEMENTED |
+| 6 | Visual Changes workspace | Viewer workspace/projection | workspace browser tests | project-aware `view` | IMPLEMENTED |
+| 7 | Actual visual entry | runtime authoring adapter | actual-entry and integrated browser gates | Viewer | IMPLEMENTED |
+| 8 | Reference visual entry | reference approval/authoring adapters | reference-entry and integrated gates | Viewer | IMPLEMENTED |
+| 9 | Explicit workflow bindings | reference binding domain/workflow writer | reference authoring/workspace tests | Viewer Add/Remove binding | IMPLEMENTED |
+| 10 | Handoff contract | handoff domain | handoff contract tests | public API/Viewer | IMPLEMENTED |
+| 11 | Bounded context | existing projection reused | bounded-context/handoff tests | handoff | IMPLEMENTED |
+| 12 | Supplemental static-context ownership | handoff service coherence gate | handoff service tests | explicit `--context-file` | IMPLEMENTED |
+| 13 | Optional orchestrator correlation | handoff metadata validator | handoff and review tests | Viewer optional fields | IMPLEMENTED |
+| 14 | Post-edit check command | handoff exact command | handoff/UI tests | `check <baseline> --json` | IMPLEMENTED |
+| 15 | Pending-review human gate | cycle helper/check/handoff gates | Batch 7 service/browser gates | Viewer controls | IMPLEMENTED |
+| 16 | Correction-requested loop | review service | correction acceptance gates | Viewer | IMPLEMENTED |
+| 17 | Two-attempt lineage | check append owner | actual/reference correction gates | attempt history | IMPLEMENTED |
+| 18 | PASS-only acceptance | review service | latest-PASS/non-PASS tests | Viewer Accept | IMPLEMENTED |
+| 19 | Abandon | review service | transition/terminal tests | Viewer Abandon | IMPLEMENTED |
+| 20 | Explicit restore separation | project workflow service | review/browser tests | Restore acceptance | IMPLEMENTED |
+| 21 | Reference-correction identity trace | existing v0.7 builders reused | reference two-candidate tests | attempt metadata | IMPLEMENTED |
+| 22 | Governance after canonical governance | review/governance service | canonical baseline/reference governance tests | Viewer recording actions | IMPLEMENTED |
+| 23 | Baseline/reference governance separation | canonical approval owners plus recorder | governance tests | CONTRACTS/WORKFLOWS | IMPLEMENTED |
+| 24 | Standalone read-only | server authoring state | Viewer/security/packed tests | `view --root` | IMPLEMENTED |
+| 25 | Authoring security | shared authoring gate | security suites | SECURITY | IMPLEMENTED |
+| 26 | PWA no-stale-evidence | PWA/service worker | isolated hard gate | SECURITY | IMPLEMENTED |
+| 27 | Packed installed v0.10 surface | package exports/dist | packed v0.10 smoke | CI/CD | IMPLEMENTED |
+| 28 | Same-candidate CI wiring | readiness workflow | Batch 8 same-tarball proof | CI/CD | IMPLEMENTED |
+| 29 | No source editing | service boundaries | browser/source immutability tests | ARCHITECTURE/SECURITY | IMPLEMENTED_BY_DESIGN_NO_PUBLIC_COMMAND |
+| 30 | No second evaluator | services call canonical owners | call-count/integration tests | ARCHITECTURE | IMPLEMENTED_BY_DESIGN_NO_PUBLIC_COMMAND |
+| 31 | No automatic approval/retry | explicit transitions | entry/review/governance tests | WORKFLOWS | IMPLEMENTED_BY_DESIGN_NO_PUBLIC_COMMAND |
+| 32 | v0.7-v0.9.1 regression preservation | unchanged owners | complete unit/browser/security/PWA suites | historical docs | IMPLEMENTED |
+
+No `MISSING_IMPLEMENTATION`, `MISSING_TEST`, `MISSING_DOCUMENTATION`, or
+`DOCUMENTATION_DRIFT` remains after this reconciliation.
+
+## 11. Milestone and roadmap acceptance
+
+`V0_10_MILESTONE_ACCEPTANCE: PASS`
+
+The applicable graphical interaction, visual scope, external edit, canonical
+evaluation, correction, human acceptance, evidence immutability, and ecosystem
+boundary criteria map to rows 1-32 and the Batch 4-8 acceptance gates.
+
+`V0_10_ROADMAP_ACCEPTANCE: PASS`
+
+Both entry modes converge on one frozen workflow; explicit activation,
+handoff, canonical check, review/correction, PASS-only acceptance, and separate
+governance are implemented and tested. Frozen exclusions remain excluded.
+
+## 12. Batch 1-8 gate audit
+
+| Batch | Frozen goal | Current source witness | Current test witness | Documentation witness | Status |
+|---:|---|---|---|---|---|
+| 1 | Workflow foundation | workflow domain/artifacts | workflow tests | CONTRACTS | PASS |
+| 2 | Project composition/check | project workflow service | project workflow tests | ARCHITECTURE/WORKFLOWS | PASS |
+| 3 | Viewer workspace | server projection/UI workspace | workspace/security tests | COMMANDS | PASS |
+| 4 | Actual entry | runtime start/promotion owners | actual-entry gate | WORKFLOWS | PASS |
+| 5 | Reference entry | approval/reference start owners | reference-entry gate | WORKFLOWS | PASS |
+| 6 | Agent handoff | handoff domain/service | handoff unit/browser tests | CONTRACTS | PASS |
+| 7 | Correction/review/governance | cycle/review services | correction/governance gates | WORKFLOWS | PASS |
+| 8 | Integrated/packed/docs wiring | integrated suite/smoke/CI | integrated and packed proofs | Batch 8 report/CI docs | PASS |
+
+Report PASS was not accepted alone; every row has current HEAD witnesses.
+
+## 13. Cross-version regression audit
+
+The final validation protects v0.1 observation, v0.2 semantic targets, v0.3
+scrolling/runtime behavior, v0.4 comparison, v0.5 contracts, v0.6 bounded
+context, v0.7 reference correction, v0.8 Viewer, v0.8.1 project workflow,
+v0.9 annotation, and v0.9.1 isolated PWA hard-gate behavior. Historical
+release documents were preserved.
+
+## 14. Document audit ledger
+
+| Document | Role | Changed | Claim/release/future result | Preservation |
+|---|---|---:|---|---|
+| README | first-use/current overview | Yes | reconciled v0.10 status; 0.9.1 remains published | preserved |
+| CHANGELOG | unreleased/release history | No | `[Unreleased]` already correct | all history preserved |
+| PROJECT_DESCRIPTION | durable intent | No | no stale status claim | complete authority preserved |
+| PROJECT_MILESTONES | capability/acceptance | No | requirements mapped and satisfied | complete authority preserved |
+| ROADMAP | version-level direction | Yes | reconciliation complete; readiness next | v0.1-v0.10 preserved; no batches |
+| PROJECT_OVERVIEW | concise orientation | Yes | stale future claim repaired | earlier version orientation preserved |
+| CURRENT_STATE | current facts | Yes | reconciliation complete; unreleased | historical sections preserved |
+| ARCHITECTURE | implemented ownership | Yes | stale v0.10 future claim repaired | earlier architecture preserved |
+| CONTRACTS | canonical contracts | No | workflow/handoff already accurate | all contract history preserved |
+| COMMANDS | implemented commands | Yes | project-aware writes corrected; no command invented | command families preserved |
+| WORKFLOWS | current procedures | No | complete loop already accurate | prior workflows preserved |
+| QUICKSTART | concise entry | Yes | source v0.10 vs published 0.9.1 clarified | simpler workflow preserved |
+| DEVELOPMENT | contributor workflow | No | no contradictory v0.10 status | retained |
+| CI_CD | CI/readiness boundary | No | four-smoke same-candidate wiring already accurate | retained |
+| RELEASE | release state/process | Yes | reconciliation complete; readiness pending | release history preserved |
+| SECURITY | safety boundary | Yes | v0.10 guarded mutations and external boundary added | v0.1-v0.9 controls preserved |
+| DOCUMENTATION_PRESERVATION_POLICY | authority rules | No | followed | unchanged |
+| v0.10 implementation plan | frozen plan/history | No | remains planning authority | unchanged |
+| Batch 1-8 reports | execution evidence | No | historically scoped claims retained | unchanged |
+
+## 15. Stale-claim repair ledger
+
+| Document | Old claim | Classification | Evidence | Correction |
+|---|---|---|---|---|
+| PROJECT_OVERVIEW | v0.10 future/unimplemented/planned | STALE_CLAIM | current source/tests and eight PASS batches | implemented, reconciled, unreleased; readiness next |
+| ARCHITECTURE | graphical workflow future/unimplemented | STALE_CLAIM | workflow/handoff/review owners | implemented/unreleased architecture |
+| CURRENT_STATE | reconciliation pending/next | STALE_CLAIM after this task | this audit and validation | reconciliation complete; readiness next |
+| ROADMAP | reconciliation remained next gate | STALE_CLAIM after this task | this audit | version-level reconciled status |
+| README | implemented but not reconciliation status | INCOMPLETE_CURRENT_FACT | this audit | concise reconciled/unreleased wording |
+| QUICKSTART | standalone Viewer phrasing implied all Viewer use was inspect-only | MISPLACED_DETAIL | project-aware routes/UI | distinguishes project-aware authoring from standalone |
+| COMMANDS and built `view --help` | only three v0.9 writes / never approves references | STALE_CLAIM | current route inventory | guarded v0.10 actions and explicit approval boundary |
+| SECURITY | v0.9 “any other POST” wording lacked current v0.10 extension | HISTORICAL_FACT_WITH_CURRENT_AMBIGUITY | route/security tests | scoped to v0.9 and added current v0.10 boundary |
+| RELEASE | reconciliation still pending implicitly | INCOMPLETE_CURRENT_FACT | this audit | reconciliation complete; readiness still pending |
+
+Matches in frozen plans and historical reports were classified as
+HISTORICAL_RELEASE_FACT or IMPLEMENTATION_PROMPT_RESIDUE and intentionally
+left unchanged.
+
+## 16. Planning and history preservation
+
+No document, roadmap version, future-version statement, product pillar,
+architecture subsystem, command family, workflow family, report, or release
+entry was removed. ROADMAP remains version-level and contains v0.1-v0.10 with
+no `Batch N` bookkeeping. CHANGELOG retains `[Unreleased]` and every historical
+release entry. The v0.10 plan and Batch 1-8 reports remain historical evidence.
+
+## 17. Documentation-check audit and hardening
+
+`DOC_CHECK_HARDENING: REQUIRED`
+
+The existing checker already protected all 17 required documents, ROADMAP
+v0.1-v0.10 retention, absence of Batch bookkeeping, package/lock version
+agreement, and `[Unreleased]`. It could not detect the exact regression found:
+current canonical documents could still describe completed v0.10 as future or
+leave reconciliation/readiness state contradictory.
+
+The existing `scripts/check-docs.mjs` owner now adds narrow semantic markers:
+no current v0.10 future/unimplemented claim, CURRENT_STATE implementation and
+reconciliation completion with readiness still next/pending, ROADMAP
+implementation-complete/documentation-reconciled status, and retention of both
+canonical v0.10 contract kind markers. It does not hardcode paragraphs or
+create a parallel preservation framework. `npm run check:docs` is the
+regression proof.
+
+## 18. Validation
+
+Final results are recorded after the complete post-edit run:
+
+- `npm run typecheck`: PASS
+- `npm run lint`: PASS
+- `npm test`: PASS
+- `npm run test:browser`: PASS
+- `npm run test:security`: PASS
+- `npm run test:pwa-hard-gate`: PASS
+- `npm run build`: PASS
+- `npm run check:docs`: PASS
+- targeted stale-claim search: PASS; remaining matches are historical
+- `git diff --check`: PASS
+- `npm pack --dry-run`: PASS; package remains 0.9.1 and contains compiled
+  v0.10/public Viewer assets without generated state
+
+This is local implementation/completeness validation, not formal multi-OS
+pre-release readiness.
+
+## 19. Changed and unchanged files
+
+Documentation changed: README, CURRENT_STATE, ROADMAP, PROJECT_OVERVIEW,
+ARCHITECTURE, COMMANDS, QUICKSTART, SECURITY, RELEASE, and this report.
+Documentation inspected but unchanged: CHANGELOG, PROJECT_DESCRIPTION,
+PROJECT_MILESTONES, CONTRACTS, WORKFLOWS, DEVELOPMENT, CI_CD, preservation
+policy, implementation plan, and Batch 1-8 reports.
+
+Tooling changed: the existing docs checker. Production behavior changed: none.
+Two user-facing documentation strings/comments in `src/cli.ts` and
+`src/viewerServer/httpServer.ts`, plus the existing CLI-help assertion, were
+updated to remove false route/security claims. No executable semantics changed.
+
+## 20. Change boundaries
+
+- Schema/protocol changes: none.
+- Package-version changes: none.
+- Dependency changes: none.
+- Product feature changes: none.
+- Release operations: none.
+- Remaining implementation gaps: none.
+- Remaining documentation ambiguities: none material.
+
+## 21. Exact next workflow
+
+Run the separate v0.10 pre-release readiness workflow: exact-candidate
+cross-platform validation, security validation, and readiness audit. Do not
+perform release preparation or publication yet.
+
+## 22. Full-file fallback accounting
+
+Canonical documentation and reports were inspected as documentation
+authorities. Source/test work used retrieval-first bounded inspection.
+
+Full source/test file reads: none.