unaltraweb 0.5.1 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: be599804b31390cca31133227e0e15f4ba623339a1072a441c74960b79c039fa
-  data.tar.gz: d70f999b0d814f6a579dbb06534c611034792a1cd29972b3015ecce5e21522a4
+  metadata.gz: 2ed24da568933de15be12350ea7b867a6aa7e14abac71ec303755f5b808e1837
+  data.tar.gz: a4176d255c14de252144d7669db6479bc43ee033342332cd596870eea1ddf71b
 SHA512:
-  metadata.gz: cb11d05e8660d167d311c7a9e1d03f895918d02c754e7189f52b25f1403f0056731aa94f77116b11cf30049c9d54b1ca6ffcae312c08d3127f942c756a1ed222
-  data.tar.gz: c7c798ce0e589fbd2fdaddfa9c4d632afd043ccfca6ecd65c780dfcae33932f6314da270968c665dfcdbac080f48e67022c66344b45961c8b87c1cfe0704ff9a
+  metadata.gz: 768943c9b012a7e165ab9136d364783203c35caaaae62c2715f95361107f63377dbac30e45252ebeff78b0707d71dd14eb0481cecca18f52b15688c82f4c8c10
+  data.tar.gz: 49edeb75312f6d45e53db50a55a65f25ddb81f7ad8cc8438c9568ada3c9d699c9c00f0a329ea9b8cc2fb5812b5e48acd254e0e967b659d16650a0ea8612dad16

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.5.1
-MCP_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.5.1
-MCP_RELEASE_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:36d17edbade77edb40a687f6a744203c6329acb33fbc2eb255e88d9ff1a42c98
+MCP_RUNTIME_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.7.0
+MCP_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.7.0
+MCP_RELEASE_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:736c4ddd0a543454e3edaeac2e9cfd97a1279ce472923ac54e326c1281b2ba05
 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.5.1
-MANUAL_PDF_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:9e0b3a45753c170b795e9a9d6df61580085c113436beac5bf6c8de69b6562097
+DOCKER_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb:0.7.0
+MANUAL_PDF_IMAGE ?= ghcr.io/dosquartsdedocs/unaltraweb-manual-pdf@sha256:0ba267cb87f53ebaca4e31805fe00610cd61fdf97a8d2c3692f4655700dceaed
 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; \
@@ -375,20 +376,21 @@ manual-pdf-image: ## Ensure the selected versioned Pandoc/XeLaTeX image is prese
 	@docker image inspect "$(MANUAL_PDF_IMAGE)" >/dev/null 2>&1 || docker pull "$(MANUAL_PDF_IMAGE)"
 
 manual-pdf-image-dev: ## Build the explicitly named maintainer PDF development image
-	docker build -f scripts/manual/Dockerfile -t "$(MANUAL_PDF_DEV_IMAGE)" scripts/manual
+	docker build -f scripts/manual/Dockerfile -t "$(MANUAL_PDF_DEV_IMAGE)" .
 
 define run_manual_pdf_worker
 	@set -e; set --; cidfile=""; \
 	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/_plugins/retained_documents.rb

@@ -0,0 +1,62 @@
+# frozen_string_literal: true
+
+require "cgi"
+require "json"
+require "open3"
+require "timeout"
+
+module UnaltrawebRetainedDocuments
+  def self.verify(site, output = nil)
+    return { "imports" => [] } unless File.exist?(File.join(site.source, ".unaltraweb", "artifacts"))
+
+    source = File.expand_path("../src", __dir__)
+    command = ["python3", "-m", "unaltraweb_mcp.artifact_imports", "--project", File.expand_path(site.source)]
+    command += ["--output-folder", output] if output
+    stdout, stderr, status = Timeout.timeout(120) { Open3.capture3({ "PYTHONPATH" => source }, *command) }
+    result = JSON.parse(stdout)
+    raise Jekyll::Errors::FatalException, "Retained document check failed: #{result['error'] || stderr}" unless status.success? && result["ok"] == true
+
+    result
+  end
+
+  class Generator < Jekyll::Generator
+    safe true
+    priority :highest
+
+    def generate(site)
+      site.config["unaltraweb_retained_documents"] = UnaltrawebRetainedDocuments.verify(site)["imports"].to_h { |item| [item["id"], item] }
+    end
+  end
+
+  class DocumentTag < Liquid::Tag
+    def initialize(name, markup, tokens)
+      super
+      @id = markup.strip
+      raise ArgumentError, "retained_document requires one import ID" unless @id.match?(/\A[a-z][a-z0-9-]{0,63}\z/)
+    end
+
+    def render(context)
+      site = context.registers[:site]
+      item = (site.config["unaltraweb_retained_documents"] || {})[@id]
+      raise Jekyll::Errors::FatalException, "Unverified retained document #{@id}" unless item
+
+      path = site.config["baseurl"].to_s.sub(%r{/\z}, "") + "/" + item.fetch("pdf")
+      url = CGI.escapeHTML(path)
+      page = context["page"]
+      title = CGI.escapeHTML(((page && page["title"]) || @id).to_s)
+      %(<figure class="retained-document"><object data-retained-document="#{@id}" data="#{url}" type="application/pdf" aria-label="#{title}" style="width:100%;height:70vh"><a href="#{url}">#{title}</a></object><figcaption><a href="#{url}">#{title} (PDF)</a></figcaption></figure>)
+    end
+  end
+end
+
+Liquid::Template.register_tag("retained_document", UnaltrawebRetainedDocuments::DocumentTag)
+
+Jekyll::Hooks.register :site, :post_write do |site|
+  source = File.expand_path(site.source)
+  destination = File.expand_path(site.dest)
+  if destination.start_with?(source + "/")
+    UnaltrawebRetainedDocuments.verify(site, destination.delete_prefix(source + "/"))
+  elsif !(site.config["unaltraweb_retained_documents"] || {}).empty?
+    raise Jekyll::Errors::FatalException, "Retained documents require a project-confined site destination"
+  end
+end

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

@@ -25,9 +25,63 @@ The template is the better place to validate gem consumption, centralized styles
 
 ## Component Contract
 
-### Published 0.5.0 release
-
-The coordinated core release is [**0.5.0**](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.5.0). It groups the integrated editorial
+### 0.7.0 D0 runtime increment
+
+The next containing runtime 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.
+Diavisuals' separate live-process identity correction still gates the full
+managed coordinator closure. Publication and activation evidence belong to the
+[D0 owner record](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/d0-runtime-identity.md).
+
+### Published 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`.
+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 post-release checkout launcher selects published 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
+
+[**0.5.1**](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.5.1)
+delivers the installed Docker launcher and runtime-specific generated Bundler
+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. That release's launcher selected
+`ghcr.io/dosquartsdedocs/unaltraweb-mcp@sha256:908b4ce54c7bdf355e14ed55b31ed4b9baae319e211af90004a680d1d1cb8692`.
+
+The four-profile populated-cache roundtrip also passed against the actual signed
+candidate. The selected PDF stays at its published 0.5.0 digest, and computation,
+capture and visual companions retain 0.4.0. See the
+[delivery report](https://github.com/dosquartsdedocs/unaltraweb/blob/main/docs/agents/owner-closeout-76.md)
+and [issue 76](https://github.com/dosquartsdedocs/unaltraweb/issues/76).
+Strict release validation applies to the receipt/tag revision; subsequent
+post-release launcher changes are ordinary source revisions, not new receipts.
+
+### Previous 0.5.0 release
+
+The previous coordinated core release is [**0.5.0**](https://github.com/dosquartsdedocs/unaltraweb/releases/tag/v0.5.0). It groups the integrated editorial
 review, guided scaffold updates, caption-credit/image behavior and published
 Diavisuals/Vegavisuals 0.4.0 acceptance. Source-bound image/package workflows,
 tag promotion and both Trusted Publishing jobs passed. Anonymous package downloads
@@ -42,7 +96,7 @@ at source `d857f8c9f5fea90cf450c0b30b4e77a37b541275` and is selected by digest
 `sha256:9e0b3a45753c170b795e9a9d6df61580085c113436beac5bf6c8de69b6562097` in
 both the factory and the consumer tuple. It is already published and tested, so
 final candidate receipts cover the remaining ready package/core components.
-The post-release factory launcher selects the MCP digest recorded in receipt
+The 0.5.0 post-release factory launcher selected the MCP digest recorded in receipt
 `3fa855378dcc61dc7b84b8b03812698042e02fed`:
 `sha256:36d17edbade77edb40a687f6a744203c6329acb33fbc2eb255e88d9ff1a42c98`.
 See [issue 69](https://github.com/dosquartsdedocs/unaltraweb/issues/69) for the
@@ -50,27 +104,27 @@ candidate, receipt, tag and package evidence.
 
 `src/unaltraweb_mcp/component-contract.json` is the canonical versioned bill of materials. Its `consumer_integration` object is the sole source for the reviewed core Git revision, reusable deploy workflow, manual PDF image digest, and Vega renderer revision. Scaffold templates render that tuple atomically into consumer `Gemfile`, `Gemfile.lock`, and deploy workflow files. `component-contract.schema.json` defines schema version 1. Runtime loading and `scripts/validate_distribution.py` validate the complete document against that schema, then enforce semantic parity between versions, release tags, repositories, references, wheel contents, CLI availability, and consumer integration pins.
 
-The BOM is an interoperability contract, not a bundle. The wheel contains its Python control/inspection modules, schema/BOM, and clean package-owned scaffolds. Next-release source also packages a small host Docker launcher, described below. Neither includes Ruby theme assets, Docker image layers, the factory's build/worker implementations, TeX, Chromium, computation environments, `diavisuals`, or `vegavisuals`.
+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.0`; earlier distributions remain immutable. Its BOM reuses immutable 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.6.0`; 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.
 
 ## Docker-First Hybrid Policy
 
-### 0.5.1 preparation
+### 0.6.0 component selection
 
-The next coordinated core identity is **0.5.1**: gem, wheel, base runtime and MCP
-image candidates change 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
+The coordinated core identity is **0.6.0**: gem, wheel, base runtime and MCP
+images were published together. The installed host launcher and runtime-aware
+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 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. Final signed image/package receipts and promotion are later gates;
-the launcher continues selecting the last published MCP digest until its normal
-post-release update.
+unchanged. Signed image/package evidence is recorded in the 0.6.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.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.
+GHCR is the canonical delivery channel for normal local use. The released package scaffold selects `ghcr.io/dosquartsdedocs/unaltraweb-mcp:0.6.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.
 
@@ -86,7 +140,7 @@ These remain real package boundaries: the MCP image installs the Python package
 
 ### Installed Docker launcher
 
-0.5.1 source adds **`unaltraweb-mcp-docker`** and a complete host launcher
+0.5.1 ships **`unaltraweb-mcp-docker`** and a complete host launcher
 under the installation prefix's `share/unaltraweb-launcher/`. The published 0.5.0
 wheel predates this addition; its receipt and bytes remain unchanged. An installed
 wheel containing the launcher can use the already-published full GHCR runtime
@@ -100,7 +154,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.6.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
@@ -132,7 +186,7 @@ the host, register a client, update a consumer scaffold, or change an active MCP
 The site Makefile's `MCP_IMAGE`, native Gem/core revision, PDF worker, global MCP
 registration and companion selections are separate parts of an effective tuple.
 TIG/TIGIT retain build defaults 0.4.0; Geodisseny retains 0.5.0. A global MCP
-selection of 0.5.0 does not rewrite those defaults. Tests use synthetic sites,
+selection does not rewrite those defaults. Tests use synthetic sites,
 image-specific test resources and dynamically allocated loopback preview ports.
 
 Compatibility evidence is a set of tested tuples, not a continuous version range.
@@ -245,7 +299,7 @@ For that reason:
 
 ## Docker Runtime
 
-Release `0.5.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`.
+Release `0.6.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

@@ -0,0 +1,138 @@
+---
+title: Import A Retained Letter
+description: Verify and retain a Carta letter bundle, display its PDF on the web and include it in a manual.
+lang: en
+ref: retained_documents
+profiles:
+- unaltredocs
+documentation_profiles:
+- local-authors
+- core-developers
+section: Build A Site
+weight: 240
+permalink: /retained-documents/
+nav_title: Retained Documents
+---
+
+A retained letter combines its original PDF with the source, rendering inputs and
+provenance needed to inspect its origin. The importer keeps that complete unit in
+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 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.
+
+Native gem builds need Python with `PyYAML>=6,<7`, `pypdf>=6,<7` and
+`markdown-it-py>=3,<5`. The containing MCP/PDF images provide these dependencies;
+the containing reusable deployment workflow installs the PDF/text parsers when
+retained imports are present.
+
+## Supported Input
+
+The receiving profile accepts leaf `letter-pdf-v1` bundles from **Carta
+0.3.0rc1**, using the existing artifact handoff v1 envelope. Verification covers
+the supplied sender SHA-256, complete file inventory, retained render recipe,
+templates, source references, drawable resources and renderer identity. PDF
+inspection is bounded and rejects encrypted files, embedded or external files,
+JavaScript and unsupported actions. Internal destinations and textual HTTP,
+HTTPS and email links are supported.
+
+Renderable metadata is checked independently of the retained Pandoc AST. A
+resealed bundle with an unretained local link in a subject or author field is
+rejected even when its older parsing evidence does not mention that link.
+
+Limits are 64 MiB for the payload unit, 32 MiB for the PDF and 1–64 pages. The
+supported source subset excludes body images, raw markup, TeX, math and citations;
+attachments remain text labels. Composite bundles, edited PDF variants and
+Diapora composition require separate receiving profiles.
+
+Obtain the bundle's expected SHA-256 through the sender's trusted handoff. A hash
+computed only from an unknown local manifest establishes consistency, not its
+origin. Importing never executes the retained recipe or contacts the producer.
+
+## Import Into A Consumer
+
+Start with an initialized consumer Git repository. Place the complete incoming
+bundle under a workspace-relative directory such as `tmp/incoming/letter/`.
+The recovery area under `tmp/` must be ignored and untracked; durable destinations
+must be eligible for version control.
+
+Review a plan using the installed CLI. Here `BUNDLE_SHA` is the sender's verified
+manifest digest:
+
+```bash
+unaltraweb-mcp --project /absolute/consumer mcp import-artifact-bundle \
+  --path tmp/incoming/letter/bundle.json --sha256 "$BUNDLE_SHA" \
+  --import-id correspondence --content-path _chapters/en/correspondence.md \
+  --title "Retained correspondence"
+```
+
+To apply the reviewed request, repeat it with `--apply --confirm-import`.
+The MCP equivalent is `import_artifact_bundle` with `dry_run=false` and
+`confirm_import=true`; its default is a read-only plan.
+
+Choose a new Markdown destination under `_pages/`, or `_chapters/` for a manual,
+or `_documentation/` for a documentation site. An executable source owning the
+same Markdown basename blocks creation. The generated document starts as a draft
+in the consumer's default language, with a literal local permalink.
+
+The resulting paths are:
+
+| Path | Purpose |
+| --- | --- |
+| `.unaltraweb/artifacts/correspondence/bundle/` | Complete, unchanged incoming seal, outside the web output |
+| `.unaltraweb/artifacts/correspondence/integration.json` | Standard v1 integration record and byte-preserving PDF mapping |
+| `.unaltraweb/artifacts/correspondence/binding.json` | Native content path and integration-record digest |
+| `assets/documents/correspondence.pdf` | Public PDF, identical to the retained original |
+| `_chapters/en/correspondence.md` | Native chapter with the retained-document component |
+
+Version the complete durable unit together. The incoming directory and ignored
+recovery journal are not runtime dependencies. The retained archive is excluded
+from website output, but remains ordinary repository content.
+
+## Edit And Render The Native Document
+
+Add explanatory prose to the generated page or chapter while preserving its
+literal permalink and component:
+
+{% raw %}
+```liquid
+{% retained_document correspondence %}
+```
+{% endraw %}
+
+On the web, the component renders a PDF object with a labelled download link.
+The build checks the bound page's exact local PDF URL and the emitted PDF bytes.
+Exposing the retained archive in the website is an error. In a manual, the PDF
+builder includes every original page and fingerprints the entire retained unit
+and its checker implementation. A controller/worker mismatch therefore fails
+freshness verification rather than silently accepting an older checker.
+
+Run `artifact_import_check` or the CLI equivalent before building:
+
+```bash
+unaltraweb-mcp --project /absolute/consumer mcp artifact-import-check
+unaltraweb-mcp --project /absolute/consumer mcp artifact-import-check --output-folder _site
+```
+
+`site_check` and `site_doctor` include the native integrity check. For a local
+manual review, use `manual_pdf_preview_prepare`, then `build_site` and
+`preview_start`. Review the web page and composed PDF, then clean only the
+receipt-owned preview copies through `manual_pdf_preview_clean`.
+
+## Preservation And Recovery
+
+An identical reimport preserves authored prose. A changed mapped PDF, conflicting
+destination, unsafe path or modified seal blocks the operation; existing files
+are never overwritten. After an interrupted import, unchanged partial files may
+be adopted by an explicit retry of the same request. Differing partial files
+require inspection. The operation retains its prepared tree and journal under
+`tmp/unaltraweb-artifact-imports/` and performs no destructive rollback.
+
+The native check verifies references and content after the incoming producer copy
+has been removed or the receiving repository has moved. It also detects missing
+content, incomplete retention and altered mappings. The generic v1 verifier can
+independently inspect `integration.json`; it does not replace the native source
+and rendered-output checks.

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

@@ -0,0 +1,89 @@
+---
+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 0.7.0 runtime increment 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 still requires its separately tracked D0 identity
+correction before the entire coordinator closure can be marked managed-ready.
+Existing 0.4.0 static provider receipts remain subject to full integrity checks
+and do not force regeneration of authored figures during an upgrade.