@dailephd/my-frontend-observer 0.9.1 → 0.10.1

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.

package/docs/reports/v0.10-pre-release-readiness.md

@@ -0,0 +1,120 @@
+# v0.10 Pre-release Readiness
+
+## Provisional verdict
+
+RUN_A passed on the corrected validation candidate. This report is intentionally
+provisional: it is shipped by the package `files` allowlist, so committing it
+changes candidate bytes. A complete RUN_B against the report-containing HEAD is
+required before the final readiness verdict may be declared.
+
+## Repository and release state
+
+- Repository: `my-frontend-observer`
+- Validation branch: `validation/v0.10-pre-release`
+- Validation entry HEAD: `ce8bf7c7b0060b35cfb2fdd850c7a80ff0b340ad`
+- RUN_A HEAD: `b1c273d853dd9f00394b355522d06c344252e928`
+- Package: `@dailephd/my-frontend-observer@0.9.1`
+- Latest npm-published version: `0.9.1`
+- v0.10 release/tag/publication: not performed
+- Implementation-completeness reconciliation: `ce8bf7c7b0060b35cfb2fdd850c7a80ff0b340ad`
+
+## Local validation before RUN_A
+
+The canonical local chain passed on the corrected HEAD: `npm ci`, Chromium
+installation, typecheck, lint, unit tests (99 files / 1,524 tests), browser
+tests (32 files / 301 tests), security tests, isolated PWA hard gate, build,
+documentation check, `git diff --check`, and `npm pack --dry-run`.
+
+The local security result was PASS. The isolated PWA hard gate passed independently
+and also through the security command, preserving active-worker, controlled-page,
+shell-precache, zero-API-cache, server-down, offline-shell, unavailable-evidence,
+and stale-identity assertions.
+
+## RUN_A
+
+- Workflow: `Pre-release readiness`
+- Run ID: `35785226212`
+- URL: https://github.com/dailephd/my-frontend-observer/actions/runs/35785226212
+- Event: push
+- Branch: `validation/v0.10-pre-release`
+- Exact HEAD: `b1c273d853dd9f00394b355522d06c344252e928`
+- Conclusion: PASS
+
+All seven required jobs passed:
+
+| Job | Result |
+| --- | --- |
+| Package exact candidate (Linux, Node 24) | PASS |
+| ubuntu-latest exact-candidate smoke | PASS |
+| windows-latest exact-candidate smoke | PASS |
+| macos-latest exact-candidate smoke | PASS |
+| ubuntu-latest Observer tutorial readiness | PASS |
+| windows-latest Observer tutorial readiness | PASS |
+| macos-latest Observer tutorial readiness | PASS |
+
+## Exact candidate and matrix proof
+
+- Candidate filename: `dailephd-my-frontend-observer-0.9.1.tgz`
+- Candidate package version: `0.9.1`
+- Candidate SHA-256: `bda75f4f5ca441b3f58f9fe6ffa535f41904608a783961db8bcef4171f353ef5`
+- Independently downloaded/recomputed SHA-256: identical
+- Windows, Linux, and macOS each verified the candidate SHA and used the same tarball.
+- Each OS uploaded `smoke-summary.json`, `viewer-smoke-summary.json`,
+  `v09-annotation-smoke-summary.json`, and `v010-workflow-smoke-summary.json`.
+
+The four packed smokes passed on every OS: observation, Viewer/project workflow,
+v0.9 annotation, and v0.10 visual workflow. The v0.10 summaries prove installed
+package workflow creation/activation, two-attempt immutable correction history,
+non-PASS rejection and PASS acceptance, reference bindings, Viewer discovery,
+standalone read-only behavior, and absence of authoring token, note text, absolute
+project/temp paths, and orchestrator paths.
+
+The three tutorial-readiness jobs also passed, preserving the v0.9 tutorial
+regression on Windows, Linux, and macOS.
+
+## Security and package audit
+
+RUN_A exercised the existing formal security suite and PWA hard gate in the
+candidate job. The added v0.10 attack surface remains bounded by loopback,
+Host/Origin/token, JSON/body/compression, path-containment, immutable-parent,
+handoff-privacy, standalone-read-only, and orchestrator-non-authority controls.
+
+The candidate retained package version `0.9.1`, Viewer protocol `1.3.0`, all
+governed schema versions, and no dependency/schema/version changes. Package
+contents were audited locally for compiled v0.10 exports and Viewer assets, with
+tests, generated state, browser profiles, summaries, and nested tarballs excluded.
+
+## Failed-run history and correction
+
+Earlier same-HEAD runs are retained as historical diagnosis:
+
+1. Run `35780908327` exposed hosted browser flakes in an existing screenshot
+   comparison and materialization toast assertion; it was cancelled after the
+   candidate failed and its matrix was not promoted.
+2. A same-HEAD rerun reproduced the materialization toast synchronization issue.
+   The test was corrected to rely on the already asserted HTTP 201 response and
+   exact canonical artifact reselection.
+3. Run `35783718376` then exposed a separate Chromium adapter flake and a
+   macOS-only packed activation failure.
+4. The packed smoke was corrected to canonicalize its disposable temp root before
+   deriving relative artifact paths. Local validation passed, and RUN_A above
+   passed all seven jobs on the corrected candidate.
+
+No product semantics, governed schema, dependency, package version, or readiness
+workflow architecture changed.
+
+## RUN_B requirement
+
+This tracked report changes the npm candidate bytes because `docs/` is included
+in the package. Commit it with:
+
+`docs: record v0.10 pre-release readiness`
+
+Push the resulting `REPORT_HEAD` to this validation branch and require a new
+complete `Pre-release readiness` run whose exact HEAD equals `REPORT_HEAD`.
+RUN_B must independently pass the candidate job, all three exact-candidate smoke
+lanes, and all three tutorial-readiness lanes. Only then may the overall verdict
+become `PASS_V0_10_PRERELEASE_READY_FOR_RELEASE_PREP`.
+
+Release operations performed: none. Version bump, tag, publication, merge, and
+GitHub Release remain unauthorized and incomplete.

package/docs/reports/v0.10-release-preparation.md

@@ -0,0 +1,70 @@
+# v0.10.0 Release Preparation
+
+## 1. Verdict and identity
+
+Verdict: `PASS_READY_TO_PUBLISH_AFTER_USER_APPROVAL`
+
+Repository: `dailephd/my-frontend-observer` (`C:\Users\daile\Projects\my-frontend-observer`)
+Workflow: `RELEASE_PREPARATION`
+Source validation branch: `validation/v0.10-pre-release`
+Starting RUN_B-validated SHA: `4ae5b9e0328364dd27e0761b8f243093bdcb3f45`
+Inherited RUN_B: `35789033295`, workflow `Pre-release readiness`, conclusion success. Its seven required jobs all succeeded. Readiness was inherited; RUN_B was not rerun.
+Release branch: `release/v0.10.0`, created directly from the exact validated SHA without merge or rebase.
+Package: `@dailephd/my-frontend-observer`
+Old package version: `0.9.1`
+Target package version: `0.10.0`
+
+## 2. Release-state preflight
+
+- npm current version before preparation: `0.9.1`.
+- npm `0.10.0`: absent (npm returned E404 for the exact version).
+- Local `v0.10.0` tag: absent.
+- Remote `origin` `v0.10.0` tag: absent.
+- GitHub Release `v0.10.0`: absent.
+- Local and remote `release/v0.10.0` branches: absent before creation.
+- GitHub identity: `dailephd/my-frontend-observer`, default branch `master`; `gh auth status` succeeded.
+- `package.json` identity: `@dailephd/my-frontend-observer`.
+
+## 3. Version and documentation state
+
+`package.json` version, `package-lock.json` version, and `package-lock.json` `packages[""]` version are all `0.10.0`. The version was changed with `npm version 0.10.0 --no-git-tag-version`; no version commit or tag was created by npm.
+
+The changelog keeps `## [Unreleased]` for future work and adds `## 0.10.0 - 2026-09-23` describing the shipped Visual Change workflow, actual/reference entry, artifact/handoff versions, explicit activation, bounded coding-agent handoff, immutable correction history, PASS-only acceptance, separate governance, installed-package/Viewer support, and security boundaries.
+
+README identifies v0.10.0 as current and accurately describes the normal user-facing Visual Change workflow. `docs/CURRENT_STATE.md` records the current release, complete shipped workflow, formal Windows/Linux/macOS readiness, package version, independently versioned schemas, and Viewer protocol. `docs/ROADMAP.md` changes only the high-level v0.10 release status and preserves future-version planning. `docs/PROJECT_OVERVIEW.md`, `docs/RELEASE.md`, `docs/CI_CD.md`, `docs/SECURITY.md`, and `docs/QUICKSTART.md` state the final v0.10 release and readiness facts while retaining relevant security limitations. Commands, workflows, contracts, and architecture semantics were not changed.
+
+`docs/reports/v0.10-pre-release-readiness.md` was preserved unchanged. The existing `scripts/check-docs.mjs` was narrowly updated to enforce final release consistency: a dated 0.10.0 changelog entry plus an Unreleased section, current package/release/readiness/protocol facts, roadmap release status, and canonical contract markers. It was not disabled and no second checker was added. `npm run check:docs` passed after the change.
+
+## 4. Source, dependencies, schemas, and package
+
+Production source audit: `git diff -- src viewer/src` is empty; no executable product changes were made. Dependency audit: `dependencies` and `devDependencies` are identical to the starting commit (`DEPENDENCY_CHANGED = false`).
+
+Schema/protocol inventory is unchanged: observation `1.2.0`; comparison `1.0.0`; frontend contract `1.0.0`; evaluation `1.0.0`; bounded-agent-context `1.0.0`; external-reference `1.0.0`; visual annotation `1.0.0`; visual-change-workflow `1.0.0`; handoff `1.0.0`; Viewer protocol `1.3.0`.
+
+Package hygiene: `.gitignore` excludes `node_modules/`, `dist/`, and the `.my-dev-kit-*` generated workflow/context roots. No `.npmignore` is present. `package.json#files` allowlists `dist`, README, CHANGELOG, docs, and LICENSE. `npm pack --dry-run` reports package `@dailephd/my-frontend-observer@0.10.0`, 437 files in the final dry run (436 before adding this report), and includes compiled visual-change workflow owners, Viewer/PWA assets, README, changelog, and release docs. The JSON dry-run content audit found no tests, private workflow/context roots, caches, browser profiles, smoke summaries, nested tarballs, or `node_modules`. No tarball was created by the dry run.
+
+## 5. Local validation
+
+All requested commands passed after release-preparation edits:
+
+- `npm run typecheck`: PASS.
+- `npm run lint`: PASS.
+- `npm test`: PASS, 99 files and 1,524 tests.
+- `npm run test:browser`: PASS, 32 files and 301 tests.
+- `npm run test:security`: PASS, including 16 security unit files (168 tests), 3 browser files (77 tests), and the PWA hard gate.
+- `npm run test:pwa-hard-gate`: PASS, one hard-gate test; six unrelated tests filtered by the task's script.
+- `npm run build`: PASS.
+- `npm run check:docs`: PASS (17 required documentation files).
+- `git diff --check`: PASS.
+- `npm pack --dry-run`: PASS, package identity/version and content audit as above.
+- `node dist/cli.js --version`: `0.10.0`.
+- `node dist/cli.js --help`: PASS; expected command surface displayed.
+
+## 6. Git, publication boundary, and handoff
+
+Release-preparation commit message: `chore: prepare v0.10.0 release`.
+Push target: `origin release/v0.10.0`. The commit is pushed and the post-push check confirms the remote branch matches the local release-preparation commit. The tracked worktree is clean after push. The final commit SHA and branch tip are recorded in the handoff summary.
+
+No product-semantic changes, dependency changes, tag, GitHub Release, npm publication, dist-tag change, PR, or merge were made. The historical pre-release readiness report was not edited. Generated build output remains ignored; no local/private generated files are staged or packaged.
+
+Exact next action: await explicit user approval. After approval, run the standardized GitHub release + final npm publication workflow from `release/v0.10.0`. The publication workflow must create/validate the release PR, merge it, validate master, create/push `v0.10.0`, create/verify the GitHub Release, verify release-channel parity, and run `npm publish --access public` as the final state-changing command.

package/docs/reports/v0.10.1-project-check-baseline-context-implementation.md

@@ -0,0 +1,86 @@
+# v0.10.1 Project Check Baseline Context Replay — Implementation Report
+
+## Result
+
+At implementation completion, the bounded maintenance fix was recorded at
+`82dc7745b1935b827a57870ff9a942d166d4cca5` on
+`fix/v0.10.1-project-check-baseline-context`, while package version `0.10.0`
+remained unchanged. This report preserves that implementation-time snapshot;
+formal readiness passed later, and release-preparation state is tracked in
+`docs/RELEASE.md`.
+
+## Defect and correction
+
+Project-aware `check` validated an immutable baseline before capture, but the candidate capture used only the project configuration. When the baseline carried `requestConfig.scrollScenario` or `requestConfig.explicitState`, the candidate omitted those dimensions and could be classified as incomparable even when rendered evidence had no differences.
+
+After baseline validation, `checkProject` now derives an optional, narrow replay context from the validated baseline artifact and passes only `scrollScenario` and `explicitState` to candidate capture. Current project configuration still owns URL, viewport, semantic targets, and ordinary capture defaults. The canonical request normalization and browser observation path remain responsible for validation and actual scroll execution. Unrelated baseline request fields are not replayed.
+
+`scrollScenario` replay executes the same bounded browser scroll action. `explicitState` replay retains caller-declared identity metadata only; it does not establish theme, application, authentication, cookie, storage, or session state. No state inference or setup was added. Controlled state/session setup remains future v0.12 scope.
+
+## Changed owners and preserved boundaries
+
+The implementation extends `src/application/projectCheckService.ts` and the existing candidate capture path in `src/application/projectWorkflowService.ts`, with unit, workflow, and real-Chromium regression coverage. It does not alter the comparison rules or weaken comparability.
+
+At implementation completion, project config remained schema `1.1.0` and rejected top-level `scrollScenario` and `explicitState`. Normal `init` and `capture` remained project-config-driven. The machine-facing CLI remained `check <baseline> --json`; no flags were added. Observation schema remained `1.2.0`; comparison schema remained `1.0.0`; check-result schema remained `1.0.0`. Viewer protocol was unchanged. No dependency was added, and package version was `0.10.0`.
+
+## Verification evidence
+
+The implementation acceptance run recorded:
+
+- Typecheck, lint, build: PASS.
+- Unit tests: 1,527 passed.
+- Browser tests: 302 passed.
+- Security tests: 170 unit and 78 browser tests passed.
+- PWA hard gate: PASS.
+- Real-Chromium project-check reproducer: baseline and candidate retained both low-level dimensions; the bounded scroll action executed; check returned `PASS`, comparison was comparable with zero differences, configured contract passed, and blockers were empty.
+- Negative target-scroll case: missing/incompatible project target fails through the existing honest blocked/failure path.
+- Project-config boundary, immutable baseline, and current-history regressions: PASS.
+
+Downstream consumer validation used the unchanged `iworkhere.space` candidate `b0ee1bb251571ce2f83b08c55285a12ee68dc4c4` with this maintenance implementation. Five document routes at desktop `1440×900` and mobile `390×844` produced 10/10 passing Observer checks, comparable results, zero differences, and passing configured contracts. This proves the original missing-context blocker is removed for that consumer candidate; it is not a release claim for iworkhere.space v0.3.0.
+
+## Release lifecycle at implementation completion
+
+At this report's implementation-time snapshot, current published release and
+package version were `0.10.0`. Documentation reconciliation and the packed-
+readiness coverage correction were complete, while formal readiness, release
+preparation, version bump, publication, PR, and merge had not occurred. These
+are historical lifecycle facts; subsequent release state is recorded in
+`docs/CURRENT_STATE.md` and `docs/RELEASE.md`.
+
+## Pre-readiness packed-acceptance coverage correction
+
+PRE_READINESS_PACKED_ACCEPTANCE_GAP: FOUND. The existing packed project/viewer
+smoke exercised installed `check` but did not include a baseline carrying both
+`scrollScenario` and `explicitState`. Source/unit/browser validation and the
+downstream consumer smoke did not close that installed-tarball acceptance gap.
+
+Correction: `scripts/ci/runPackedViewerSmoke.mjs`, the existing installed
+project/viewer smoke owner, now creates a canonical low-level observation with
+both dimensions through the installed CLI, registers its generated identities
+in the existing schema-1.0.0 catalog, and checks it using installed
+`check <baseline> --json` with no added flags. The assertion requires real
+scroll evidence, matching candidate request context, a comparable zero-
+difference result, passing configured contract, no blockers, and immutable
+baseline/source/configuration. The smoke summary records bounded v0.10.1
+acceptance fields. The existing three-OS matrix already invokes this same
+smoke on the one frozen tarball, so readiness workflow architecture is
+unchanged.
+
+PRODUCT_SOURCE_CHANGED: NO
+READINESS_WORKFLOW_ARCHITECTURE_CHANGED: NO
+At the time of this packed-acceptance correction, formal v0.10.1 readiness had
+not yet run; local packed regression was validation evidence only.
+
+### Local exact-packed-candidate evidence
+
+One local `0.10.0` tarball was installed and exercised by the existing packed
+observation, Viewer/project, v0.9 annotation, and v0.10 workflow smokes. The
+updated `runPackedViewerSmoke.mjs` passed on Windows and wrote
+`viewer-smoke-summary.json`; its `projectCheckBaselineContextReplay` section
+records check exit 0/PASS, comparable/zero differences, contract PASS, zero
+blockers, both context matches, real baseline/candidate scroll to 240,
+immutable baseline/source/configuration, and current-only alias advancement.
+Exact local tarball identity and summaries are retained in project-local
+workflow evidence.
+
+Validation after this correction: typecheck PASS; lint PASS; 1,527 unit tests PASS; 302 browser tests PASS; security 170 unit + 78 browser tests PASS; the nested PWA hard-gate invocation PASS; build PASS; docs check PASS. No hosted workflow or formal readiness run was started.