unaltraweb 0.7.1 → 0.7.3

data/docs/agents/mcp-contract.md

@@ -38,8 +38,10 @@ 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.7.0 MCP digest
-`sha256:b84cdb404ba7bab5ff0b14fa8a7ee93d7293e829cf32e28ff0dacaa8afff4677`.
+The post-release checkout pin selects published 0.7.1 MCP digest
+`sha256:6aa20cff86c3891a876e37ba0548fa36f3c5633c9f22ba672e9f50123d677cf6`.
+The [0.7.1 delivery report](owner-closeout-93.md) records the consolidated deployment
+contract, exact hotfix migration and matching PDF verifier closure.
 Existing processes keep their running image until clients reconnect. Site build
 defaults and customized Makefiles remain separate, explicitly reviewed selections.
 
@@ -87,6 +89,8 @@ baseline format nor runtime cleanup changes.
 
 | Resource | Description |
 | --- | --- |
+| `web://practice-edition-schema` | Versioned Web recipient/edition configuration, separate from the producer-owned GIS descriptor. |
+| `web://practice-verifier-runtime` | Static private controller/package/profile identities and distinct release metadata; acquisition belongs to the hub. |
 | `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. |
@@ -114,8 +118,68 @@ baseline format nor runtime cleanup changes.
 
 ## Tools
 
+Private teaching editions use `manual_practice_compose(config, dry_run=false)`
+(CLI `mcp manual-practice-compose`, factory Make `manual-practice-compose`).
+`web://practice-edition-schema` supplies the versioned Web composition contract.
+The editor invokes the native CLI of the hub-prepared private QGIS controller, validates the full common
+bundle, selects explicit IDs with their complete producer closure, and retains
+one independent PDF and one ZIP per recipient, plus external receipts, under
+`dist/practiques/`. The PDF is copied from the sealed reading job and has exactly
+the same bytes as its ZIP member; no second render occurs. The entire edition
+directory is installed atomically and never replaces an existing edition. GIS parsing,
+execution and offline project reopening remain producer-owned.
+
+Each PDF build returns its original PDF and receipt hashes. Composition captures
+and checks that seal before building the other recipient, then copies only those
+sealed bytes. A changed PDF or replaced/resealed receipt fails before publication.
+
+`packages.<recipient>` retains its ZIP fields and adds `pdf` with the independent
+PDF path/hash/bytes and its own receipt path/hash. Names share the same stem:
+`<slug>[-docent]-<version>-<lang>.pdf` and `.zip`. Source/reading code remains
+versioned; data, PDFs, ZIPs and their retained sandbox/dist jobs remain ignored
+deliveries for Moodle, not Git publication. The paired PDF keeps ZIP-relative
+resource links; extract the ZIP beside it for those links to resolve locally.
+
+An edition's `gis.profile` explicitly selects `qgis-practice-v1` or
+`qgis-practice-v2` and its matching producer schema hash. Omitted profile is the
+legacy v1 case only. New configurations explicitly select verifier origin
+`prepared-image`, its image ID, native installed-package revision and schema hash.
+Legacy installed-wheel configuration shapes remain readable but are not silently
+converted or executed by this public Web runtime. Schema discovery invokes the
+requested profile in the private image. The selected bundle check must return
+that same profile. V2 map exports and their font/symbol/sidecar closures retain
+producer-declared roles and paths; the editor does not inspect their native formats.
+
+The public Web image contains no private QGIS package. The hub prepares the
+authenticated private image before activation; missing/mismatched images produce
+a concrete blocker without pull/build. Native calls reuse bounded processes,
+mount encoding and exact worker lifecycle. `practice_verifier` is a startup-fixed
+worker selection. Release wheel hashes and release producer revisions are declared
+provenance, separate from observed image/package identity; no `direct_url` is
+fabricated. Public CI reports private checks as `not_run`.
+See [private-practice-verifier-98.md](private-practice-verifier-98.md).
+
+Existing private readings can be declared once in `_config.yml` under
+`unaltraweb.practices.readings`, with exact `source`, `slug`, `lang`, `recipient`.
+Only Markdown beneath `practiques/` or `_practices/` is accepted. The same resolver
+serves PDF preparation and targeted `prose_check` / `editorial_review_prepare`.
+Private targets include draft/unpublished prose and retain original anchors;
+they are excluded from the default public corpus. Mapping does not approve copy
+or expose private directories through Jekyll.
+
+Reading mappings and edition readings accept the same optional `bindings` list:
+`reference`, exactly one `path` or selected `product`, required `sha256`, and
+optional portable `destination`. One practice resolver uses these declarations
+for both image snapshots and prose links. It never searches sandbox directories.
+Composition normalizes a prose href relative to the original source and emits
+only the authorised recipient's ZIP destination; bound files/maps and effective
+Pandoc sources are fingerprinted and receipted. Normal filesystem validators stay
+strict. Standalone PDFs allow explicit image bindings but refuse local file links
+without a portable edition context; HTTPS and internal anchors remain intact.
+
 | Tool | Notes |
 | --- | --- |
+| `manual_practice_compose` | One versioned consumer configuration selects GIS roots, two approved reading hashes and optional declared editable-SVG resources; delivers an independent PDF and ZIP per recipient with complete closure and create-only receipts. |
 | `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. |
@@ -131,7 +195,7 @@ baseline format nor runtime cleanup changes.
 | `site_source_read` | Read one allowed UTF-8 site source and return its exact SHA-256. |
 | `site_source_write` | Dry-run or atomically create/update one allowed source. Creates require `create_only`; updates require the exact SHA-256 returned by a read. |
 | `site_source_delete` | Dry-run or delete one allowed source with exact SHA-256 and explicit confirmation. It never deletes `_config.yml` or directories. |
-| `scaffold_sync` | Dry-run or transactionally synchronize the nine package-managed scaffold controls against `.unaltraweb/scaffold.json`; preserve local edits if the package file has not changed from baseline, reject conflicting edits and known version downgrades, and optionally require `expected_plan_sha256` from the reviewed proposal. Exact package bytes may be adopted without rewriting. Adopted, unchanged and preserved files are rechecked around the manifest-last transaction; rollback covers partial apply. README prose remains site-owned. |
+| `scaffold_sync` | Dry-run or transactionally synchronize the ten package-managed scaffold controls against `.unaltraweb/scaffold.json`; preserve local edits if the package file has not changed from baseline, reject conflicting edits and known version downgrades, and optionally require `expected_plan_sha256` from the reviewed proposal. Exact package bytes may be adopted without rewriting. Adopted, unchanged and preserved files are rechecked around the manifest-last transaction; rollback covers partial apply. README prose and source-CI project policy remain site-owned. |
 | `profile_check` | Check current profile and expected content/config paths. |
 | `prose_check` | Check a selected content target or all supported reader-facing sources and public metadata using shared profile/genre rules; no writes or model calls. |
 | `editorial_policy` | Inspect common guidance, profile defaults, genre overrides, local writing preferences and optional publication requirements. |
@@ -153,6 +217,7 @@ baseline format nor runtime cleanup changes.
 | `web_capture_render` | Start Jekyll and Chromium on an ephemeral internal Docker network, then publish original PNG plus editable annotated SVG from declared CSS selectors. |
 | `manual_pdf_status` | Inspect PDF configuration, sources, generated artefacts, published paths, selector, and freshness without Docker, network, or writes. |
 | `manual_pdf_build` | Build one or all configured language PDFs and first-page cover previews under `tmp/`; `release_selector` defaults to `latest` and is part of the PDF fingerprint. |
+| `manual_practice_pdf_build` | Build one private A4-landscape reading from `practiques/<slug>/<lang>/<audience>/` into an ignored, retained sandbox job. Reuse manual metadata/logos; require a prepared PDF toolchain; never publish or package course data. `dry_run` plans without writes and `run` names an explicit retained attempt. |
 | `manual_pdf_preview_prepare` | Build only stale `latest` PDF languages, then atomically stage ignored, untracked PDF and cover copies for local Jekyll review under a cleanup receipt. Always reports `publishes: false`; disabled PDF configuration is a no-op unless receipt-owned preview files still require cleanup. |
 | `manual_pdf_preview_clean` | Dry-run or remove only preview files whose path, Git state, content hash, and file identity still match the staging receipt. Real cleanup requires explicit confirmation plus the dry-run's exact `receipt_sha256` as `expected_receipt_sha256`, and never publishes. |
 | `manual_pdf_publish` | Copy built PDFs and covers to configured public assets. Defaults to dry-run; real publication requires explicit confirmation, and the selector must match the build. |
@@ -189,6 +254,36 @@ Manual PDF publication is a local workspace operation: it copies reviewed artefa
 
 ## New Site Initialization
 
+### Private Practice Readings
+
+`manual_practice_pdf_build(source, version, run="", dry_run=false)` delegates to
+the factory target `manual-practice-pdf-build`. Source paths are
+`practiques/<slug>/<ca|es|en>/<alumnat|docent>/<localized-name>.md`, using
+`LLEGIU-ME`, `LEEME` and `README`. The consumer must exclude `practiques/`,
+`sandbox/` and `dist/` from Jekyll and ignore `sandbox/practiques/` in Git.
+`profile_check` blocks a manual with practice sources and missing exclusions.
+
+The controller reuses manual metadata normalization and its authoritative
+typographic preamble, with a factory-owned A4-landscape article wrapper. It
+snapshots only the selected Markdown, local PNG/JPEG/PDF images, logos, template
+and filters. Its network-disabled, read-only worker receives that snapshot and
+one writable output directory; it receives neither checkout nor Docker socket.
+The already-prepared PDF toolchain is resolved to an exact image ID and never
+pulled implicitly. Session/project/token worker labels retain the existing D0
+ownership and timeout-cleanup contract.
+
+Jobs under `sandbox/practiques/` are create-only and sealed last. Repeat calls
+verify and reuse the exact job when its effective inputs match. Changed source,
+assets, rendering controls or image identity select another job; a nominal MCP
+version change alone does not. Edited, incomplete or conflicting jobs are
+retained. The optional `run` name provides an explicit retry/review identity.
+Every result reports `publishes: false`.
+
+This API compiles a reading, not a GIS job, public chapter or Moodle ZIP. The
+larger producer-handoff and package contract remains under issue #98. See
+[private practice PDFs](../_documentation/en/47-private-practice-pdfs.md) for
+supported syntax and adoption in an existing manual.
+
 ### Retained Letter Integration
 
 The published 0.6.0 release adds package-only import/check commands and the
@@ -224,7 +319,17 @@ It sets `lang`, `default_lang`, and `languages` so a new site has an explicit so
 
 Before writing, it validates every managed path, rejects destination symlinks, and compares existing files with the complete rendered scaffold through bounded regular-file reads. Identical files make repeated calls idempotent. Any differing file or file/directory collision detected during preflight aborts the whole operation before website files are written. Descriptor-relative, no-clobber writes and a final descriptor-relative content check prevent raced paths from being followed or overwritten; overwrite mode is not available. The baseline manifest is created after every other scaffold file.
 
-The baseline records exactly `.gitignore`, `.unaltraweb/docker-mount.sh`, `.github/CONTRIBUTING.md`, `.github/dependabot.yml`, `Makefile`, `Gemfile`, `Gemfile.lock`, `.github/pull_request_template.md`, and `.github/workflows/deploy.yml`. `scaffold_sync` updates one of these while its bytes still match the recorded baseline, adopts it when its bytes already equal the current package payload, and creates a newly managed path only when absent. If the package payload still equals the baseline but the local file differs, it preserves the local file and the original baseline hash; a subsequent upstream edit will still conflict. Conflicting local/upstream edits, missing managed files, collisions, unsafe paths and known newer consumer versions block the whole apply. It removes retired paths only from the baseline and never deletes their project files; it also never changes site-owned README/agent guidance, config, seed content, bibliography, data, or assets. A real synchronization requires `dry_run=false` and `confirm_sync=true`; adopted, unchanged and preserved files are included in the final rechecks around the manifest-last commit.
+The baseline records exactly `.gitignore`, `.unaltraweb/docker-mount.sh`, `.github/CONTRIBUTING.md`, `.github/dependabot.yml`, `Makefile`, `Gemfile`, `Gemfile.lock`, `.github/pull_request_template.md`, `.github/workflows/deploy.yml`, and `.github/workflows/source-checks.yml`. `scaffold_sync` updates one of these while its bytes still match the recorded baseline, adopts it when its bytes already equal the current package payload, and creates a newly managed path only when absent. If the package payload still equals the baseline but the local file differs, it preserves the local file and the original baseline hash; a subsequent upstream edit will still conflict. Conflicting local/upstream edits, missing managed files, collisions, unsafe paths and known newer consumer versions block the whole apply. It removes retired paths only from the baseline and never deletes their project files; it also never changes site-owned README/agent guidance, config, seed content, bibliography, data, assets, or `.unaltraweb/source-checks.json`. A real synchronization requires `dry_run=false` and `confirm_sync=true`; adopted, unchanged and preserved files are included in the final rechecks around the manifest-last commit.
+
+Source CI is a separate host entrypoint, `unaltraweb-source-checks` (equivalently
+`python -I -m unaltraweb_mcp.source_checks`), not another MCP server. One packaged
+workflow control calls it for all profiles; only the bounded Git-versioned JSON
+policy differs by project. It wraps the public `profile-check` and `prose-check`
+commands and observes the existing approval inventory without granting approval.
+Read-only clone mounts, no Docker socket, network-none checkers, explicit partial
+coverage and base-to-head inventory checks preserve the distinction between
+source conservation and retained-input/domain validation. See
+[source-ci-98.md](source-ci-98.md) for activation and the public/private GitHub boundary.
 
 At session start, `site_context.update_status` supplies an offline advisory against the active MCP package, including current literal version pins, target integration tuple, planned paths, preserved files, conflicts and `plan_sha256`. The agent explains available updates and asks for explicit acceptance before invoking `scaffold_sync` with that digest as `expected_plan_sha256`. The digest binds the consumer path, configuration, baseline, observed managed bytes and target package bytes; stale approval is rejected before writes. The parameter is optional for compatibility with existing explicit sync callers, but the guided flow always supplies it. An update can refresh scaffold controls without claiming a newer semver release. Unmanaged sites report an unavailable plan instead of being reinitialized. A declined update leaves normal content work available; there is no background network poll, self-upgrade, Git operation or automatic artefact regeneration. This flow requires a reviewed MCP/package release containing it and a reconnected client; updating the discovery checkout alone cannot replace the public digest-pinned runtime.
 

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

@@ -0,0 +1,185 @@
+# unaltraweb 0.7.1 delivery closeout
+
+Published **2026-10-07 12:33:20 UTC**:
+[v0.7.1](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.7.1).
+Owner: [issue 93](https://github.com/dosquartsdedocs/unaltraweb/issues/93).
+This report supersedes the chronological preparation states in
+[deployment-integration-0.7.1.md](deployment-integration-0.7.1.md).
+
+## Delivered behavior
+
+The package owns independent immutable core/workflow pins and exact PDF
+digest/producer records. The reusable workflow fetches bounded strict JSON from
+its own defining provider revision, not the consumer checkout. Release readiness
+checks that selected workflow and its records. CI generates a caller, executes
+its actual selected provenance gates and compares retained-document verifier
+bytes across the selected core, controller and PDF worker.
+
+The exact issue-86 hotfix is recognized by the original baseline hash and current
+file hash, listed in the update plan and bound to its SHA. Extra local edits
+remain conflicts; existing confinement, staging, CAS and rollback are retained.
+The new/upgrade/hotfix installed acceptance preserves author and generated-cache
+hashes while building and probing actual web/PDF output.
+
+The owner explicitly authorized the full 0.7.1 review, integration, gated
+publication and post-release pin. Work used one authoritative checkout and serial
+ordinary branches. Reviews are agent-attributed, not human approval. Published
+earlier artifacts and real consumer selections remain intact.
+
+## Source and receipt lineage
+
+| Role | Revision / evidence |
+| --- | --- |
+| Implementation | `2133b8fa2f668e14d603a36d15584eed63e4386a`, [PR 94](https://github.com/dosquartsdedocs/unaltraweb/pull/94) |
+| Initial implementation integration | `2ff27f27c274eb09b2c53ef8bd374f333702d8ee` |
+| Initial candidate source, later rejected as a core tuple | `b7ec1d7a139c65b3b0b88699cdbeb19080f13be1`, [PR 95](https://github.com/dosquartsdedocs/unaltraweb/pull/95) |
+| Worker-record/checker-closure correction | `1ce0e2039e3cb59ed57dbef7961193c7de9ea751`, [PR 96](https://github.com/dosquartsdedocs/unaltraweb/pull/96) |
+| Selected reviewed core and workflow | `3332e0b93933f12317e05f1ce8d38ce80046feab` |
+| Final tuple selection | `18d8d20ba92e397b8341f91207ae05cb6146473b`, [PR 97](https://github.com/dosquartsdedocs/unaltraweb/pull/97) |
+| Final artifact-producing source | `ae5dab1d99804e7f73da82930199c1e2f3c08f61` |
+| Receipt-only child | `24834dcc3e2e03f0bb76b5f18c2fbe346b143455` |
+| Receipt integration / tag target | `1ff25c6956458c3a99436312466e9cc588ed34b9`, [PR 99](https://github.com/dosquartsdedocs/unaltraweb/pull/99) |
+| Annotated tag object | `6e8d7f107a6bfa013a400db0e2a3cb6269d37e38` |
+
+The tag target's first parent is exactly the final artifact source; its
+first-parent diff contains only `release-candidates.json`. Native package-run
+authorization/staging, strict distribution/ancestry/publication-ref checks and
+annotated-tag verification passed before publication.
+
+[Tagged receipt](https://github.com/dosquartsdedocs/unaltraweb/blob/v0.7.1/release-candidates.json)
+SHA-256: `feda4f19b4133e60b4dae3cf88367ae8089c88077b4ac3fcfccc76d153411f2e`.
+
+| Component | Artifact / repository | SHA-256 / OCI index digest |
+| --- | --- | --- |
+| Gem | `unaltraweb-0.7.1.gem` | `6371e502601f970bc30711868b0eb2a29f429e1b78e21ac71ac09696b108baee` |
+| Wheel | `unaltraweb_mcp-0.7.1-py3-none-any.whl` | `cd2a06a2d2e16758c916d640e71210b16285fe3848cc987651801ff324a50a8e` |
+| Base runtime | `ghcr.io/dosquartsdedocs/unaltraweb` | `sha256:af776cfcd79f2778d36e179dccba63792d820d1939fd89187b7af7089e11247a` |
+| MCP | `ghcr.io/dosquartsdedocs/unaltraweb-mcp` | `sha256:6aa20cff86c3891a876e37ba0548fa36f3c5633c9f22ba672e9f50123d677cf6` |
+
+Linux/amd64 configuration IDs, distinct from registry index digests:
+
+- Runtime: `sha256:7b58b0ad1e7fdfd00087b6702c7002b4a4d393072077def17ff5fb1e198c8cfb`.
+- MCP: `sha256:f0e7915527fa68a67448287e131ec431aeae902b8269856e4e219e67faade146`.
+
+Both revision labels identify the final artifact source. Both `0.7.1` and
+`v0.7.1` aliases were inspected anonymously and match the receipt. Public registry
+downloads and downloaded GitHub assets match their hashes. `SHA256SUMS` itself
+has SHA-256 `10938774ef08dabd24cbd7853abd2d72957e75c750418ac8ebe7af7c1ce4553b`.
+
+## The PDF compatibility failure was caught before release
+
+The first core candidates reused PDF 0.6.0. Plain manuals passed, but retained
+Carta freshness failed because the verifier closure includes the changed
+`distribution.py` and component schema. The old worker's successful PDF output
+was not accepted as fresh by the new controller. No manifest was edited and no
+freshness check was disabled to force a pass.
+
+The signed specialization from the initial image run has the correct 0.7.1
+checker bytes and is now selected by immutable digest:
+
+```text
+ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:1bb3f2dafd741e96c28639ec1cc8ccaeb81cbaa73e649f787c0b4ef59997bd4b
+producer: b7ec1d7a139c65b3b0b88699cdbeb19080f13be1
+configuration ID: sha256:618163d3f924439792b2306617bd9612f566c5881166102fa544b4e782d569fa
+native package version: 0.7.1
+```
+
+The final four-component receipt reuses this separately verified digest. The
+later image workflow also built verification PDF
+`sha256:6bc7342a9ad6eb4edfff0d022d7157370e9c9bcba2b87bb80532389cfded62d4`;
+it is not the selected worker and received no coordinated semver promotion.
+The rejected initial core candidate tuple and local diagnostic overlay remain
+clearly separated from final signed-byte acceptance.
+
+## CI, signing and publication
+
+| Gate | Successful run |
+| --- | --- |
+| Implementation PR CI / CodeQL | [37526811887](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37526811887) / [37526811747](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37526811747) |
+| Initial signed images / packages | [37530306398](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37530306398) / [37530310332](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37530310332) |
+| Worker-record PR CI / CodeQL | [37534571592](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37534571592) / [37534571578](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37534571578) |
+| Corrected tuple PR CI / CodeQL | [37613153175](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37613153175) / [37613153240](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37613153240) |
+| Final source CI / CodeQL | [37613808731](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37613808731) / [37613808758](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37613808758) |
+| Final signed images / packages | [37614367552](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37614367552) / [37614371507](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37614371507) |
+| Receipt PR CI / CodeQL | [37619948216](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37619948216) / [37619948348](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37619948348) |
+| Receipt integration CI / CodeQL | [37620746600](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37620746600) / [37620746542](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37620746542) |
+| Tag CI | [37620758376](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37620758376) |
+| Image promotion | [37621482487](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37621482487) |
+| PyPI/RubyGems Trusted Publishing | [37621486444](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37621486444) |
+
+Final package artifact `11479132691` has archive digest
+`sha256:648e84e49abc0af299f7caf1b1d50931da42439d0a58ceb0839ebfa99524893b`.
+The signing/test/promotion jobs verified exact digest, source and signer bindings.
+The package publisher authorized the run/source/inventory and published only the
+staged recorded bytes. Promotion reused the tested image manifests.
+
+## Installed final-byte proofs
+
+The final downloaded wheel and exact signed MCP, without a derived controller,
+passed all of these gates:
+
+- `deployment_integration_smoke.py`: new manual, populated 0.5.0 upgrade and exact
+  reviewed hotfix. Author/cache hashes were preserved, plans applied, PDF/web/HTTP
+  passed and the actual generated workflow pin was exercised.
+- `artifact_import_smoke.py`: authenticated Carta seal, original PDF, author prose,
+  copied-producer retirement, receiver relocation and forced rebuild. Both composed
+  PDFs have 11 pages and hash `1b942d003847126cfdbc14630059bb6ede5512751400b3701dab85a7d37b78a7`;
+  the unchanged original letter is on page 10. Integration record hash:
+  `e80d504b19677ace36c512f758161d3d5663d38d0979ef8c36bc87be765f9e40`.
+- `d0_runtime_smoke.py`: live identity, reconnect/scope, disk drift, busy drain,
+  real worker crash recovery, offline/mapping/mismatch checks and actual
+  0.7.0 → 0.7.1 → 0.7.0 rollback with retained state.
+- `bundler_transition_smoke.py`: all four populated 0.4.0 → 0.7.1 → 0.4.0 profiles,
+  two builds and a preview per point, unchanged author/cache files and separate
+  reproduction of the known unpatched 0.5.0 failure.
+- Published Diavisuals 0.5.0 / Vega 0.5.1 rendering, receipts, tampering and relocation;
+  downloaded-gem isolated helper closure. Earlier exact 0.4.0 static receipts retain
+  their integrity-checked compatibility point.
+
+Evidence root: `/tmp/opencode/unaltraweb-071-93/`.
+
+| Result | SHA-256 |
+| --- | --- |
+| `final-integration/evidence.json` | `dcfce02ed10e7567a1030c1c93fc31fb7d75dfc73281fe8f1c4ee6b46038b6da` |
+| `final-carta/evidence.json` | `c456b5e72d72bc224a7416589805c7d80c50d7fafe8747c86cd31ecb782cd308` |
+| `final-d0/evidence.json` | `989603ed0a09fd6af9ca659ffbb824ab46907cb4538d094dcf32e34c8ea77c25` |
+| `final-bundler/evidence.json` | `352fe35a81f36b2b44fbfe92f000d9179053d45f572b37f48485c82dd4c7c949` |
+| `final-helpers/evidence.json` | `df994ccd8afaff45a7e3cfa9b6a29b650c9d01d63db2c9c36e59c31834273473` |
+| `published-packages/verified.json` | `39b322784e5eef0ccde89ad8883e495c66ec9df23213fbe3301fb91862cb2c2c` |
+| `public-images.json` | `6c2f54a877728dabbf39f2f2b0432beb5fe4c50c98769b22e06b6e1c562d7f77` |
+| `post-pin-proof/evidence.json` | `f9168183e859e842b4bc236cca126edc2e9bd5464eb2527450302cc9342121c6` |
+
+A fresh public-wheel venv passed default prepare/check/stdio smoke with the exact
+expected configuration ID and rechecked the relocated Carta mapping. The public
+gem installed in an isolated gem home and activated as 0.7.1 using the runtime's
+existing dependency set; this is not a network-fresh dependency installation claim.
+
+The actual checkout `MCP_CONSUMER_WORKSPACE=… make mcp-stdio` transport reported
+instance `effcd7bce6cb477da6c49107a5582e02`, loaded 0.7.1 and the expected image.
+Tool/resource identity agreed, the scaffold target selected the reviewed workflow,
+and drain/close followed by exact session inspection proved resource release.
+The post-release pin/report PR and clean-main CI result are recorded in issue 93.
+
+The post-pin local suite passed 629 cases (599 passed, 30 optional skips),
+distribution/workflow/fresh-wheel gates, prose/publication-copy checks and
+whitespace checks. `make mcp-check mcp-smoke` used owned
+`unaltraweb-071-93-*:post-pin` development images and the selected public PDF;
+`make docs-build` used the exact published runtime digest. Both passed. These
+development builds are separate from the signed-byte acceptance above.
+
+## Consumer and hub boundaries
+
+TIG independently adopted the earlier issue-86 hotfix in
+[geourv/tig#24](https://github.com/geourv/tig/pull/24) and deployed reviewed main
+`f5ddfabe650c95c10a99f3656a7cfc09e885dcbf` in successful run
+[37523692990](https://github.com/geourv/tig/actions/runs/37523692990).
+Its owner verified the public 311-page PDF byte-for-byte against the approved
+copy, SHA-256 `3d58d63b7315099ac3518401415c35f0a0acf4a3f7f41ee6270716f394309bc4`.
+That is hosted proof of its existing 0.5.0/hotfix combination, not a 0.7.1 migration.
+
+This release's acceptance covers Linux/amd64 installed web/PDF work and selected
+workflow preflights; real-manual hosted adoption remains per-consumer. The full
+managed helper graph still needs composing-owner acceptance of the published
+Diavisuals 0.6.0 correction; selected rendering compatibility remains 0.5.0.
+gaContExt catalogue/advisory/activation work and deliberate client reconnection
+remain separate. Earlier releases, author data and client registrations are preserved.