unaltraweb 0.6.0 → 0.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 33193d7900939e3cf2e4e9769e8fd9443e0a7242eaa73aef1d93b8ffcee6e79b
-  data.tar.gz: 3ef63e4f55c4b369e0926be413eb2da4d3702f49ac733d84dedc952bb1ec563c
+  metadata.gz: 5697f730a670b00edc9d6cda6bb653552470c6c58667d27557e33309203f552c
+  data.tar.gz: 1fb32fa043262eca9724aed6dc0184246bc6012f2a6261037f03203ef1265945
 SHA512:
-  metadata.gz: eb799646f841a4444d315aa4a71d161ec83acacbef75f36fe00b8db7242699be40147c2829bedee18f249f3085b51328cd18a902f317196d518b4f2b8e11a9f2
-  data.tar.gz: cfe5a103146718d7bbae56c9821b2dabdc0fdf1bcde966779ee41ea96c468bd795446202844a56a0974919ce4bca33e2d90e5c6de98e8e95936b1335c44dca86
+  metadata.gz: d43c24786b83d17e9cf8cc238eb12227a3d46581fbc550468c95549f9061cd60b6eb4681021855e646929ca41f6b51de850e2db183d956dfd72876b6e48a8a2e
+  data.tar.gz: 15c574473f3c71b81b624b08bf4767902deebfc5f0164abc668f43dae6f33f9a0eb8c4a45e1d734a03bd4540b42b81d4e0a77aa8f42ae46566e7cd81cf7af19f

data/Makefile

@@ -1,9 +1,9 @@
 PYTHON ?= python3
 override PROJECT := $${MCP_CONSUMER_WORKSPACE:?MCP_CONSUMER_WORKSPACE is required}
 override PROJECT_ROOT := $(PROJECT)
-MCP_RUNTIME_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.6.0
-MCP_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.6.0
-MCP_RELEASE_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692
+MCP_RUNTIME_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.7.1
+MCP_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.7.1
+MCP_RELEASE_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:b84cdb404ba7bab5ff0b14fa8a7ee93d7293e829cf32e28ff0dacaa8afff4677
 MCP_DOCKER_BUILD_NETWORK ?= default
 INIT_SITE_PROFILE ?= unaltreselfie
 NEW_WEB_PROFILE ?= unaltreselfie
@@ -40,8 +40,8 @@ WEB_CAPTURE_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-web-capture@sha256:0bf1b
 WEB_CAPTURE_DEV_IMAGE ?= unaltraweb-web-capture:dev
 WEB_CAPTURE_DOCKER_BUILD_NETWORK ?= default
 VEGAVISUALS_CLI ?=
-DOCKER_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.6.0
-MANUAL_PDF_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:0ba267cb87f53ebaca4e31805fe00610cd61fdf97a8d2c3692f4655700dceaed
+DOCKER_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.7.1
+MANUAL_PDF_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:1bb3f2dafd741e96c28639ec1cc8ccaeb81cbaa73e649f787c0b4ef59997bd4b
 MANUAL_PDF_DEV_IMAGE ?= unaltraweb-manual-pdf:dev
 MCP_SMOKE_MANUAL_PDF_IMAGE ?= $(MANUAL_PDF_IMAGE)
 MCP_SMOKE_PROJECT ?=
@@ -71,7 +71,7 @@ export MANUAL_RELEASE_SELECTOR MANUAL_PDF_LANG MANUAL_PDF_PUBLISH_DRY_RUN MANUAL
 UNALTRAWEB_WORKER_ROLE ?=
 UNALTRAWEB_WORKER_PROJECT ?=
 UNALTRAWEB_WORKER_TOKEN ?=
-WORKER_LABEL_ARGS = $(if $(strip $(UNALTRAWEB_WORKER_TOKEN)),--label "io.context.mcp-factory=unaltraweb" --label "io.context.mcp-role=$(UNALTRAWEB_WORKER_ROLE)" --label "io.context.mcp-project=$(UNALTRAWEB_WORKER_PROJECT)" --label "io.context.mcp-worker-token=$(UNALTRAWEB_WORKER_TOKEN)",)
+WORKER_LABEL_ARGS = $(if $(strip $(UNALTRAWEB_WORKER_TOKEN)),--label "io.context.mcp-factory=unaltraweb" --label "io.context.mcp-role=$(UNALTRAWEB_WORKER_ROLE)" --label "io.context.mcp-project=$(UNALTRAWEB_WORKER_PROJECT)" --label "io.context.mcp-worker-token=$(UNALTRAWEB_WORKER_TOKEN)",) $(if $(strip $(UNALTRAWEB_RUNTIME_SESSION)),--label "io.context.mcp-session=$(UNALTRAWEB_RUNTIME_SESSION)",)
 DOCS_CONTAINER ?= unaltraweb-docs-local
 DOCS_HOST ?= 0.0.0.0
 DOCS_PORT ?= 4000
@@ -295,17 +295,18 @@ manual-compute-render: ## Execute sources and atomically publish Markdown and fi
 	  python_image="$(COMPUTE_PYTHON_IMAGE)"; r_image="$(COMPUTE_R_IMAGE)"; \
 	  if test "$$engine" = "r"; then r_image="$$image"; else python_image="$$image"; fi; \
 	  if ! docker image inspect "$$image" >/dev/null 2>&1; then \
+	    if test "$${UNALTRAWEB_MANAGED_RUNTIME:-0}" = 1; then printf '%s\n' 'Selected computation image is not prepared; managed execution never builds or pulls' >&2; exit 1; fi; \
 	    COMPUTE_PYTHON_IMAGE="$(COMPUTE_PYTHON_IMAGE)" COMPUTE_R_IMAGE="$(COMPUTE_R_IMAGE)" COMPUTE_DOCKER_BUILD_NETWORK="$(COMPUTE_DOCKER_BUILD_NETWORK)" $(PYTHON) "$(COMPUTE_SCRIPT)" image --project "$(PROJECT_ROOT)" --engine "$$engine" >/dev/null; \
 	  fi; \
 	  identity=$$(docker image inspect "$$image" --format '{{.Id}}'); \
 	  digest=$$(docker image inspect "$$image" --format '{{join .RepoDigests ","}}'); \
 	  set --; if test -n "$(UNALTRAWEB_WORKER_TOKEN)"; then cidfile="$$runtime_dir/worker-$(UNALTRAWEB_WORKER_TOKEN)-$$engine.cid"; rm -f "$$cidfile"; cidfiles="$$cidfiles $$cidfile"; set -- --cidfile "$$cidfile"; fi; \
-	  docker run --rm "$$@" $(WORKER_LABEL_ARGS) --user "$(LOCAL_UID):$(LOCAL_GID)" --network none --read-only --cap-drop ALL --security-opt no-new-privileges --pids-limit "$(COMPUTE_PIDS_LIMIT)" --cpus "$(COMPUTE_CPUS)" --memory "$(COMPUTE_MEMORY)" --tmpfs /tmp:rw,noexec,nosuid,size=1g \
+	  docker run --rm --pull never "$$@" $(WORKER_LABEL_ARGS) --user "$(LOCAL_UID):$(LOCAL_GID)" --network none --read-only --cap-drop ALL --security-opt no-new-privileges --pids-limit "$(COMPUTE_PIDS_LIMIT)" --cpus "$(COMPUTE_CPUS)" --memory "$(COMPUTE_MEMORY)" --tmpfs /tmp:rw,noexec,nosuid,size=1g \
 	    -e HOME=/tmp -e COMPUTE_PYTHON_IMAGE="$$python_image" -e COMPUTE_R_IMAGE="$$r_image" \
 	    -e UNALTRAWEB_COMPUTE_IMAGE_ID="$$identity" -e UNALTRAWEB_COMPUTE_IMAGE_DIGEST="$$digest" \
 	    --mount "$$project_mount" \
 	    --mount "$$runtime_mount" \
-	    -w /project --entrypoint python3 "$$image" \
+	    -w /project --entrypoint python3 "$$identity" \
 	    /opt/unaltraweb/computations/render.py render --project /project --engine "$$engine" $(if $(strip $(COMPUTE_SOURCE)),--source "$(COMPUTE_SOURCE)",) $(if $(filter 1 true TRUE yes YES y Y,$(COMPUTE_CONFIRM_OVERWRITE)),--confirm-overwrite,) $(if $(filter 1 true TRUE yes YES y Y,$(COMPUTE_STALE_ONLY)),--stale-only,) $(if $(strip $(COMPUTE_MODE)),--mode "$(COMPUTE_MODE)",) >> "$$results"; \
 	done; \
 	if test -z "$(strip $(COMPUTE_SOURCE))"; then $(PYTHON) "$(COMPUTE_SCRIPT)" prune --project "$(PROJECT_ROOT)" >/dev/null; fi; \
@@ -382,13 +383,14 @@ define run_manual_pdf_worker
 	if test -n "$(UNALTRAWEB_WORKER_TOKEN)"; then runtime_dir="$(PROJECT_ROOT)/tmp/.unaltraweb/manual-pdf"; mkdir -p "$$runtime_dir"; cidfile="$$runtime_dir/worker-$(UNALTRAWEB_WORKER_TOKEN).cid"; rm -f "$$cidfile"; set -- --cidfile "$$cidfile"; fi; \
 	mount=$$(/bin/sh "$(DOCKER_MOUNT_SCRIPT)" "$(PROJECT_ROOT)" /project); \
 	trap 'test -z "$$cidfile" || rm -f "$$cidfile"' EXIT; \
-	docker run --rm "$$@" $(WORKER_LABEL_ARGS) --user "$(LOCAL_UID):$(LOCAL_GID)" -e HOME=/tmp -e "UNALTRAWEB_MANUAL_RELEASE_SELECTOR=$${MANUAL_RELEASE_SELECTOR}" --mount "$$mount" -w /project "$(MANUAL_PDF_IMAGE)" $(1) --project /project $(if $(strip $(MANUAL_PDF_LANG)),--language "$(MANUAL_PDF_LANG)",) $(2)
+	identity=$$(docker image inspect "$(MANUAL_PDF_IMAGE)" --format '{{.Id}}'); \
+	docker run --rm --pull never --network none --cpus 2 --memory 2g --pids-limit 256 "$$@" $(WORKER_LABEL_ARGS) --user "$(LOCAL_UID):$(LOCAL_GID)" -e HOME=/tmp -e "UNALTRAWEB_MANUAL_RELEASE_SELECTOR=$${MANUAL_RELEASE_SELECTOR}" --mount "$$mount" -w /project "$$identity" $(1) --project /project $(if $(strip $(MANUAL_PDF_LANG)),--language "$(MANUAL_PDF_LANG)",) $(2)
 endef
 
 manual-pdf-preflight: ## Run required PDF gates without contaminating the worker JSON stream
 	@$(MAKE) --silent --no-print-directory manual-compute-check >/dev/null
 	@$(MAKE) --silent --no-print-directory web-capture-check >/dev/null
-	@docker image inspect "$(MANUAL_PDF_IMAGE)" >/dev/null 2>&1 || docker pull "$(MANUAL_PDF_IMAGE)" >/dev/null
+	@docker image inspect "$(MANUAL_PDF_IMAGE)" >/dev/null 2>&1 || { if test "$${UNALTRAWEB_MANAGED_RUNTIME:-0}" = 1; then printf '%s\n' 'Selected PDF image is not prepared; managed execution never pulls' >&2; exit 1; fi; docker pull "$(MANUAL_PDF_IMAGE)" >/dev/null; }
 
 manual-pdf-status: ## Inspect manual PDF configuration and artefacts without Docker, network, or writes
 	@UNALTRAWEB_MANUAL_RELEASE_SELECTOR="$${MANUAL_RELEASE_SELECTOR}" $(PYTHON) "$(CURDIR)/scripts/manual/build_pdf.py" status --project "$(PROJECT_ROOT)" $(if $(strip $(MANUAL_PDF_LANG)),--language "$(MANUAL_PDF_LANG)",)

data/docs/_documentation/en/33-reusable-workflows.md

@@ -45,9 +45,34 @@ For `unaltremanual`, the `latest` channel is a manual-only deployment from the r
 
 Clean package scaffolds include a manual GitHub Pages wrapper pinned to a reviewed workflow revision. It has no push deployment trigger: a maintainer runs it only after local checks/renders and human review. The optional integration template retains additional local publishing experiments, but generated sites do not publish from local validation targets.
 
-The `consumer_integration` object in `src/unaltraweb_mcp/component-contract.json` is the single source for the reviewed core revision, workflow path, attested manual PDF image digest, and Vega renderer revision. The scaffold renders that tuple atomically into `Gemfile`, `Gemfile.lock`, and the packaged caller. The caller passes the existing `reviewed_sha` input through to the provider, so the reviewed `main` source is checked independently at both caller and provider boundaries.
-
-This pin-only integration follows the required M -> D -> B order: D was built from M's permanent identity before the caller recorded either value. Repeat that order for future provider updates; never use `@main` or substitute a mutable/version-tagged image for D.
+The `consumer_integration` object in `src/unaltraweb_mcp/component-contract.json` is the single source for the reviewed core revision, workflow path and revision, attested manual PDF image digest, and Vega renderer revision. The scaffold renders that tuple atomically into `Gemfile`, `Gemfile.lock`, and the packaged caller. From 0.7.1, `site_deploy_workflow_sha` is independent of `core_sha`; older records default to their core pin. The caller passes the existing `reviewed_sha` input through to the provider, so the reviewed `main` source is checked independently at both caller and provider boundaries.
+
+The 0.7.1 deployment workflow reads the exact accepted PDF digest and its producer
+commit from the defining provider revision's `deployment_contract` in the BOM.
+It fetches bounded JSON from that immutable provider commit, independently of
+the consumer checkout. It checks the pulled image's revision label against that record, rather
+than assuming the worker and a later workflow revision share a commit. Unknown
+digests fail before Docker access. The reviewed records cover PDF workers 0.5.0
+and 0.6.0; extending them requires a provider review and published-worker tests.
+The records are data in the contract, rather than a release list embedded in the
+workflow program. Release readiness checks the selected workflow's code and own
+records; CI generates a caller and executes the workflow it actually references.
+
+A reviewed deployment-only workflow fix can therefore be pinned independently
+of the site's Gem/core revision while retaining an already-accepted PDF worker.
+Update the caller's `uses:` to the immutable corrected workflow commit, review
+that consumer change, and dispatch with the resulting reviewed `main` SHA. The
+existing Gem, PDF and Vega selections need not change for this workflow repair.
+Such a local caller override remains subject to normal scaffold-update conflict
+review. A later package release can incorporate its own reviewed integration tuple.
+Never use `@main` or a mutable/version-tagged image as a substitute for these pins.
+
+The 0.7.1 update plan recognizes the exact reviewed one-line issue-86 caller fix
+by both its original baseline hash and current content hash. It lists this as a
+`migrations` entry and requires the normal reviewed plan/atomic apply. Additional
+local edits still produce a conflict; authored content and unrelated files are
+preserved. This lets a known provider repair converge to the next managed tuple
+without treating arbitrary custom workflow code as package-owned.
 
 ## Stable manual releases
 

data/docs/_documentation/en/40-distribution.md

@@ -25,12 +25,40 @@ The template is the better place to validate gem consumption, centralized styles
 
 ## Component Contract
 
-### Pending 0.6.0 retained-letter increment
-
-The source branch prepares a separate 0.6.0 identity for native
-[retained-letter import]({{ '/retained-documents/' | relative_url }}).
-Gem, wheel, base runtime and MCP are authorized as `ready` for final same-source
-candidates. The consumer core selects reviewed integration
+### Published 0.7.0 release
+
+[**0.7.0**](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.7.0)
+adds [live instance identity and session-scoped
+resource control]({{ '/live-runtime/' | relative_url }}). Preparation is explicit,
+launch is pull-never, and startup identity remains distinct from current disk
+metadata. The owner-tested rendering closure selects Diavisuals 0.5.0 and Vega
+0.5.1 with exact artifacts; old 0.4.0 static receipts remain integrity-checked.
+The selected Diavisuals 0.5.0 lacks full live-process identity. The provider's
+[0.6.0 correction](https://github.com/dosquartsdedocs/diavisuals/releases/tag/v0.6.0)
+is published, but remains outside this tested Web combination. Full managed
+coordinator acceptance requires composing-owner validation and a new reviewed
+helper selection.
+
+Gem, wheel, base runtime and MCP were produced from
+`b44818c67eecef159f7aa0f825b0416cd511bc43`; receipt integration and tag target
+`9fc84ac7fd01c78c6fe15fe862beb6a5d1633a9e` bind the same-source candidates.
+The post-release checkout launcher selects
+`sha256:b84cdb404ba7bab5ff0b14fa8a7ee93d7293e829cf32e28ff0dacaa8afff4677`.
+Signed-byte D0 acceptance, the retained-letter relocation/rebuild and all four
+populated Bundler roundtrips passed. Public downloads match the receipt.
+The [delivery report](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/owner-closeout-85.md)
+records exact identities and the remaining gates; the
+[D0 owner contract](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/d0-runtime-identity.md)
+defines the native API and lifecycle scopes.
+
+### Previous 0.6.0 release
+
+[**0.6.0**](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.6.0)
+delivers native [retained-letter import]({{ '/retained-documents/' | relative_url }}).
+Gem, wheel, base runtime and MCP were published from
+`de52db351490e94939aac20c6af264f22a6a1678`; receipt-only integration and tag target
+`ec6dcb28e890d32718aa173934527a7b4213a042` bind their verified bytes.
+The consumer core selects reviewed integration
 `5cf9817489c8dc47cee726bfe42fe3071cd32b85`; the PDF 0.6.0 worker is already
 published, signed and tested at immutable digest
 `sha256:0ba267cb87f53ebaca4e31805fe00610cd61fdf97a8d2c3692f4655700dceaed`.
@@ -38,12 +66,14 @@ The PDF worker changes to include complete retained documents and the same
 integrity checkers used by its controller. Computation, capture and visual
 companions retain their tested 0.4.0 selections.
 
-The checkout's active launcher remains pinned to the published 0.5.1 MCP digest.
-Its receipt and package bytes remain unchanged. Local development images and an
-installed wheel exercise the new import without claiming a public 0.6.0 release
-or changing real consumer sites. The
-[owner acceptance record](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/retained-letter-import.md)
-records the authenticated Carta packet, receiver mapping and relocation proof.
+That release's post-release checkout launcher selected MCP digest
+`sha256:736c4ddd0a543454e3edaeac2e9cfd97a1279ce472923ac54e326c1281b2ba05`.
+Signed candidates, protected CI, strict receipt/ancestry gates, registry promotion
+and Trusted Publishing passed. Anonymous downloads match the receipt. The
+[delivery report](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/owner-closeout-80.md)
+records the installed Carta relocation proof and four-profile populated-cache
+roundtrip against those exact bytes. Existing clients keep their loaded image
+until reconnecting; real consumer adoption remains explicit.
 
 ### Published 0.5.1 release
 
@@ -53,7 +83,7 @@ state. Source `aab5a7b030cd711b40770a3f44ad3a356eab90da` produced the signed
 images and verified gem/wheel. Receipt/tag commit
 `e842c733c8a274279dd5efdc3618e20669f29037` changes only the receipt from that
 first parent. Strict release/publication gates passed before promotion, and
-anonymous registry downloads match the receipt. The checkout launcher now selects
+anonymous registry downloads match the receipt. That release's launcher selected
 `ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692`.
 
 The four-profile populated-cache roundtrip also passed against the actual signed
@@ -91,25 +121,25 @@ candidate, receipt, tag and package evidence.
 
 The BOM is an interoperability contract, not a bundle. The wheel contains its Python control/inspection modules, schema/BOM, clean package-owned scaffolds and a small host Docker launcher, described below. It does not include Ruby theme assets, Docker image layers, the factory's build/worker implementations, TeX, Chromium, computation environments, `diavisuals`, or `vegavisuals`.
 
-The selected public core release is `0.5.1`; earlier distributions remain immutable. Its BOM reuses immutable PDF, compute and web-capture worker digests and selects published `diavisuals v0.4.0` and `vegavisuals v0.4.0` through SHA-256-pinned wheel URLs. Companion references can describe either a provider/release-matching Git reference or a provider/release/version-matching wheel with its content hash. The wheel boundary remains external. The scaffold's Vega revision is the published `68c0b231402ae9485cc34ce530dc5239cb0ec194` commit. `distribution-check` validates structural integrity for normal CI. `distribution-release-check` blocks coordinated publication while any component is `pending` or `unavailable`; reviewed source authorized to produce final same-commit candidates is `ready`, while an already-published component is `released`. Final receipt values remain immutable after publication.
+The selected public core release is `0.7.0`; earlier distributions remain immutable. Its BOM reuses immutable PDF, compute and web-capture worker digests and selects published `diavisuals v0.5.0` and `vegavisuals v0.5.1` through SHA-256-pinned wheel URLs. Companion references can describe either a provider/release-matching Git reference or a provider/release/version-matching wheel with its content hash. The wheel boundary remains external. The scaffold's Vega revision is the published `a448cc50a5f511743a6fcfc213baeb9be80f4a27` commit. `distribution-check` validates structural integrity for normal CI. `distribution-release-check` blocks coordinated publication while any component is `pending` or `unavailable`; reviewed source authorized to produce final same-commit candidates is `ready`, while an already-published component is `released`. Final receipt values remain immutable after publication.
 
 ## Docker-First Hybrid Policy
 
-### 0.5.1 component selection
+### 0.7.0 component selection
 
-The coordinated core identity is **0.5.1**: gem, wheel, base runtime and MCP
+The coordinated core identity is **0.7.0**: gem, wheel, base runtime and MCP
 images were published together. The installed host launcher and runtime-aware
-generated Bundler state are included. The unchanged PDF worker retains its
-published 0.5.0 digest, alongside the 0.4.0 computation/capture workers and visual
-companions. A released PDF can be reused only by full digest; new/pending workers
-still require the coordinated version. The historical 0.5.0 receipt remains
-unchanged. Signed image/package evidence is recorded in the 0.5.1 receipt;
+generated Bundler state are included. The PDF worker uses its reviewed, signed
+0.6.0 digest, alongside the 0.4.0 computation/capture workers and the accepted
+Diavisuals 0.5.0 / Vega 0.5.1 rendering combination. A released PDF can be reused
+only by full digest; new/pending workers still require the coordinated version.
+Earlier receipts remain unchanged. Signed image/package evidence is recorded in the 0.7.0 receipt;
 promotion and anonymous-download checks passed before the post-release launcher
 pin was advanced.
 
 ### Local delivery
 
-GHCR is the canonical delivery channel for normal local use. The released package scaffold selects `ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.5.1`; existing sites can remain on their immutable previous release until deliberately updated. Its `make build`, `make serve` and `make test` targets mount the thin child site and run inside that image. The image contains both the installed Python control plane and the reviewed factory source at `/opt/unaltraweb`, so those targets load the theme as a path gem without downloading PyPI or RubyGems packages.
+GHCR is the canonical delivery channel for normal local use. The released package scaffold selects `ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.7.0`; existing sites can remain on their immutable previous release until deliberately updated. Its `make build`, `make serve` and `make test` targets mount the thin child site and run inside that image. The image contains both the installed Python control plane and the reviewed factory source at `/opt/unaltraweb`, so those targets load the theme as a path gem without downloading PyPI or RubyGems packages.
 
 Factory registration uses a stricter pin. gContExt runs `mcp-build`, which inspects or pulls the full `MCP_RELEASE_IMAGE` digest, and `mcp-stdio` launches that exact image. Checkout builds use local `:dev` names by default through `mcp-image`, `mcp-check` and `mcp-smoke`, so they do not shadow public semver references unless a maintainer explicitly overrides them. The digest is advanced in a separate post-release change after each new receipt exists; candidate source continues to select the last completed release instead of attempting to embed an unknown self-digest.
 
@@ -139,7 +169,7 @@ unaltraweb-mcp-docker serve --project /absolute/consumer
 ```
 
 The installed default selects its package's full MCP release image, currently
-`ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.5.1`. It resolves that selection to the
+`ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.7.0`. It resolves that selection to the
 local immutable image ID before executing. The checkout's `MCP_RELEASE_IMAGE`
 is a separate digest pin advanced only after publication; it is not the installed
 wheel's default. This avoids sending a new package back to an older MCP while
@@ -284,7 +314,7 @@ For that reason:
 
 ## Docker Runtime
 
-Release `0.5.1` publishes the selected base/MCP runtime and packages while pinning the verified PDF worker and reusing unchanged specialized workers. Local maintainers continue to use explicit development names such as `unaltraweb:dev`; generated sites select the reviewed semver MCP image rather than `main` or `latest`.
+Release `0.7.0` publishes the selected base/MCP runtime and packages while pinning the verified PDF worker and reusing unchanged specialized workers. Local maintainers continue to use explicit development names such as `unaltraweb:dev`; generated sites select the reviewed semver MCP image rather than `main` or `latest`.
 
 The base runtime owns Ruby, Jekyll and system dependencies. The MCP image builds on its exact candidate digest and adds the full reviewed factory plus the Python package. Specialized workers remain separate. This keeps each layer focused without adding Chromium, TeX or computation stacks to every site; the coordinated core-image workflow still rebuilds and verifies runtime, MCP and manual PDF candidates together.
 

data/docs/_documentation/en/45-retained-documents.md

@@ -19,7 +19,7 @@ provenance needed to inspect its origin. The importer keeps that complete unit i
 the receiving repository and creates a native page or chapter referencing the PDF.
 The website displays the original; a manual PDF includes all its pages.
 
-This capability belongs to the **0.6.0 development increment**. It requires a
+This capability ships in **0.6.0**. It requires a
 containing Python package and Jekyll core, plus the matching PDF worker for manual
 output. The published 0.5.1 runtime predates it. Changing the global MCP selection
 does not update a site's Gemfile, Makefile or PDF-worker selection.

data/docs/_documentation/en/46-live-runtime.md

@@ -0,0 +1,92 @@
+---
+title: Inspect And Close A Live MCP Session
+description: Startup identity, exact prepared images and session-scoped resource release.
+lang: en
+ref: live_runtime_identity
+profiles:
+- unaltredocs
+documentation_profiles:
+- local-authors
+- core-developers
+section: Core Development
+weight: 635
+permalink: /live-runtime/
+nav_title: Live Runtime
+---
+
+The [published 0.7.0 runtime](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.7.0)
+distinguishes the process serving a connection from
+the installed package, source checkout and rendering workers. Call
+`runtime_identity` or read `web://runtime-identity` through that live MCP
+connection. Both report the same backend instance and startup information.
+
+The observation includes the loaded package version, startup code fingerprint,
+current disk fingerprint, interpreter, PID/start information, workspace mapping
+and selected versus observed image identities. A disk edit is reported as drift;
+it does not upgrade an already-running process. Docker-host and container PID
+namespaces are reported separately. Identity checks read engine/runtime metadata,
+not website prose, private records or arbitrary environment variables.
+
+## Prepare Explicitly, Then Launch
+
+Use `unaltraweb-mcp-docker prepare --image REF` to acquire a selected release.
+Launch, check, smoke and identity observations do not build or pull missing images.
+For a managed launch, supply a full image ID or repository digest, or bind a local
+reference to its independently verified configuration ID:
+
+```bash
+unaltraweb-mcp-docker serve --project /absolute/site \
+  --image "$PREPARED_REFERENCE" --expected-image-id "$EXPECTED_IMAGE_ID" --managed
+```
+
+The expected value is Docker's full `sha256:` configuration ID, not the archive
+checksum or OCI index digest. A missing or mismatched selection is an error.
+Execution uses that inspected ID with `--pull never`; existing aliases are not
+rewritten. Add `--offline` for a controller without networking. The declared
+Docker socket remains available for local inspection and prepared workers.
+
+The normal host launcher mounts the canonical site path and a `/workspace` alias.
+A launcher itself running in a container must supply its explicit daemon-host
+mapping using `--host-project`. Unsupported direct controller mappings require
+inspection rather than guessing a host path from `/workspace`.
+
+## Close One Connection Safely
+
+1. Retain the identity's consumer binding, session ID and exact container ID.
+2. Call `runtime_drain(confirm=true)`. The backend stops admitting new operations.
+3. Close that stdio connection. Bounded active work finishes before its idle
+   session resources are released.
+4. Use the installed `session-status` command to confirm resource termination.
+
+```bash
+unaltraweb-mcp-docker session-status --project /absolute/site \
+  --session-id "$SESSION_ID" --container-id "$CONTAINER_ID"
+```
+
+`connected`, `busy`, `orphaned` and `unknown` do not mean resources are free.
+Only `stopped` with `resources_released=true` establishes observed absence.
+After a crash, `reap-session` with the same retained tuple can recover eligible
+idle leftovers. It preserves live backends, active jobs, other sessions, prepared
+images, volumes and authored files. Disk cleanup remains explicit and separate.
+
+The older `down` command is workspace-wide, and `mcp-down-all` is factory-wide.
+Use them only for those intended scopes, not as a substitute for closing one
+client. The managed stdio profile has one connection per backend; it does not
+claim shared-HTTP backend reattachment semantics.
+
+## Workers And Helpers
+
+Worker references are fixed at startup. Managed rendering requires those exact
+images to be prepared; it refuses a fallback pull/build or a conflicting authored
+computation-image choice. The identity reports resource bounds and image
+observations without running a renderer.
+
+Visual helpers are separate MCP processes. Their versions and immutable package
+selections describe the accepted rendering closure, not their current live
+instances. The composing controller must obtain each helper's own live identity.
+The selected Diavisuals 0.5.0 lacks full live-process identity. Diavisuals 0.6.0
+publishes the provider correction, but is outside unaltraweb 0.7.0's tested helper
+combination. Composing-owner compatibility validation and a new reviewed selection
+are required before accepting that corrected helper in the managed closure.
+Existing 0.4.0 static provider receipts remain subject to full integrity checks
+and do not force regeneration of authored figures during an upgrade.

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

@@ -0,0 +1,209 @@
+# 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).
+
+Delivery: [0.7.0 is published](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.7.0).
+The [signed-byte delivery report](owner-closeout-85.md) supersedes the chronological
+development/candidate state below. It retains the full managed-closure blocker and
+the partial legacy identity gate; publication alone does not close them.
+
+## 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
+
+Release 0.7.0 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. **Selected Diavisuals 0.5.0 lacks the full live-instance identity**.
+[Diavisuals 14](https://github.com/dosquartsdedocs/diavisuals/issues/14#issuecomment-5987114002)
+already records the provider correction in published **0.6.0**; the issue remains
+open for intake. That newer provider is outside unaltraweb 0.7.0's tested helper
+point. The remaining gate is composing-owner compatibility acceptance and a new
+reviewed selection of the corrected helper, followed by independent live
+observations. It is not an unpublished provider implementation. Rendering
+compatibility alone does not make the 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.