Isolate tenant readback cache and prepare verified runtime release

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade

docs/conformance/2026-10-11-layer-v08-migration.md

@@ -0,0 +1,31 @@
+---
+type: conformance-record
+derived: true
+derived_from: net-kingdom/canon/standards/security-layer-model_v0.8.md
+derived_source_sha256: "3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b"
+updated: "2026-10-11"
+---
+
+# user-engine accepted v0.8 checker migration
+
+This owner applies GH-WP-0004-T11's post-flip migration to the confirmed
+accepted NetKingdom v0.8 cut, immutable accepted-1 artifact SHA256
+3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b.
+The checker names that artifact and its local scope in every run. INTENT
+frontmatter remains authoritative and the sidecar remains derived; a
+contradiction is a finding, never hidden by choosing one form. No declaration
+acquires a standard version.
+
+The pin detector follows OpsWarden's A12 r3 reference semantics: standard and
+companion identity values (including nested lists), version-bearing paths and
+standard/companion version keys are pins; unrelated intent/schema/spec versions
+and bare prose provenance are not. Existing local Tooling/contact and capability
+detectors remain in place. Historical version strings in negative fixtures are
+retained. This source migration grants no native capability or runtime authority.
+
+Validation includes the existing local declaration/contact suite and the same
+12-case pin/provenance corpus across all four assigned owners, with exact
+accepted-artifact and scope assertions. The local test counts and staged source
+digests are retained in the coordinating Custodian evidence receipt. Standalone
+checker runs continue to inspect only this repository; no estate-wide compliance
+claim or novel declaration is produced.

docs/evidence/2026-10-11-runtime-base-refresh.md

@@ -0,0 +1,31 @@
+# Runtime base refresh — 2026-10-11
+
+The exact source-bound application readback candidate failed its independent
+scan with 88 HIGH and three CRITICAL OS findings. Preserve that scan and OCI
+index bea54ccf in the managed runtime release record. This remediation changes
+only the Containerfile's immutable official Python base index from d764629c
+to a6e34c59. It preserves Python 3.12, updates patch 3.12.13 to 3.12.15, and
+uses current Docker Official Image source commit
+2a3b794c223ab067d122719541cdd54a068732a5 (3.12/slim-trixie). The native new
+base contains perl-base 5.40.1-6+deb13u1, libc6 deb13u4 and OpenSSL 3.5.7.
+
+Detailed registry/source, exact context, installed file hashes, dependency
+snapshot and unfiltered scan are in
+`rapp-user-engine/docs/evidence/2026-10-11-readback-base-refresh/`. All 47
+copied application inputs and all 45 installed package files match the prior
+source. Resolved Python package versions are unchanged. All 20 image readback
+tests pass; all 323 source tests pass with 8 optional skips and accepted-v0.8
+layer conformance passes. Native consumer acceptance remains USER-WP-0026-T03.
+
+The refreshed scan has zero CRITICAL and 44 HIGH findings across 8 distinct
+CVEs, all without a published fixed version in the fresh recorded database.
+These findings remain visible; no severity reduction, ignore-unfixed option
+or suppression was applied. This does not claim a vulnerability-free or
+approved release. Clean accepted source commit, publication and independent
+release review remain required, alongside exact scoped live rollout permission.
+
+CI source preparation also replaces short-revision archive lookup with the
+validated full 40-hex GITHUB_SHA and labels the built image with that exact
+revision. Both workflow shell blocks pass bash syntax checks. This workflow
+change is outside the local image runtime context and was not published or
+executed; owner CI must produce a new publication receipt from a clean commit.