The administrator-owned source /home/ax_julian/ProfileBackups/ax_julian was a clean Git tree at revision 83a7a154eed1ecab03b9cfca58eacdf1f01dd2ae. The repository-managed publisher produced a 24-file immutable bundle with aggregate SHA-256 a7c83379da31b71f820bbad7187bdeae3666789e7e4288022e1ee1e3913e2430 and ConfigMap name autocoder-canonical-instructions-a7c83379da31b71f820bbad7187bdeae3666789e7e4288022e1ee1e3913e2430.
The ConfigMap was applied to autocoder-engine and autocoder-test after verifying the kubernetes-admin@kubernetes context. In both namespaces, the observed immutable flag, name, source-revision/digest annotations, complete manifest JSON, and compressed binary archive matched the publisher output byte-for-byte. The extracted AGENTS.md SHA-256 matched the source file: 476a4256344749848ca21b6a3886288f08f9a31d2ce73d370da799a897ed62fb.
This operation created ConfigMaps only; no Deployment, pod, secret, ingress, database, or worker-claim configuration was changed. The prior abbreviated ConfigMap remains for the old runtime until the bundle-mount and admission cutover is separately validated. Temporary publisher JSON files were removed after verification. Next evidence: confirm the exact new bundle is mounted read-only in Engine and worker pods, that startup/claim admission rejects absent or mismatched bytes, and that a task persists this exact digest. Do not treat publication alone as worker parity.