unaltraweb 0.6.0 → 0.7.1

data/docs/agents/deploy-provenance-86.md

@@ -0,0 +1,86 @@
+# Independent PDF worker provenance — issue 86
+
+[Owner issue 86](https://github.com/dosquartsdedocs/unaltraweb/issues/86) records
+TIG's failed latest deployment at consumer
+`a87eb4fc7fe58f072413a99356d2465b36d05136`. Its published PDF 0.5.0 was produced
+from `d857f8c9f5fea90cf450c0b30b4e77a37b541275`, whereas its reusable workflow
+was pinned to `02af70001bf8085af860fd57f8d7e75ec96a89c7`. Comparing those two
+different component identities blocked the build before Pages publication.
+
+The original gates were re-executed with real published images: canonical 0.5.0,
+0.5.1 and 0.7.0 tuples fail; the 0.6.0 tuple passes because its two revisions
+happen to coincide. Retained diagnostic evidence is
+`/tmp/opencode/unaltraweb-deploy-86/matrix/evidence.json`, SHA-256
+`8640b7b68456b1bce42b9a0a271fe1c4853fde181eff9b3a130c990bd119142f`.
+
+## Corrected trust binding
+
+The reviewed provider workflow now owns these exact digest/producer records:
+
+| PDF worker | OCI digest | Producer commit |
+| --- | --- | --- |
+| 0.5.0 | `sha256:9e0b3a45753c170b795e9a9d6df61580085c113436beac5bf6c8de69b6562097` | `d857f8c9f5fea90cf450c0b30b4e77a37b541275` |
+| 0.6.0 | `sha256:0ba267cb87f53ebaca4e31805fe00610cd61fdf97a8d2c3692f4655700dceaed` | `5cf9817489c8dc47cee726bfe42fe3071cd32b85` |
+
+Both references use the fixed repository
+`ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf`. The gate first checks the defining
+provider repository and full workflow SHA, rejects an unrecorded digest before
+Docker access, pulls the exact digest and compares its actual revision label
+with the recorded producer. The worker may have been released before the workflow.
+The expected producer is not an input supplied by the consumer, and an inherited
+environment value cannot replace it. Failed pull/inspection stops the step.
+
+The deployment's reviewed-main guard, input interface and publication checks are
+unchanged. The gate uses the already-reviewed immutable artifact identity; this
+change does not introduce or claim a new live signature-verification service.
+Release preparation's existing signed-image evidence remains separate.
+
+Static workflow policy binds the whole gate, including its records and step
+controls, to reviewed canonical JSON. It rejects disabled/error-tolerant gates
+and refuses a BOM default whose worker has no approved record. A new worker
+requires an explicit provider review, updated policy and published-image tests.
+
+## Regression coverage
+
+`test/test_deploy_provenance.py` executes the actual shell blocks from the reusable
+workflow. Unit cases cover earlier legitimate producers, unknown digests with
+plausible labels, mutable/foreign references, missing/wrong labels, a label that
+matches the workflow instead of the worker, attempted expected-revision override,
+foreign/unbound provider authority, pull/inspection failure and reviewed-main
+ref/SHA rejection.
+
+The independently gated Docker case executes real pulls and inspections for both
+published workers against a later workflow revision. The ordinary CI distribution
+job must run this case; static policy rejects silently disabling it:
+
+```bash
+UNALTRAWEB_DEPLOY_PROVENANCE_DOCKER=1 PYTHONPATH=test \
+  python -m unittest test_deploy_provenance.PublishedDeployProvenanceTests
+PYTHONPATH=src python3 -m unittest discover -s test -p 'test_*.py'
+make workflow-check distribution-check
+git diff --check
+```
+
+Local checks passed 619 Python cases, with 30 optional/environment skips, plus
+the explicitly enabled real-Docker case. The actual image configuration IDs were
+`sha256:c1998dc3345444cb3994ac0cd649ad80ac88dde127dec1dd9f09c719aafe170a`
+for PDF 0.5.0 and
+`sha256:d7e7d3243616270fc9e6eed7f8238c412dbe3d9ffc18d2832d17d66ca630d139`
+for PDF 0.6.0. These tests exercise provenance gates without deploying a consumer.
+Protected PR/integration results and the exact delivery commit are recorded in
+issue 86 after integration.
+
+## Urgent consumer adoption
+
+The owner authorized a reviewed workflow-only delivery, independently of a new
+gem/wheel/image release. TIG can retain its approved 0.5.0 Gem/core, PDF digest
+and Vega selection and change only the `deploy.uses` revision in
+`.github/workflows/deploy.yml` to the corrected provider's immutable merge SHA.
+This is a reviewed local caller override; a later scaffold update must preserve
+or explicitly reconcile it rather than resetting it to an older packaged pin.
+
+In the TIG checkout, open the integration PR, verify that the content remains at
+its approved baseline, repeat the local publication checks, merge, then dispatch
+with the exact newly reviewed `main` SHA. Confirm the hosted build, Pages site
+and downloadable PDF. The provider gate proof alone does not replace TIG's full
+311-page manual validation or successful hosted deployment.

data/docs/agents/deployment-integration-0.7.1.md

@@ -0,0 +1,138 @@
+# Consolidated deployment integration — 0.7.1
+
+Owner: [issue 93](https://github.com/dosquartsdedocs/unaltraweb/issues/93), following
+the workflow-only [issue 86 correction](deploy-provenance-86.md). The owner
+authorized implementation, review/integration and gated 0.7.1 publication.
+Current source preparation is distinct from a published distribution; final
+source, receipts, installed-byte evidence and publication are recorded in issue 93.
+
+## One package-owned contract
+
+The BOM now carries two additive schema-v1 fields:
+
+- `consumer_integration.site_deploy_workflow_sha`, independent of the Gem's
+  `core_sha`. Legacy records default to their core revision.
+- `deployment_contract`, with exact `manual_pdf_workers` digest/producer records
+  and bounded `caller_migrations` describing reviewed baseline/current hash pairs.
+
+The package schema and semantic checks validate repository confinement, unique
+records, nonzero identities, the selected PDF's membership and exact migration
+identities. Existing packages, receipts and the issue-86 workflow pin remain
+unchanged. PDF 0.6.0, computation/capture 0.4.0 and the accepted visual-helper
+combination are reused rather than introducing additional component upgrades.
+
+The workflow fetches at most 256 KiB of JSON from its **defining provider commit**
+on the fixed canonical GitHub repository. It does not read a consumer-supplied
+contract or producer SHA. Strict JSON rejects duplicate/non-finite values; records
+have bounded inventory and exact digest/source syntax. Fetch, lookup, pull and
+inspection failures stop publication. A selected immutable digest is checked
+against its recorded producer, not a later workflow commit. Its temporary metadata
+file is invocation-owned and removed on exit.
+
+Static policy binds the generic gate code, while approved artifacts live in the
+contract. Ready-source validation resolves the actual workflow Git pin, checks
+its gate and compares its own producer record with the package selection.
+The CI Docker test additionally creates a package caller and executes the
+preflight blocks of the workflow that caller really selects. Checking only the
+current checkout's YAML is insufficient.
+
+## Reviewed hotfix migration
+
+Only `.github/workflows/deploy.yml` is eligible for the issue-86 migration:
+
+| Identity | SHA-256 |
+| --- | --- |
+| Original package baseline | `a789870542614d5817d30ea4328c7d1ad38d27443c009c68a48ad5aaa3106b8e` |
+| Exact reviewed one-line hotfix | `c632a548d0782867be20a2a52fe03469cf63066b7364bace77fd54a226cb3b18` |
+
+Both must match. The dry-run lists `deploy-provenance-86` in `migrations`, proposes
+the new package-generated caller and binds that authorization to `plan_sha256`.
+The existing confinement, CAS rechecks, private staging, rollback and final
+manifest commit remain in force. Any additional author edit remains a conflict;
+removing the migration authority changes the plan hash. This is not a general
+force-sync or semantic rewrite of authored workflow YAML.
+
+## Acceptance stages
+
+- Unit/schema/workflow tests cover independent core/workflow pins, legacy metadata,
+  invalid or ambiguous records, exact migration, preservation of additional edits,
+  plan binding, provider-only contract acquisition and fail-closed network/Docker
+  errors.
+- `test/test_deploy_provenance.py` tests actual published PDF workers and a generated
+  caller's selected workflow. CI obtains the reviewed source SHA explicitly for
+  source-bound metadata access.
+- `test/deployment_integration_smoke.py` uses installed launchers and owned synthetic
+  manuals: fresh, populated 0.5.0 upgrade and exact reviewed hotfix. It preserves
+  author/cache hashes, applies the reviewed plan, builds PDF/web, probes HTTP and
+  executes the exact remotely pinned workflow's source/provenance gates.
+- Final acceptance must use the downloaded same-source wheel and signed MCP
+  candidate. The driver does not dispatch Pages or claim a hosted real-manual
+  deployment. TIG's authorized deployment is a separate consumer-session proof.
+
+The implementation is integrated before the containing source selects its final
+reviewed core/workflow revisions. Candidate components remain pending until that
+selection; release readiness and publication keep their existing strict receipt,
+ancestry, signing and immutable-byte gates.
+
+## Reviewed source selection
+
+Implementation `2133b8fa2f668e14d603a36d15584eed63e4386a` is integrated through
+[PR 94](https://github.com/dosquartsdedocs/unaltraweb/pull/94) at
+`2ff27f27c274eb09b2c53ef8bd374f333702d8ee`. PR CI `37526811887` and CodeQL
+`37526811747` passed, including actual provider-record acquisition and generated
+caller provenance checks. The review is agent-attributed.
+
+The containing candidate now selects this integration for both independent
+core/workflow fields and marks gem, wheel, runtime and MCP ready for same-source
+candidate preparation. The selected workflow's own contract records the reused
+PDF 0.6.0 producer correctly; no worker version change is needed.
+
+Local source validation passed 629 cases with 31 optional/environment skips,
+fresh-wheel and owned-image MCP checks/smoke, docs and prose checks. The installed
+development new/upgrade/hotfix manual proof is retained at
+`/tmp/opencode/unaltraweb-071-93/local-integration/evidence.json`, SHA-256
+`d98c0fb56d2b74839a7132cc9dc7ab3f65a9802087837af1a13070a51316a14a`.
+That development proof still used the earlier reviewed workflow pin; final
+signed-candidate acceptance must exercise the now-selected integration above.
+
+## Final-byte gate: retained-document worker closure
+
+The first candidates from `b7ec1d7a139c65b3b0b88699cdbeb19080f13be1` passed normal
+manual upgrades but failed retained-Carta freshness with the reused PDF 0.6.0.
+The manifest fingerprints `artifact_imports.CHECKER_FILES`, including the changed
+distribution module and component schema. Successful PDF generation alone was
+not sufficient: the old worker and new controller calculated different identities.
+Those first core candidates are retained diagnostic evidence and are not promoted
+as the 0.7.1 release.
+
+The signed PDF specialization already built/tested by run `37530306398` contains
+the matching 0.7.1 checker closure:
+`ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:1bb3f2dafd741e96c28639ec1cc8ccaeb81cbaa73e649f787c0b4ef59997bd4b`.
+Its configuration ID is
+`sha256:618163d3f924439792b2306617bd9612f566c5881166102fa544b4e782d569fa`,
+its producer revision is the first candidate source above and its native package
+reports 0.7.1. The changed checker files match the controller byte for byte.
+
+A local controller overlay selecting only that exact worker passed the complete
+Carta import, copied-producer retirement, receiver relocation and forced PDF
+rebuild. Both 11-page PDFs have hash
+`eb693ced023efafe36a926dd38a1bf1c85399a1b114551cc0ff32e652144c496`; original Carta
+bytes remain unchanged. Diagnostic evidence:
+`/tmp/opencode/unaltraweb-071-93/pdf071-carta-probe/evidence.json`, SHA-256
+`c076f988e43ddb474132e58f5027931085bd734242757b84fb50289ef68cde25`.
+The overlay is not a signed final MCP identity.
+
+The worker record is integrated before a follow-up selection pins its containing
+workflow and PDF. Core components return to pending during this preparation.
+Ready-source CI now requires the exact selected core, controller and PDF worker
+to agree on every retained-document checker file. This catches this class of
+incompatibility before final publication; the final signed core candidates must
+still repeat the complete composed acceptance.
+
+The producer record and checker-closure regression were integrated through
+[PR 96](https://github.com/dosquartsdedocs/unaltraweb/pull/96) at
+`3332e0b93933f12317e05f1ce8d38ce80046feab`. This is the final reviewed core/workflow
+selection. The tuple selects the verified PDF specialization above as 0.7.1,
+published by its immutable digest, and the four core components return to ready.
+Their new same-source candidates replace the rejected first core tuple in the
+eventual release receipt. No earlier release or worker is overwritten.

data/docs/agents/mcp-contract.md

@@ -1,5 +1,11 @@
 # MCP Contract
 
+The D0 additions ship in the published 0.7.0 runtime. Their pinned requirements,
+exact API mapping, lifecycle scopes and external helper-identity blocker are
+documented in [the owner contract](d0-runtime-identity.md). A source descriptor
+does not upgrade an already-running 0.6.0 connection. Exact public identities and
+installed acceptance are recorded in [the delivery report](owner-closeout-85.md).
+
 `unaltraweb` exposes one global, on-demand stdio MCP server for website workspaces. Every client session starts an independently named Dockerized MCP process and mounts its current consumer project at `/workspace` and at its canonical host path. Stable factory, role, and project labels preserve project-scoped lifecycle control without forcing concurrent sessions to share a deterministic container name. The image includes both FastMCP and the Jekyll runtime, so the host does not need Python, the optional `mcp` package, Ruby, or Bundler.
 
 The client registration should launch:
@@ -32,8 +38,8 @@ it to an image ID before execution. The source checkout's digest pin is separate
 it advances only after a new receipt exists. Explicit `--image` (or the console
 adapter's `UNALTRAWEB_MCP_IMAGE`) permits a reviewed immutable selection.
 
-The post-release checkout pin selects published 0.5.1 MCP digest
-`sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692`.
+The post-release checkout pin selects published 0.7.0 MCP digest
+`sha256:b84cdb404ba7bab5ff0b14fa8a7ee93d7293e829cf32e28ff0dacaa8afff4677`.
 Existing processes keep their running image until clients reconnect. Site build
 defaults and customized Makefiles remain separate, explicitly reviewed selections.
 
@@ -43,7 +49,7 @@ Repository editing coordination remains a control-plane responsibility rather th
 
 For a new agent-driven workspace, create or select the empty Git repository first, open that directory in the IDE, register the factory, restart the client, and then call `new_web`. The tool remains confined to the configured project root and does not accept an arbitrary destination. Generated sites include user-owned `README.md` and `AGENTS.md`, profile-specific source directories, and a managed runtime baseline; `scaffold_sync` never rewrites those user-owned guidance or content files.
 
-The native Python CLI remains modular. Without a factory checkout it supports `version`, `new-web`, top-level `doctor`, the host-only `import-calibre` command, and the exact package-only MCP inventory declared in `component-contract.json`. The complementary exact inventory fails clearly with `UNALTRAWEB_FACTORY_DIR` remediation. The separate Docker adapter delegates to the full image and does not expand that native inventory. The BOM selects the published `diavisuals v0.4.0` and `vegavisuals v0.4.0` releases. Its `consumer_integration` object is also the single source for the immutable core, workflow, PDF worker, and Vega revisions rendered into consumer scaffolds. Neither companion is bundled in the wheel or MCP server namespace.
+The native Python CLI remains modular. Without a factory checkout it supports `version`, `new-web`, top-level `doctor`, the host-only `import-calibre` command, and the exact package-only MCP inventory declared in `component-contract.json`. The complementary exact inventory fails clearly with `UNALTRAWEB_FACTORY_DIR` remediation. The separate Docker adapter delegates to the full image and does not expand that native inventory. The 0.7.0 BOM selects owner-tested `diavisuals v0.5.0` and `vegavisuals v0.5.1`; existing 0.4.0 static receipts retain their exact integrity-checked compatibility point. Its `consumer_integration` object is also the single source for the immutable core, workflow, PDF worker, and Vega revisions rendered into consumer scaffolds. Neither companion is bundled in the wheel or MCP server namespace.
 
 Static Vega-Lite and Vega rendering remains owned by the required companion `vegavisuals` MCP dependency. Use its `visualization_status`, `visualization_check`, `render_visualizations`, and `vegavisuals://project/*` resources directly; `unaltraweb` exposes the authoring syntax but does not proxy those tools into the `web://` server.
 
@@ -81,6 +87,7 @@ baseline format nor runtime cleanup changes.
 
 | Resource | Description |
 | --- | --- |
+| `web://runtime-identity` | Bounded identity of this serving process: startup/current code, instance/PID namespaces, binding, runtime selections and cooperative lifecycle. |
 | `web://distribution` | Package-owned component BOM plus offline, feature-aware doctor findings for the current factory and project. |
 | `web://site-context` | Site profile, feature flags, content inventory, bibliography, bibliometrics, build state, and offline consumer-update advisory. |
 | `web://site-doctor` | Read-only offline distribution, project-contract, freshness, scaffold-drift, and core-override findings. |
@@ -109,6 +116,8 @@ baseline format nor runtime cleanup changes.
 
 | Tool | Notes |
 | --- | --- |
+| `runtime_identity` | Observe the actual serving instance, startup/current package evidence and selected/observed images; never prepare a runtime or inspect site content. |
+| `runtime_drain` | With `confirm=true`, stop admission on this connection; then close stdio and verify exact container/session resource termination. It is not workspace-wide down. |
 | `distribution_doctor` | Return offline component/factory/project findings with stable codes and optional local Docker image inspection that never pulls. |
 | `new_web` | Create a profile-specific site from package-owned assets after a complete collision, path, and symlink preflight. |
 | `starter_templates` | List package-owned profile scaffolds under the legacy inventory name. |
@@ -182,7 +191,7 @@ Manual PDF publication is a local workspace operation: it copies reviewed artefa
 
 ### Retained Letter Integration
 
-The 0.6.0 development increment adds package-only import/check commands and the
+The published 0.6.0 release adds package-only import/check commands and the
 `web://artifact-imports` resource. Web rendering needs its containing Jekyll core;
 manual inclusion also needs the matching PDF worker. Published 0.5.1 components
 do not acquire this capability from a launcher-pin change.

data/docs/agents/owner-closeout-80.md

@@ -0,0 +1,185 @@
+# unaltraweb 0.6.0 delivery closeout
+
+Published **2026-10-02 17:28:14 UTC**:
+[v0.6.0](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.6.0).
+Owner coordination: [issue 80](https://github.com/dosquartsdedocs/unaltraweb/issues/80).
+This report supersedes the pending delivery state in the chronological
+[preparation record](retained-letter-import.md). Issue 76 and release 0.5.1
+remain closed and immutable.
+
+## Review, source and integration
+
+The owner explicitly authorized commits, push, PR review/integration, signed
+candidate workflows, gated publication and the post-release launcher pin. The
+checkout was reconciled against all existing unit-80 paths; no unrelated edits
+were found. Work used one checkout and ordinary serial branches.
+
+| Role | Revision / evidence |
+| --- | --- |
+| Reviewed implementation | `7af652fb83629e959af05c407a34a2f5a15f7936` |
+| Integrated core selected by consumers | `5cf9817489c8dc47cee726bfe42fe3071cd32b85`, [PR 81](https://github.com/dosquartsdedocs/unaltraweb/pull/81) |
+| Immutable core/PDF selection | `8e93b8b808204faef54cccaee622699f04a11805` |
+| Final artifact-producing source | `de52db351490e94939aac20c6af264f22a6a1678`, [PR 82](https://github.com/dosquartsdedocs/unaltraweb/pull/82) |
+| Receipt-only child | `3ce7606bc6148aee19d067c559823d8c5b52db5d` |
+| Receipt integration and tag target | `ec6dcb28e890d32718aa173934527a7b4213a042`, [PR 83](https://github.com/dosquartsdedocs/unaltraweb/pull/83) |
+| Annotated tag object | `1605578861a1a09157037e6085020baad4948d72` |
+
+All three PRs have explicit agent review records and protected CI; those records
+do not claim human review. Merge commits preserve the reviewed core's ancestry.
+The receipt integration's first parent is exactly the artifact-producing source,
+and its first-parent diff contains only `release-candidates.json`.
+
+Review closed independent metadata-reference validation, malformed Pandoc-link
+handling, internal PDF OpenAction destinations, and direct signed-runtime
+acceptance. The vendored v1 verifier/schema still match the established hub pin
+byte for byte; 26 reference conformance tests passed against matching fixtures.
+Source checks reported 587 Python cases with 30 optional skips. Ruby, actual PDF,
+MCP, wheel/gem, workflow/distribution, docs and reproducibility gates passed.
+
+## Receipt and published identities
+
+[Tagged native receipt](https://github.com/dosquartsdedocs/unaltraweb/blob/v0.6.0/release-candidates.json):
+
+```text
+schema_version: 1
+release: v0.6.0
+source_commit: de52db351490e94939aac20c6af264f22a6a1678
+receipt SHA-256: 5ed4e6dd615367927e6ea8a3541c9e7dca9dad73a738851705f563e0e6895280
+```
+
+Exactly the four `ready` components are bound to that source:
+
+| Component | Registry artifact | SHA-256 / OCI index digest |
+| --- | --- | --- |
+| Gem | `unaltraweb-0.6.0.gem` | `276d04a71d1170220c3881cce8d0800633c42b0ee7ad07a376f80996c6afd177` |
+| Wheel | `unaltraweb_mcp-0.6.0-py3-none-any.whl` | `3effb471ffd264f7fb2a8c88dd6536bc86639eae52806527c2d872653944c85a` |
+| Base runtime | `ghcr.io/dosquartsdedocs/unaltraweb` | `sha256:a4e9d82b0e9a72e519c44e09ca449b2dc37964fbb9953ae6e4adff648e39b94b` |
+| Full MCP | `ghcr.io/dosquartsdedocs/unaltraweb-mcp` | `sha256:736c4ddd0a543454e3edaeac2e9cfd97a1279ce472923ac54e326c1281b2ba05` |
+
+Both `0.6.0` and `v0.6.0` OCI aliases were inspected anonymously and match those
+index digests. The MCP's local configuration ID is
+`sha256:73320210b19597243c7183ef255ffa1cbc36a07157e6ab4e1b3d9349fa89a063`;
+its revision label is the exact artifact source above. Configuration IDs and
+registry index digests are distinct identities.
+
+The selected PDF 0.6.0 is the already-published, signed and tested specialization:
+`ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:0ba267cb87f53ebaca4e31805fe00610cd61fdf97a8d2c3692f4655700dceaed`.
+It was produced from core `5cf9817489c8dc47cee726bfe42fe3071cd32b85` by the
+[initial signed image run](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37029374441),
+and its local configuration ID is
+`sha256:d7e7d3243616270fc9e6eed7f8238c412dbe3d9ffc18d2832d17d66ca630d139`.
+The BOM, generated consumer tuple and Make default select that same digest.
+It is reused as `released`, outside the four-component coordinated receipt.
+The later image workflow also tested a verification-only PDF candidate
+`sha256:9b3ae6fe1f04ff7de6c81c258d7c16f79cc7f2857c9b46b0829fc71812ace11f`;
+that candidate is not the selected worker and received no coordinated semver
+promotion. No self-digest or fabricated core SHA was introduced.
+
+Computation, capture, Diavisuals and Vegavisuals retain the tested 0.4.0 selections.
+Their exact immutable references remain in the BOM, and earlier published
+artifacts and receipts remain at their original tags.
+
+## CI, signing and publication
+
+| Gate | Successful run |
+| --- | --- |
+| Implementation PR CI / CodeQL | [37027921742](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37027921742) / [37027922332](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37027922332) |
+| Core integration CI | [37028677932](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37028677932) |
+| Tuple PR CI / CodeQL | [37032368507](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37032368507) / [37032368609](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37032368609) |
+| Final source CI / CodeQL | [37033064607](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37033064607) / [37033064633](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37033064633) |
+| Signed final image build/test | [37033593312](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37033593312) |
+| Package preparation | [37033596931](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37033596931) |
+| Receipt PR CI / CodeQL | [37038403708](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37038403708) / [37038403802](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37038403802) |
+| Receipt/tag target CI / CodeQL | [37039075585](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37039075585) / [37039075748](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37039075748) |
+| Tag CI | [37039786598](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37039786598) |
+| Semver image promotion | [37040420721](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37040420721) |
+| PyPI/RubyGems Trusted Publishing | [37040424945](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37040424945) |
+
+The signed image workflows checked exact OCI digests, signer workflow, source
+revision and labels before executing candidates. Promotion reverified those
+bindings and reused the tested manifests without rebuilding. The package
+authorizer bound workflow/run/source, immutable artifact ID `11237594327`, exact
+inventory and checksums to the receipt. Its archive digest is
+`sha256:79a67d7a8370468abe1f0265b248f3e9d6cf6187ac0bc891a0b3801e5a9931a6`.
+OIDC jobs published only the staged verified gem and wheel.
+
+The actual receipt-only branch, merged target and annotated tag passed strict
+`distribution-release-check` and publication-ref/ancestry gates. Native package
+run authorization, exact staging and `verify_package_publish.py release` passed
+before privileged publication. Strict release checks apply to the receipt/tag
+revision, not subsequent ordinary post-release source commits.
+
+## Real retained-letter and rollback proofs
+
+Acceptance consumed the authenticated published Carta 0.3.0rc1 packet, not a local
+producer checkout or synthetic unit fixture. The sender bundle hash is
+`aeaa757ee1be19bfe56dc9af8dd1178032929b4a2bec2dad2ebb621b158ad999`.
+All 12 seal files remain under `.unaltraweb/artifacts/carta/bundle/`.
+The mapping `payload/output/letter.pdf` → `assets/documents/carta.pdf` retains
+SHA-256 `4a661740a18fe1cf75b84aa0d8532511fd105eb5484a5af700e11e8e30828ea4`.
+The native chapter is `_chapters/en/carta.md`, with its separate binding and
+standard-v1 integration record outside the seal.
+
+The downloaded final CI wheel ran against the exact signed MCP and selected PDF
+digests above, without deriving another controller image. Both copied producer
+and incoming trees were removed, author prose survived an identical reimport,
+and the receiver was moved before native/generic verification and a forced PDF
+rebuild. Web/HTTP checks passed at both locations. The complete original letter
+appears on page 10 of an 11-page composed manual. Both composed PDFs have hash
+`416e96f66bb6608b1e20bf5e36b6b16133bd4018c17e6c079e8987b736fe9cae`.
+The integration record hash is
+`ebe07ee10ad740a2bbbd36d532f336374cf4bb19ccb373b6590b2279f664a222`.
+Generic verification confirms one bundle, one mapping and 14 verified files;
+the native checker additionally binds the source and rendered page.
+
+Local evidence root: `/tmp/opencode/unaltraweb-closeout-060/`.
+
+| Retained evidence | SHA-256 |
+| --- | --- |
+| `candidate-letter-proof/evidence.json` | `618573b1a867daf6b1f3023e0d5700c27a6de429abea160b4c51ff8699f86f9c` |
+| `candidate-roundtrip/evidence.json` | `23ec8885e8306931fb8ee4899e95b7bff4b3d23d2b63cdd3321e3f68722c3bb8` |
+| `published-packages/verified.json` | `073d7ca1bbe46b8be5d89211501ca8fc7b71297d7eb542c4c9cc27ff167aa91e` |
+
+The roundtrip exercised all four profiles using immutable MCP references:
+0.4.0 `sha256:389bc585cdb4fc89d3372f4896a55fe26e15df38b46bc114ce44fdb3f1c8deb9`,
+unpatched 0.5.0 `sha256:36d17edbade77edb40a687f6a744203c6329acb33fbc2eb255e88d9ff1a42c98`,
+then the new 0.6.0 digest. The unpatched failure was reproduced on a separate
+copy. Two builds and a preview passed at 0.6.0 and again after returning to 0.4.0.
+All six author/cache files retained their hashes; no caches were emptied.
+
+## Public downloads and post-release selection
+
+Anonymous PyPI and RubyGems metadata and package bytes match the receipt exactly.
+GitHub Release assets were downloaded again and pass `SHA256SUMS`, whose own hash
+is `60d80d6e0803154a7b5c98c1731f4bec905def3a481152d4e59d7daf8932fc1a`.
+A fresh public-wheel venv passed default `prepare`, `check` and real stdio `smoke`,
+selecting the expected MCP configuration ID without a local factory dependency.
+That public installation rechecked the relocated receiver and rendered mapping.
+The public gem installed into an isolated gem home and activated as 0.6.0 using
+the runtime's existing Ruby dependencies; this is not a network-fresh dependency
+installation claim. The downloaded candidate gem also passed isolated native
+helper-closure inspection.
+
+The source-only post-release branch `chore/80-pin-published-mcp-0.6.0` selects the
+published MCP digest in `Makefile` and `scripts/unaltraweb-mcp-bootstrap.sh`, updates
+the pin regression and current docs, and accompanies this report. Its PR/merge
+and final clean-main confirmation are recorded in issue 80 after protected CI.
+It does not rebuild or alter the published receipt, tag or packages.
+
+The post-pin local recheck passed 587 Python cases (558 passed, 29 optional
+skips), distribution/workflow/wheel and prose checks, `mcp-check`, real
+`mcp-smoke` with the selected public PDF, docs build and whitespace checks.
+Development builds used only `unaltraweb-closeout-060-*:post-pin` resources.
+The actual `MCP_CONSUMER_WORKSPACE`-bound `make mcp-stdio` transport also initialized
+a fresh synthetic consumer and exposed both native import tools; Docker inspection
+confirmed the published MCP configuration ID above. Its retained result is
+`/tmp/opencode/unaltraweb-closeout-060/post-pin-proof/evidence.json` and the session
+exited normally. `mcp-build` and the bootstrap's `--check` selected the public
+runtime directly.
+
+Acceptance covers the exact Linux/amd64 tuple and published English one-page
+Carta sample. The generic conformance tests do not establish Diapora composition
+or other domain imports. Active IDE processes keep their loaded runtime until
+reconnected. No real manual, author artifact, client registration or helper
+selection was migrated. Consumer adoption and hub catalogue integration remain
+separate owner actions; this report supplies their verified intake evidence.