unaltraweb 0.5.1 → 0.7.0

data/docs/agents/d0-runtime-identity.md

@@ -0,0 +1,200 @@
+# D0 native runtime identity and lifecycle — issue 85
+
+Requirements: gaContExt
+`5634ea2e3e42122bb365992dfca9f248feb89dec`,
+[NATIVE_RUNTIME_REQUIREMENTS.md](https://github.com/dosquartsdedocs/gacontext/blob/5634ea2e3e42122bb365992dfca9f248feb89dec/src/bash/mcp_factories/NATIVE_RUNTIME_REQUIREMENTS.md).
+Owner issue: [85](https://github.com/dosquartsdedocs/unaltraweb/issues/85).
+Coordination: [gaContExt 15](https://github.com/dosquartsdedocs/gacontext/issues/15).
+
+## Native API mapping
+
+The containing 0.7.0 increment adds `runtime_identity` and
+`web://runtime-identity` on the actual serving MCP instance. Both use one
+startup-created object, not a helper CLI. It records a random backend instance,
+process PID/start ticks/PID namespace, start time, interpreter, loaded package
+version and startup package fingerprint. Current bounded package bytes and
+metadata are separate observations; changing metadata cannot rename the loaded
+version. Only engine code/contracts and allowlisted runtime selections are read,
+not site content or arbitrary environment values.
+
+The identity's component/profile/selection hashes bind the fixed requirements,
+startup BOM, behavioral profile, worker selections and consumer mapping. The
+package fingerprint is a startup code-content observation, not a wheel checksum
+or a permanent process attestation. The live container's image ID, source label,
+limits and mount mapping are inspected separately. Its daemon-host init PID is
+not compared numerically with the inner serving PID. Session ID, exact container
+ID, factory/role/project labels and mapping correlate those namespaces.
+
+`runtime_drain(confirm=true)` freezes admission on that connection. Ordinary
+tools execute in a bounded one-operation lane, leaving identity/drain responsive
+while a worker runs. Closing stdio waits for active work and releases that
+session's idle preview/capture resources. A new connection creates a new backend
+instance. This profile is **one stdio connection per backend**, not a shared HTTP
+service: shared-backend reattachment/idle leases are not claimed.
+
+Host-side installed API:
+
+```text
+unaltraweb-mcp-docker prepare --image REF [--expected-image-id SHA256_ID]
+unaltraweb-mcp-docker serve --project ROOT --image REF --expected-image-id SHA256_ID --managed
+unaltraweb-mcp-docker session-status --project ROOT --session-id SESSION --container-id CONTAINER
+unaltraweb-mcp-docker reap-session --project ROOT --session-id SESSION --container-id CONTAINER
+```
+
+Preparation may acquire the explicitly selected image. Launch/check/smoke never
+build or pull; execution uses its inspected exact configuration ID with
+`--pull never`. Managed mutable aliases require the expected full image ID.
+Full local IDs and repository digests are immutable selections. Ordinary mutable
+local selections without an expected ID remain an explicitly weaker mode.
+Archive hashes, repository/index digests and Docker configuration IDs are distinct.
+
+`--offline` disables controller networking; the explicitly mounted local Docker
+socket still permits image/owned-container inspection. Preview HTTP probing and
+intentional external metrics calls need their documented network access.
+`--worker-images` accepts bounded JSON mapping supported worker names to exact
+`reference` / `expected_image_id` pairs. Otherwise startup BOM/dedicated image
+environment selections apply. Managed execution refuses missing/mismatched
+workers and never substitutes a preparation build/pull. Authored computation
+image choices must match the approved startup identity before execution.
+
+The normal host launcher canonicalizes the consumer and binds it at its canonical
+path and `/workspace`. A containerized launcher must supply `--host-project` (or
+its explicit inherited daemon mapping); the child uses that verified canonical
+mirror. Identity reports launcher-visible, daemon-host and effective paths.
+Other direct controller layouts are not silently inferred. In particular,
+[issue 31](https://github.com/dosquartsdedocs/unaltraweb/issues/31) remains a separate
+boundary for arbitrary direct `/workspace` controllers and is not automatically
+closed by this profile.
+
+## Resource ownership
+
+Each launch has a 32-hex session ID and a uniquely named owned stdio container.
+Previews are per-session for these backends. Worker invocation tokens are retained
+and augmented with session labels. Cleanup validates full IDs and ownership and
+confirms absence before claiming release. Image and volume removal is outside
+these APIs.
+
+After EOF or a crash, the caller uses the **retained** binding/session/container
+tuple with `session-status`. A live backend is `connected`; a running one-shot
+worker is `busy`; idle leftovers are `orphaned`; only proven absence is `stopped`
+with `resources_released=true`. Unavailable/changed ownership is `unknown` and
+does not authorize removal. `reap-session` preserves a live backend or running
+job, and recovers only that retired session's idle resources. Occupied or foreign
+networks fail closed. No fresh-helper PID is presented as the backend's PID.
+
+The legacy `down` / `make mcp-down` is an explicit **workspace-wide** shutdown;
+`mcp-down-all` is maintainer/factory-wide. Neither is the hub's per-client toggle
+operation. The managed sequence is live drain, close this transport, inspect its
+exact retained identity, and recover eligible orphans when necessary.
+
+The profile reports controller limits (2 CPUs, 4 GiB, 512 PIDs), preview/PDF/capture
+limits (2 CPUs, 2 GiB, 256 PIDs), and managed computation limits (4 CPUs, 8 GiB,
+512 PIDs). Existing per-invocation time bounds remain 1800 seconds for PDF/compute
+and 900 for captures; requests may compose several bounded jobs. Per-backend
+operation concurrency is one. A drain does not falsely claim immediate RAM/CPU
+release while a job continues.
+
+## Accepted visual-helper points and remaining closure blocker
+
+The candidate selects the published Diavisuals 0.5.0 and Vega 0.5.1 packages:
+
+| Helper | Wheel SHA-256 | Renderer configuration ID |
+| --- | --- | --- |
+| Diavisuals 0.5.0 | `f52e20f20f1fb3a2418f07adb8d6a68a5567d0c321fb7c0ccc0f4db04917b96b` | `sha256:5a6887b372a0e1c386a7b54981d11ae1910215baeb6a12dfd0706b3e85ef0846` |
+| Vega 0.5.1 | `5aba4f267a37179c520b3cd164e1cec62ac5561872aa33b069cce73442dc52b1` | `sha256:695125943d0fbc3aa7c877babb9a11a6501bbc7ac265b0975bb5657c60439d98` |
+
+Native selector mapping is Diavisuals `--runtime-image` plus
+`--runtime-expected-id`, and Vega `--renderer-image-id`. Published metadata,
+wheel/acceptance hashes and locally prepared renderer IDs were verified. Actual
+Mermaid, PlantUML, Vega-Lite/CSV and Vega rendering passed native receipt checks,
+tamper refusal and consumer relocation without rewriting renderer aliases.
+Retained evidence: `/tmp/opencode/unaltraweb-d0-85/helpers-proof/evidence.json`.
+
+Previously accepted **0.4.0 static receipts remain valid** under the unchanged
+input/output/request integrity rules. This is an exact legacy point, not a
+continuous version interval or permission to overwrite edited outputs. New work
+uses the selected helper points. No existing client or real consumer is migrated
+by this source change.
+
+The coordinator does not claim to observe another MCP's serving process. Its live
+identity returns the helper selections and requires their independent connection
+observations. **Diavisuals 0.5.0 still lacks the full live-instance identity**;
+[Diavisuals 14](https://github.com/dosquartsdedocs/diavisuals/issues/14) is therefore
+an external D0 managed-closure blocker. Rendering compatibility alone does not
+close that gate or make the whole coordinator dependency graph managed-ready.
+
+## Acceptance and delivery state
+
+`test/d0_runtime_smoke.py` exercises installed launchers, actual images, tool/resource
+agreement, independent consumers, reconnect, running-container metadata drift,
+busy drain, offline launch, wrong/missing image refusal, manual/web work and
+0.6.0 → containing 0.7.0 → 0.6.0 activation with retained authored/generated state.
+The published 0.6.0 point accurately remains **partial** for live identity; no
+fixture or relabelled package is counted as a second D0-capable release.
+Backend-crash/orphan recovery is exercised separately from graceful disconnect.
+The existing Carta and populated Bundler acceptance drivers remain release gates.
+
+This is owner development evidence until reviewed source, containing release
+receipts, installed signed-byte acceptance and remaining blockers are returned to
+the central issue. Published 0.6.0 and its active checkout launcher pin remain
+unchanged during candidate development. The worker/data choices and external
+Diavisuals identity blocker must remain visible in the hub's adapter decision.
+
+## Retained local acceptance — 2026-10-05
+
+The owner explicitly authorized the full 0.7.0 review/PR/integration, gated
+publication and post-release pin flow. No other checkout is a write workspace.
+
+The installed local wheel
+`67689b76225511439175c82b6df033005d84e990b147b8fa4875f3adbd7d684f` and owned MCP
+image `sha256:d8eafba61a2e1f02bc22b244610d8174879e04d9ea36b47a71e8cd7f993a54b1`
+passed eight stages: reconnect/scope, loaded-versus-disk, busy drain, backend
+crash recovery, offline launch, explicit daemon mapping, wrong worker and missing
+worker. The crash record observed a real PDF job still **busy** after backend
+death, then confirmed eligible recovery and resource absence. The other live
+instance was preserved. The published 0.6.0 A/B/A point remained explicitly
+partial for live identity; authored files and its old cache entries kept their
+hashes. This is prepared development evidence, not a signed release identity.
+
+| Local retained evidence under `/tmp/opencode/unaltraweb-d0-85/` | SHA-256 |
+| --- | --- |
+| `acceptance-final/evidence.json` | `e35457153c5ffe98b4bd231f608735a2c4ad07e9db756699d7446e06e6b0b9c7` |
+| `helpers-proof/evidence.json` | `df994ccd8afaff45a7e3cfa9b6a29b650c9d01d63db2c9c36e59c31834273473` |
+| `carta-proof/evidence.json` | `ac305ad222a792291ebd27679a72a37a3ff29ab4746301ed9db7f64705ca4755` |
+| `bundler-proof/evidence.json` | `b304c4c5abe45ae9295f6eba86eae36be92e348e6be33463fcb50e119550d341` |
+
+The Carta proof retains the published sender seal and unchanged original PDF,
+removes the copied producer, relocates the receiver and forces another PDF build.
+Both 11-page manuals have SHA-256
+`46e50f815c007a97ac59898194023de3fa4e916e77e7eac21b73f8792244713c`; the letter is
+on page 10. The four-profile populated Bundler regression passed 0.4.0 → prepared
+0.7.0 → 0.4.0, preserving all six tracked author/cache checksums and separately
+reproducing the known unpatched 0.5.0 failure. No caches were cleared.
+
+Review additionally tightened Docker absence classification: an unavailable
+daemon socket is **unknown**, not evidence that a container was removed. That
+source-only correction has a dedicated regression; final release acceptance must
+be repeated against the actual source-bound candidates after integration.
+
+The local suite passes 608 tests with 30 optional/environment skips. Distribution,
+workflow, fresh-wheel and extracted-gem gates pass, as do the real MCP smoke,
+manual preparation, docs build, prose checks and whitespace checks. These checks
+do not override the separate signed-candidate/publication gates or the external
+helper-process blocker.
+
+## Reviewed core selection
+
+Implementation `0c87e8c276e58ac9c747833df69cdb439aa6132b` was reviewed and
+integrated through [PR 87](https://github.com/dosquartsdedocs/unaltraweb/pull/87)
+as `216ab2e8b6b8b45a5bb7da0a54bffd10edee895d`. Protected PR CI
+[37271200816](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37271200816)
+and CodeQL [37271200817](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/37271200817)
+passed. The recorded review is agent-attributed.
+
+The next candidate source pins that integrated core and authorizes gem, wheel,
+runtime and MCP as `ready` for same-source candidate preparation. The selected
+signed PDF 0.6.0 and computation/capture 0.4.0 workers remain unchanged: the new
+selection/lifecycle behavior is controller-owned. Strict receipt, ancestry,
+candidate, installed-byte and publication gates still apply. This readiness is
+for the containing owner release, not approval of the full managed coordinator
+closure while the external Diavisuals identity gap remains.

data/docs/agents/mcp-contract.md

@@ -1,5 +1,10 @@
 # MCP Contract
 
+The D0 additions require a containing 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.
+
 `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:
@@ -16,7 +21,7 @@ MCP_CONSUMER_WORKSPACE="$PWD" make --silent --no-print-directory -C /path/to/una
 
 Replace `/path/to/unaltraweb` with the checkout's absolute path. The bootstrap canonicalizes the inherited environment value after process launch; neither Make nor generated shell source evaluates consumer path text. The declared launcher remains `make`, which gContExt permits for a container runtime without a `runtime.allowed_host_launchers` exception. Restart clients such as OpenCode after changing their MCP registration.
 
-Next-release wheels also install this native descriptor and its complete host
+Released 0.5.1 wheels also install this native descriptor and its complete host
 helper closure under `share/unaltraweb-launcher`. For that installed profile,
 `${factoryRoot}` is the path returned by `unaltraweb-mcp-docker path`, rather than
 a core checkout. Its small Makefile implements `mcp-build`, `mcp-check`,
@@ -32,13 +37,18 @@ 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.6.0 MCP digest
+`sha256:736c4ddd0a543454e3edaeac2e9cfd97a1279ce472923ac54e326c1281b2ba05`.
+Existing processes keep their running image until clients reconnect. Site build
+defaults and customized Makefiles remain separate, explicitly reviewed selections.
+
 gContExt dependency preparation ensures the selected MCP release image and prepares required companions but does not initialize consumer content. The transport passes `${workspaceFolder}` only through `MCP_CONSUMER_WORKSPACE`; it never sets `transport.cwd` or embeds the consumer path in a Make assignment. The factory command may therefore use `make -C` without changing or reparsing the selected consumer root. Companion-aware checks and smoke tests include both required providers, while provider updates remain explicit. The manifest does not advertise an `init` command, and both companion dependencies set `init: false`. Use `new_web` explicitly when a new consumer site should be created. Restart long-lived MCP clients after registration, release-pin changes, or provider upgrades so their stdio processes use the selected releases.
 
 Repository editing coordination remains a control-plane responsibility rather than an `unaltraweb` runtime feature. Request one top-level MCP and let the control plane select its declared dependency closure; unrelated user registrations remain configured until explicitly removed and clients reconnect. Before editing, the control plane runs its read-only checkout preflight against the one primary mutable checkout and, when required, holds a process-scoped cooperative lease through its `exec` wrapper. Only one editing session may be active per repository. The control plane must never create, switch to, move, prune, repair, or remove Git worktrees implicitly.
 
 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.
 
@@ -76,6 +86,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. |
@@ -97,12 +108,15 @@ baseline format nor runtime cleanup changes.
 | `web://manual-authoring-components` | Supported prose structures and component syntax, including callouts, definition lists, figure layouts, tables, diagrams, citations, and web/PDF compatibility. |
 | `web://manual-computations` | Executable manual sources, selected runtime images, generated outputs, and freshness state. |
 | `web://web-captures` | Selector-based screenshot recipes, original PNGs, editable SVG layers, edited overrides, and freshness. |
+| `web://artifact-imports` | Native retained-letter bindings, complete seal/mapping integrity and source references; read-only. |
 | `web://new-web-scaffolds` | Package-owned scaffold availability and contract paths for every supported site profile. |
 
 ## Tools
 
 | 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. |
@@ -111,6 +125,8 @@ baseline format nor runtime cleanup changes.
 | `site_context` | Read the main local state plus `update_status`: current/target package versions, planned paths, preserved customizations, conflicts and a reviewed-plan digest. |
 | `site_doctor` | Combine distribution doctor with strict project config, identity/language, generated Make contract, scaffold drift, required generated-output/receipt status, existing HTML audit, companion actions, and core override inventory. Unknown required status is blocking. Read-only and offline. |
 | `site_check` | Run profile, publication-copy source diagnostics, freshness, companion visualization/diagram receipt, bibliography, bibliometrics, and build-state checks without network. |
+| `import_artifact_bundle` | Plan or explicitly apply a create-only Carta 0.3.0rc1 `letter-pdf-v1` import with the sender SHA-256, complete retained seal, standard v1 integration record and native content binding. Defaults to dry-run; apply requires `confirm_import=true`. |
+| `artifact_import_check` | Verify retained domains, mappings and native source references; optional `output_folder` checks the bound rendered page and exact emitted PDF bytes. |
 | `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. |
@@ -172,6 +188,33 @@ Manual PDF publication is a local workspace operation: it copies reviewed artefa
 
 ## New Site Initialization
 
+### Retained Letter Integration
+
+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.
+
+The complete seal lives at `.unaltraweb/artifacts/<id>/bundle/`, alongside an
+unchanged-schema v1 integration record and a separate native `binding.json`.
+Only the byte-identical mapped PDF under `assets/documents/` is public. A new
+draft page/chapter binds it using the `retained_document` Liquid tag and a literal
+permalink. `site_check`, `site_doctor`, Jekyll and manual PDF preparation verify
+the corresponding domain, seal, mapping and native reference; the PDF fingerprint
+includes every retained dependency and checker. Producer sources are never run.
+
+Writes require the consumer Git root, ignored/untracked recovery staging and
+non-ignored durable paths. They are descriptor-relative and create-only, with
+preflight and final integrity checks. The project/import locks coordinate with
+native readers and the PDF controller. An interrupted operation retains its
+prepared tree and partial files, without destructive rollback. An explicit retry
+may adopt identical bytes; conflicts preserve existing content. Successful
+identical reimport preserves authored prose. See the
+[author reference](../_documentation/en/45-retained-documents.md) and
+[owner acceptance record](retained-letter-import.md) for bounds and evidence.
+
+### Package-Owned Initialization
+
 `new_web` is intended for empty or nearly-empty website repositories. It creates common runtime files, profile-specific configuration, localized home pages, the content paths required by the selected profile, and `.unaltraweb/scaffold.json`. All scaffold assets are shipped inside the `unaltraweb_mcp` Python package and MCP Docker image; environment variables, sibling checkouts, and arbitrary template paths are not consulted.
 
 The `unaltremanual` scaffold also creates `context/writing-profile.md` with a usable default editorial policy and `.unaltraweb/computations.yml` with both BOM-selected workers, `_chapters` and `assets/quarto` source roots, and a generated-asset root. Customize the writing profile for the manual's audience, voice, terminology, evidence policy, language workflow, and review requirements. Computation configuration is consumer-owned rather than scaffold-managed so a project can add lockfiles, dependency paths, or extension Dockerfiles without creating scaffold-sync conflicts. PDF generation and Vega manifests remain opt-in project configuration.

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

@@ -0,0 +1,205 @@
+# unaltraweb 0.5.1 delivery closeout
+
+Publication: **2026-09-30**, [v0.5.1](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.5.1).
+Owner coordination: [issue 76](https://github.com/dosquartsdedocs/unaltraweb/issues/76).
+This supersedes the pending-publication status of the retained preparation and
+follow-up reports without changing their historical bytes.
+
+## Revisions, review and integration
+
+| Role | Revision / evidence |
+| --- | --- |
+| Initial accepted local source | `217340cadc9db85aa717e020682068b9ce0ef379` |
+| Bundler/core implementation, retained consumer pin | `c23e12b0e1567d18a7f9dd225dc062ddc77dad8b` |
+| Closeout installed-launcher default correction | `1640572ccd9156037b9a4c0018b4c849a027296f` |
+| Integrated source producing the release artifacts | `aab5a7b030cd711b40770a3f44ad3a356eab90da`, [PR 77](https://github.com/dosquartsdedocs/unaltraweb/pull/77) |
+| Receipt-only branch commit | `8a0b6ce0d0c875ac6a8b86d9e354b8a388b5d038`, direct child of the source above |
+| Receipt integration and release tag target | `e842c733c8a274279dd5efdc3618e20669f29037`, [PR 78](https://github.com/dosquartsdedocs/unaltraweb/pull/78) |
+| Annotated `v0.5.1` tag object | `c4901b583c777a050cd53e1e96643ad53b7c0f64` |
+
+Both integrations used merge commits, preserving the approved core's ancestry.
+The receipt integration's first parent is exactly the artifact source; its diff
+from that parent contains only `release-candidates.json`. The source pin still
+names the real approved core implementation. The later closeout correction
+changes host-launcher selection, not that Jekyll/Bundler core implementation.
+
+All preparation commits and the complete base diff were reviewed. The remaining
+delivery finding was that the installed 0.5.1 launcher still selected the older
+0.5.0 MCP. Commit `1640572` fixes that: the console adapter uses explicit
+`--image`, then `UNALTRAWEB_MCP_IMAGE`, then its own BOM release image. The installed
+Make profile also defaults to its own release. The checkout's stricter digest
+pin remains a separate post-release operation. Default and override precedence
+are exercised by the factory-free wheel gate.
+
+Agent review records are attached to both PRs; they do not claim human review.
+Copilot could not review because of quota exhaustion and was not counted as a
+completed review. Explicit owner authorization covered integration and, in two
+later approvals, credentialed candidate preparation and final publication.
+All protected checks and conversation requirements passed without bypass.
+
+## Published receipt and artifacts
+
+[Tagged native receipt](https://github.com/dosquartsdedocs/unaltraweb/blob/v0.5.1/release-candidates.json):
+
+```text
+schema_version: 1
+release: v0.5.1
+source_commit: aab5a7b030cd711b40770a3f44ad3a356eab90da
+receipt SHA-256: 0e9d8f0589fa1ebf3aa067f0558523868fec29210927d1715f22e16e72cb30ec
+```
+
+Exactly four ready components are recorded:
+
+| Component | Published name / repository | SHA-256 / OCI repository digest |
+| --- | --- | --- |
+| Gem | `unaltraweb-0.5.1.gem` | `818bfbb53af4de16383a211e4224ab7ab77a2647afe8703f9c3f7c1ebd123c64` |
+| Wheel | `unaltraweb_mcp-0.5.1-py3-none-any.whl` | `354bff5894073d66e064b5bcd0887c5963f58035ee2b1751b541722f345cf08f` |
+| Base runtime | `ghcr.io/dosquartsdedocs/unaltraweb` | `sha256:3712453bf30289f02181cff0c095ecda563306e1d8a8f2a0e087c65ea9c8d730` |
+| Full MCP | `ghcr.io/dosquartsdedocs/unaltraweb-mcp` | `sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692` |
+
+The GitHub Release retains both packages and `SHA256SUMS`; that checksum file's
+SHA-256 is `5cd3be237015841b65583b9b54b9df37c8a4b642e9231e6ee522d8d37d90821a`.
+These are the newly downloaded workflow/publication bytes, not the earlier local
+0.5.1 candidates whose hashes appear in the follow-up report.
+
+Native component selections retained unchanged:
+
+- PDF 0.5.0:
+  `ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:9e0b3a45753c170b795e9a9d6df61580085c113436beac5bf6c8de69b6562097`.
+- Python 0.4.0:
+  `ghcr.io/dosquartsdedocs/unaltraweb-compute-python@sha256:18cb269811bd4005800382da25a480ec2bca7eac8d0501ad1ef36bad1c0f8cd9`.
+- R 0.4.0:
+  `ghcr.io/dosquartsdedocs/unaltraweb-compute-r@sha256:928ffb93f221e09e8b929157dee473b838e061915a2eb67224e4124b85f81837`.
+- Web capture 0.4.0:
+  `ghcr.io/dosquartsdedocs/unaltraweb-web-capture@sha256:0bf1bc67fe63e1440bffe708a168beefa11c54441650a871ab99380d362f7c1e`.
+- Diavisuals/Vegavisuals 0.4.0: the same BOM-selected hashed wheels and provider
+  receipt contract. Their exact references remain in `component-contract.json`.
+
+The image workflow additionally built/tested a PDF verification candidate
+`sha256:55c88a6e805f0612b8dced992868aab8443f077d72ecc9aaf7ff1bf862a154a6`.
+It is not selected by the BOM, not included in this receipt, and was not promoted
+as a 0.5.1 PDF component. The original 0.5.0 receipt remains at its existing tag,
+with SHA-256 `e57a9dbb041c1e7fcd781cd1524f4de0317382e0f7303bb36bfa59c0b6d1cb9b`.
+
+## CI, signing and publication gates
+
+| Gate | Successful run |
+| --- | --- |
+| Integration PR CI | [36780877307](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36780877307) |
+| Integration PR CodeQL | [36780877311](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36780877311) |
+| Integrated-source CI | [36785554970](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36785554970) |
+| Signed image build, verification, tests | [36785858325](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36785858325) |
+| Package preparation | [36785861424](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36785861424) |
+| Receipt PR CI | [36788752930](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36788752930) |
+| Receipt/tag target CI | [36789293544](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36789293544) |
+| Tag CI | [36791298216](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36791298216) |
+| Semver image promotion | [36791298413](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36791298413) |
+| PyPI and RubyGems Trusted Publishing | [36791301396](https://github.com/dosquartsdedocs/unaltraweb/actions/runs/36791301396) |
+
+GitHub-signed OCI provenance was verified against the owner workflow and exact
+source digest in the candidate and promotion jobs. Local inspection additionally
+confirmed the OCI digests and source revision labels. The package workflow's
+immutable artifact ID is `11129633290`, archive digest
+`sha256:60a68862dcedec3747ed49112b66d10e697765a0ab5d6f249b33690aa5c5a3c5`.
+The publication verifier bound that run, source, artifact inventory and checksums
+to the receipt and annotated tag object before granting OIDC publishing authority.
+
+Before promotion, both the actual receipt-only branch and merged tag target
+passed `make distribution-release-check`. The merged `main` and then the annotated
+tag passed `--require-release-ready --validate-publish-ref --components
+gem,wheel,runtime,mcp,manual_pdf`. `verify_package_publish.py release` and exact
+package staging also passed. The old receipt was never substituted as evidence
+for the new version. Strict release validation refers to this receipt/tag
+revision, not to later ordinary post-release source commits.
+
+## Populated-cache evidence
+
+The previous final evidence was first rehashed at intake: gem, wheel and
+`final-roundtrip/evidence.json` matched the follow-up report. All six preserved
+files still matched in every profile, and the manual PDF matched its manifest.
+
+The actual signed candidate and downloaded CI wheel then passed a new full
+roundtrip in **all four profiles**: `unaltreselfie`, `unaltreprojecte`,
+`unaltredocs`, `unaltremanual`.
+
+1. A real 0.4.0 build populated the generated lock with `google-protobuf 4.36.1`.
+2. Unpatched 0.5.0 failed as expected on a separate populated copy.
+3. The signed corrected full MCP passed two builds, preview and HTTP.
+4. Returning to the unchanged published 0.4.0 passed two builds, preview and HTTP.
+5. Gemfile, Gemfile.lock, Makefile, scaffold baseline and both historical generated
+   Gemfile/lock files retained their original SHA-256 values throughout.
+
+New evidence:
+`/tmp/opencode/unaltraweb-closeout-051/candidate-roundtrip/evidence.json`, SHA-256
+`b5a2935359103983ff497760d8e9c367318ed9f77741ae1c5404a56449547179`.
+An external recording wrapper ran the unchanged owner driver and retained the
+manual tool responses plus PDF/cover bytes for both stages; it did not change
+arguments, caches or runtime behavior.
+
+| Manual artifact | SHA-256 |
+| --- | --- |
+| Corrected stage PDF | `203b39def968b644d1d0d3999827516e0e00aa8dd6b85202b33167d68dcb150e` |
+| Return-0.4 PDF | `aba2802d4e0d978c8acc0cfbfc26a84607739b0953756a6bdb16fabbc43defa0` |
+| Both stage covers | `afc3ba16ca919a7879f4629023e6316b77e31e56403e82edb7168f3181a3dc9d` |
+
+The responses report `ok: true`, `publishes: false`; preview cleanup remained
+receipt-bound. No cache was emptied to obtain a pass. The historical image
+selections and reproduction command remain in `owner-followup-76.md`; this run
+used the receipt's full MCP digest as `--fixed-image` and the downloaded CI wheel.
+
+## Public-download and installed acceptance
+
+Artifacts are retained under `/tmp/opencode/unaltraweb-closeout-051/`:
+`packages/`, `verified-packages/`, `published/`, `github-release/`,
+`installed-candidate/`, `installed-published/`, and `candidate-roundtrip/`.
+
+- Anonymous PyPI and RubyGems downloads match the receipt exactly; metadata and
+  downloaded bytes were independently compared.
+- Both `0.5.1` and `v0.5.1` GHCR aliases were checked with an empty Docker client
+  configuration and match the expected OCI index digests.
+- GitHub Release assets were downloaded again and pass their `SHA256SUMS`.
+- The public wheel was installed non-editably in a new venv. Its default
+  `prepare`/`check` selects and runs MCP 0.5.1 without a local core.
+- The public gem installs into an isolated gem home and activates as 0.5.1 using
+  the image's preinstalled Ruby dependencies. An initial probe artificially
+  omitted standard gem paths and failed to find `rexml`; retaining `Gem.path`
+  corrected the probe. This is not a claim of a network-fresh dependency install.
+- The host's older Buildx did not render the requested digest-only template;
+  anonymous verification instead checked the exact top-level `Digest:` field.
+- Closeout source tests reported **562 cases, 532 passed, 30 optional skips**;
+  distribution, workflow, wheel and prose checks passed. CI additionally ran its
+  Python matrix, Ruby, PDF, MCP, reproducibility and docs gates.
+- The post-pin local recheck reported **562 cases, 533 passed, 29 optional skips**
+  after the public image became available. Distribution, workflow, wheel,
+  `mcp-check`, `mcp-smoke`, docs build and diff gates passed with isolated
+  `unaltraweb-closeout-051-*:post-pin` tags and a fresh smoke fixture. The smoke
+  used the selected published PDF digest. These local development builds do not
+  replace the published release artifacts.
+
+Observed local configuration IDs (distinct from OCI repository digests):
+runtime `sha256:5c406a7981118203070517b6689f2f4f03ac7fd2b5626b52ed96fe14009d67b9`;
+full MCP `sha256:e7b2bd34751c2d3a30f9974f46c64e30a1a2fbd9ba412279234a5f24ff197eda`.
+
+## Post-release pin and remaining adoption scope
+
+The post-release source change on `chore/76-pin-published-mcp-0.5.1` accompanies
+this report. `Makefile` and `scripts/unaltraweb-mcp-bootstrap.sh` select
+`ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692`;
+the pin regression and current documentation are updated. Its PR/merge and final
+clean-main confirmation are recorded in issue 76 after protected CI completes.
+Published packages, receipt and tag are not rebuilt by this source update.
+
+An actual `MCP_CONSUMER_WORKSPACE`-bound `make mcp-stdio` session was launched from
+the post-pin checkout against a new empty synthetic consumer. Initialize and
+`detect_site` succeeded, and Docker inspection proved the session used the public
+MCP configuration ID `sha256:e7b2bd34751c2d3a30f9974f46c64e30a1a2fbd9ba412279234a5f24ff197eda`.
+The temporary session exited cleanly. The post-pin `mcp-build` and bootstrap
+`--check` also selected the published image without rebuilding it.
+
+The installed package already selects its own release; existing MCP processes
+keep their image until reconnected. No real manual, client registration or shared
+authoring worker was migrated. Historical Makefile adaptation remains restricted
+to matching baselines; customized Makefiles require explicit owner integration.
+The accepted evidence covers these exact Linux/amd64 tuples, not an untested
+version interval or architecture. No new H1 fields were introduced. Consumer
+adoption and central catalogue integration remain their own later sessions.