unaltraweb 0.5.0 → 0.6.0

data/docs/agents/mcp-contract.md

@@ -16,13 +16,34 @@ 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.
 
+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`,
+`mcp-smoke`, `mcp-stdio` and `mcp-down` against the selected released image;
+it cannot build checkout images. `unaltraweb-mcp-docker serve --project PATH`
+is the direct installed entry point. Preparation may pull, whereas check/smoke
+require a locally prepared image and use no consumer or Docker socket mount.
+The copied schema-v1 descriptor retains the same server, workspace, inventory
+and dependency identities. The released 0.5.0 wheel lacks these host assets;
+the full 0.5.0 GHCR runtime already supports the operations they launch.
+The installed profile selects its own BOM release image by default and resolves
+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`.
+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 Python wheel 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 BOM selects the published `diavisuals v0.3.1` and `vegavisuals v0.3.1` 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 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.
 
 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 +102,7 @@ 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
@@ -95,6 +117,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. |
@@ -156,6 +180,33 @@ Manual PDF publication is a local workspace operation: it copies reviewed artefa
 
 ## New Site Initialization
 
+### Retained Letter Integration
+
+The 0.6.0 development increment 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.
@@ -226,7 +277,7 @@ For companion linking, compare the selected BOM and dependency capabilities with
 each running provider's `factory_manifest`, `compatibility_status` and release
 evidence. A development checkout announcing a future version is not a published
 release or evidence that a long-lived MCP process has upgraded. The current
-published companion selections are `diavisuals v0.3.1` and `vegavisuals v0.3.1`.
+published companion selections are `diavisuals v0.4.0` and `vegavisuals v0.4.0`.
 Advance them only after their immutable releases exist and their receipt/tool
 contracts have been verified; source-checkout version drift remains an explicit
 control-plane finding, not a reason to weaken receipt validation.
@@ -247,6 +298,17 @@ Translations are a pre-publication task. They should preserve `ref`, citations,
 
 Run `site_doctor` and `site_check`, then resolve any blocking validation result before compiling. `build_site` reuses the active MCP container and the consumer's `build-native` target, and runs the local HTML audit after a successful Jekyll process. The generated `test-native` target also runs `html_audit`. This is intentionally different from the consumer's normal host-side `make build`, which starts a Jekyll container and would create a nested runtime when called from MCP.
 
+In 0.5.1, `bundler_runtime` prepares offline, identity-keyed generated locks under
+`tmp/unaltraweb-bundle`, verifying their receipts on reuse and retaining edited
+or incomplete caches. Identity includes the actual Ruby/Bundler/gem inventory,
+core inputs and hashed Bundler configuration. Updated native targets use private
+invocation copies; an explicit author `LOCAL_GEMFILE` requires its own existing frozen lock.
+For unchanged historical package Makefiles, `build_site` and the same-image
+preview pass invocation-owned copies through `LOCAL_GEMFILE`, preserving the old
+generated lock and all author sources. A modified Makefile is not overridden.
+The fix requires a containing runtime, and does not mutate released 0.5.0 images
+or real consumers. See [the populated-cache follow-up](owner-followup-76.md).
+
 Make delegation and feasible Docker control calls use one bounded subprocess runner. Status and control commands have short deadlines, builds/renders have target-specific longer deadlines, timeout terminates the process group and returns code `124`, and retained stdout/stderr is capped with explicit truncation fields. Factory commands that promise JSON fail closed when output is empty, malformed, non-object, non-finite, or truncated. Every bind source and target is encoded as a quoted Docker CSV field, so commas or quotes in host paths cannot introduce duplicate mount fields; carriage-return and newline path characters are rejected before canonicalization or mount construction. Computation, capture, and PDF containers carry factory, worker-role, project, and invocation-token labels plus cidfiles; after timeout cleanup selects all four labels and cannot remove unrelated containers.
 
 A preview must outlive one MCP tool invocation, so it runs in a separate container made from the same MCP/Jekyll image. Its deterministic name is derived from the canonical host project path and it carries the factory, role, and project labels. Its isolated container always listens on port `4000`; the default host port is allocated atomically by Docker on loopback and is reported as `preview_status.port`, preventing the old cross-project collision on host port `4000`. Starting an already-running preview probes it again instead of creating a duplicate. A preview created under the former fixed-port default is accepted as compatible with the new automatic default until it is stopped; its next start uses dynamic allocation. Changing an explicit requested port or profile still requires stopping first. Stdio session containers intentionally have Docker-generated names so independent clients can run simultaneously, but carry the same stable project ID and labels as previews and capture resources. That process-level capability does not authorize concurrent editing sessions in one repository. Stop and cleanup operations select ownership labels before removing anything.

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.

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

@@ -0,0 +1,144 @@
+# Owner follow-up 76: populated Bundler transitions and 0.5.1 preparation
+
+This follows the immutable historical intake in
+[owner-preparation-2026-09-29.md](owner-preparation-2026-09-29.md) and the hub's
+`owner-followups/05-unaltraweb.txt`. Tracking and final execution results:
+[issue 76](https://github.com/dosquartsdedocs/unaltraweb/issues/76).
+
+## Correction and source identity
+
+Implementation commit: `c23e12b0e1567d18a7f9dd225dc062ddc77dad8b`, on the existing
+`feat/76-distributed-mcp-launcher` primary checkout. Local commits were explicitly
+authorized. The following integration commit pins `consumer_integration.core_sha`
+to this real 0.5.1 core, so the generated Gemfile/lock/workflow tuple no longer
+combines a 0.5.1 gem version with a 0.5.0 source revision.
+
+The correction lives in `src/unaltraweb_mcp/bundler_runtime.py` and is included in
+both wheel and gem. It keys generated state by the actual Ruby/platform, Bundler,
+installed gem inventory, core dependency inputs and hashed Bundler configuration.
+No mutable Docker alias or project build default acts as the cache identity.
+
+- Offline `bundle lock --local` and `bundle check` prepare a new identity cache
+  under `tmp/unaltraweb-bundle/<hash>/` and record exact Gemfile/lock hashes.
+- Reuse verifies that receipt. Edited, unsafe or incomplete caches are retained
+  and rejected rather than silently reset. No old generated tree is removed.
+- Each build/preview gets private invocation copies. This also accommodates
+  Bundler 4's local default-gem checksum completion without disabling checksums
+  or changing a cached or authored lock. An initially attempted frozen generated
+  lock exposed empty `rake` CHECKSUMS entries in the owner runtime; private copies
+  fixed that additional regression. Explicit author Gemfiles require an existing
+  lock and run with `BUNDLE_FROZEN=true`.
+- Updated package scaffolds use the helper in native build/test/serve targets.
+- MCP build and same-image preview adapt unchanged historical Makefiles only
+  when their bytes match the recorded package scaffold baseline. They pass
+  `LOCAL_GEMFILE` pointing to an invocation copy. The original
+  `tmp/Gemfile.local.lock`, project Gemfile/lock, Makefile and scaffold manifest
+  remain byte-identical. Custom Makefiles retain their own dependency policy;
+  adopting the new native targets remains an explicit scaffold update.
+
+The already-published 0.5.0 image is still unpatched. The roundtrip fixture retains
+its exact Ruby/gem layers and adds the new owner controls as a separately named
+test image; this proves the correction against the problematic 0.5.0 inventory,
+not a new empty cache or an unrelated fresh Ruby installation.
+
+## Component decision
+
+| Component | 0.5.1 preparation |
+| --- | --- |
+| Core gem | New 0.5.1: ships the runtime helper and updated controls/docs. |
+| Python wheel | New 0.5.1: installed Docker launcher, cache orchestration, scaffolds and integration tuple. |
+| Full MCP image | New 0.5.1: required to run the correction without a local core. |
+| Base Ruby/Jekyll image | Coordinated 0.5.1 candidate under the existing image workflow. The Dockerfile/toolchain recipe itself is unchanged. |
+| Manual PDF | Reuse published 0.5.0 digest `sha256:9e0b3a45753c170b795e9a9d6df61580085c113436beac5bf6c8de69b6562097`. |
+| Python/R computation, web capture | Retain their published 0.4.0 versions/digests. |
+| Diavisuals/Vegavisuals | Retain published hashed 0.4.0 wheels and current receipt contract. |
+
+The native validator now permits a released, digest-pinned PDF to retain its
+actual version across a coordinated core patch. Pending/ready PDF candidates,
+mutable aliases and other repositories do not receive that exception. The
+existing source image workflow may build a PDF verification candidate; it does
+not thereby replace the selected released worker or put it in the new receipt.
+The new receipt must contain exactly `gem`, `wheel`, `runtime`, `mcp` when those
+four components remain `ready`.
+
+The 0.5.0 receipt is unchanged, SHA-256
+`e57a9dbb041c1e7fcd781cd1524f4de0317382e0f7303bb36bfa59c0b6d1cb9b`.
+Historical tags and published packages are untouched. The launcher retains the
+last published MCP digest until a separately reviewed post-release selection.
+Local 0.5.1 artifacts have new names and are not registry-published candidates.
+
+## Regressions and pre-integration owner gates
+
+Executed on Linux/amd64:
+
+- All four historical profiles: successful 0.4.0 host build first, containing
+  `google-protobuf (4.36.1-x86_64-linux-gnu)` in the retained generated lock.
+- Unpatched 0.5.0 fails with the known missing `google-protobuf (4.36.1)` on a
+  disposable copy of each populated consumer; this negative control is required.
+- Corrected controls on 0.5.0 Ruby layers: two builds, preview and HTTP pass.
+- Return to unchanged published 0.4.0: two builds, preview and HTTP pass.
+- Hash comparisons verify preservation of both authored and retained generated
+  Gemfile/lock pairs, Makefile and scaffold baseline across the roundtrip.
+- The manual additionally builds/stages real PDFs and performs receipt-bound
+  preview cleanup. No source mount or real manual is used.
+- Unit regressions cover populated A→B→A cache reuse, modified generated locks,
+  symlink ancestors, author Makefile overrides, frozen author locks, credential
+  hashing, and private checksum-completion copies.
+
+Initial evidence is retained under
+`/tmp/opencode/unaltraweb-followup-76/all-profiles-first/` (three completed
+profiles) and `manual-first-roundtrip/` (completed manual). The first combined
+run reached its 20-minute terminal limit during the final historical preview;
+the manual was rerun to completion. No test container remained from that timeout.
+
+Before integration: **562 unit tests, 30 optional skips**; distribution, workflow,
+wheel, gem, MCP CLI, MCP stdio/manual-preview, prose and docs-build gates passed.
+The final native smoke passed using `unaltraweb-followup-76-mcp:precommit3`; the
+earlier frozen-generated-lock attempts remain failed intermediate evidence.
+The old report's 0.5.0-labelled local wheel is not a release artifact.
+
+## Final-version artifact gate protocol
+
+After pinning the corrected core, build the final 0.5.1 wheel and gem from that
+clean integration commit, retain their hashes, install the wheel non-editably,
+and repeat the gates against those bytes. Retain final outcomes and immutable
+local image IDs in issue 76 rather than inserting a self-referential artifact
+digest into its own source. Evidence belongs under
+`/tmp/opencode/unaltraweb-followup-76/final-artifacts/` and
+`/tmp/opencode/unaltraweb-followup-76/final-roundtrip/`.
+
+The reproducible populated-cache command is:
+
+```bash
+python3 test/bundler_transition_smoke.py \
+  --launcher /tmp/opencode/unaltraweb-followup-76/final-venv/bin/unaltraweb-mcp-docker \
+  --legacy-image ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:389bc585cdb4fc89d3372f4896a55fe26e15df38b46bc114ce44fdb3f1c8deb9 \
+  --broken-image ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:36d17edbade77edb40a687f6a744203c6329acb33fbc2eb255e88d9ff1a42c98 \
+  --fixed-image unaltraweb-followup-76:051-on-050-final \
+  --output /tmp/opencode/unaltraweb-followup-76/final-roundtrip
+```
+
+Use a fresh output directory and a sufficiently long outer deadline; the driver
+never clears a populated fixture to obtain a pass. The test overlay is built
+with `test/bundler_transition.Dockerfile`, the exact published 0.5.0 base digest,
+and a named `wheel` build context containing the final wheel. Installation uses
+`--no-index --no-deps`, and the build uses `--network none`. Ordinary owner
+`mcp-check`/`mcp-smoke` also run against separate test tags and fresh fixtures.
+
+## Publication status and next gate
+
+Issue 76 stays open until integration and release. No PR, push, tag, workflow
+dispatch, registry upload or consumer activation is authorized by the local
+commit approval. The native schema remains unchanged; H1 range/catalogue fields
+are not invented here. Tested points are the explicit tuples above, not a
+continuous semver compatibility interval.
+
+The strict `distribution-release-check` is mandatory and must remain blocking
+until there is a new 0.5.1 receipt-only child commit with the correct default-branch
+candidate ancestry, signed image digests and verified package checksums. The
+retained 0.5.0 receipt cannot satisfy that gate and is not rewritten to do so.
+Next: reviewed branch integration (preserving or deliberately refreshing the
+core pin), approved signed candidate/package preparation on the resulting source,
+new receipt-only commit, strict gate, then separately approved promotion and
+post-release launcher selection. TIG, TIGIT, Geodisseny, their active registrations
+and their image/worker selections are outside this test and adoption scope.