The user requested consolidation of host, shared, root/user profile, engine and project instructions.
The shared source is ProfileBackups/ax_julian revision 1a5708d1b4bd791c8891a81503f1e071b4b03b19, integrated through PR #18. Root and user profile links select the same shared AGENTS file. The host file owns server operations and scoped administrator exceptions; project files own product and technical rules; engine templates own validated workflow stages and output protocols. Existing named Lease coordination guidance was preserved.
Verified Kubernetes target before mutation: context kubernetes-admin@kubernetes, API https://192.168.1.9:6443. Published immutable ConfigMap autocoder-canonical-instructions-fe82091a841aae4a1f4068d06c94e5c8a5fb81b3039f920bb053bf782794e04c in namespaces autocoder-engine and autocoder-test using the repository publisher and the clean committed shared source. The manifest has 44 files and aggregate digest fe82091a841aae4a1f4068d06c94e5c8a5fb81b3039f920bb053bf782794e04c.
These publications create unused immutable objects; they do not select them in running deployments. Engine PR #6788 prepares the matching repository-managed selection for the configured development/test route. Production promotion is separate. Existing immutable ConfigMaps and pinned running tasks were preserved; no credentials, identities, RBAC or workload environment were changed by publication. Rollback is selection of the previously retained bundle through the repository-managed deployment route, not deletion of history or objects.
Instruction-file edits do not prove changed agent behavior. Existing session context can lag behind current linked files. The engine still assigns token ceilings in code (resource_budget.rs and the live-acceptance task); that implementation mismatch is recorded in its canonical-bundle procedure and requires a separate repair preserving cost/capacity safeguards.
TheWell backend PR #6657 and frontend PR #6658 target dev; Bodylog PR #1288 targets dev. Their instruction changes remove duplicate human collaboration gates while preserving product consent and reproduction-path verification. Development delivery and live outcome evidence must be reported separately from merged instructions.
Published the latest reviewed source 2c90e665bb17efbdd732018b31ca0793454ab97d as immutable ConfigMap autocoder-canonical-instructions-8a7099fa2c9ba56acd3e12332c62ebb7299c2aafcf02b81ca9e5fcce3dc72a12 in autocoder-engine and autocoder-test, after rechecking the same cluster context/API. The bundle contains 44 tracked files and the approved default-high and accumulated-runtime six-hour review / 48-hour validation SOP. PR #6788 selects this revision. Publication still does not establish deployment or runtime-policy enforcement; previous immutable objects remain retained.
Engine PR #6792 merged into development as 13b00b39d0085f580b25fd9468b3910e963fcce0 after exact-head branch run4082 succeeded. PR #6788 merged as 84818cea8f85e0dcacd525f0c64e510aec17b7e7 after exact-head branch run4083 succeeded. The integrated candidate run4087 owns full native/database validation and subsequent configured delivery; branch CI alone is not that evidence.
Prepared and verified immutable production environment/root ConfigMaps from exact integrated source84818cea. Configuration contract digest 135c1e6a7a389f1aa7eaa39720644ba26ac7fe5fa807f850eb3b865f42e007e1 selects environment autocoder-env-7bc29c35a9e817b5a712c5d30c6c532d49a1da386df3043dba7e1d7fbd16a1c9, retained root autocoder-root-9f5f5590186a8c8aa4caa39d37aada9dd9acb8af587144f8a8a0e807cae9797f, and canonical8a7099fa. Set only the guarded deployment metadata preparation receipt; workload template and generation2606 stayed unchanged. Repository source root retains background automation, implementation workers and operator-chat workers false; current stops stay effective. Preparation itself does not deploy. Existing reviewed automatic main delivery remains selected in the provider variable; candidate validation and exact artifacts still govern actual promotion.
Preparation verification correction: the guarded metadata annotation update incremented Deployment generation from2606 to2607. Comparison verified the pod template, selected images and deployed candidate remained identical; no rollout was caused by preparation. The earlier statement that generation stayed2606 was incorrect. The preparation receipt now matches 135c1e6a7a389f1aa7eaa39720644ba26ac7fe5fa807f850eb3b865f42e007e1.
Candidate db857f5cb9e1e6df014ca9546944bc8022d4f6c2-4097-1 passed integrated candidate validation and promotion run 4101. Live deployment has one ready replica, source db857f5cb9e1e6df014ca9546944bc8022d4f6c2, backend sha256:a7362181c8ac2316699935c2d6a0ae2deb4c6054c3c9262f9f6897e53aeca489 and frontend receipt sha256:48d7dd954c9fa6386d8f41db4c4694711a090b6f776c563ad4bb7fb188eac2d3. The pod selects immutable canonical instruction digest 8a7099fa2c9ba56acd3e12332c62ebb7299c2aafcf02b81ca9e5fcce3dc72a12 and the prepared configuration receipt 135c1e6a7a389f1aa7eaa39720644ba26ac7fe5fa807f850eb3b865f42e007e1. This proves engine selection of the consolidated guidance and high default source; separate worker-image publication and accumulated-runtime implementation remain pending. Original candidate 4087 failed its obsolete formatting fixture and skipped delivery; commit 03315d0a corrected the existing assertion in subsequently reviewed PR 6800 before this successful candidate. No failed candidate was deployed.
The existing worker-publication workflow run 4111 completed successfully for main revision 09daea7cd2278e5a95b5da8f7ec156f4d75e2a6b, whose source tree is deployed candidate c9b808013cac1fbfe97a9a13fa9c2f6a9d4ff93d. Read-only live verification confirms selected worker image sha256:053112704014e9d1615bbee847c71feab7630de1a17cf5f88865120b4f841085, production backend sha256:e58b280b23476d07242aa1dd55985a2fc0a7a67484eeb8c207d2fca8a334f849, frontend sha256:8cddcee5e9052f4c6d310dc376ffb7991f2be2345bc078f88785fa1b8f944589 and one ready replica. Canonical instruction digest and prepared contract remain 8a7099fa2c9ba56acd3e12332c62ebb7299c2aafcf02b81ca9e5fcce3dc72a12 / 135c1e6a7a389f1aa7eaa39720644ba26ac7fe5fa807f850eb3b865f42e007e1.
Both local user/root Codex configuration files select model_reasoning_effort = "high". The selected immutable environment ConfigMap confirms high engine effort, background automation false, implementation workers false and requirements automation false. Operator-chat workers remain true as already configured; the earlier repository-root false statement was not a statement of the effective environment. This verification does not change any stop.
The six/48-hour ledger implementation in PR 6804 is not merged or deployed. Exact branch run 4117 rejected compilation errors before integration; those errors are being corrected and isolated fixtures remain required before rollout. Publishing the consolidated SOP and default-high worker does not establish runtime enforcement.