3.1 KiB
Code Development Report V5
V5 succeeds V4. Fixed product source and input-artifact hashes are unchanged; the following V5 implementation work changes only the release-control-plane package and must be reflected by rebuilt package digests.
Implemented:
- six V5-isolated systemd service definitions and V5 tmpfiles coverage;
- regression tests for exact runtime/state paths and effective unit/drop-in evidence;
- task Manifest schema v5 plus
AIOS_RUNTIME_LAYOUT_V1Release Root cross-binding; - safe tar extraction that rejects traversal, special files, undeclared absolute links, and escaping link targets;
- binding of the actual
--release-artifactarchive to the generated extracted Artifact file manifest; - writable-path overlap rejection for the fixed read-only OpenClaw dependency;
- external dependency package metadata/tree validation and symlink policy;
- mandatory candidate/effective production-unit digest equality and explicit
no-drop-in verification, including
ProtectSystem=strict,NoNewPrivileges=true, systemd list-reset handling, and read-only bindings; - V5-scoped systemd paths in the manifest and validation contract;
- CLI support for
--release-artifact, mandatory effective-unit/no-drop-in inputs,artifact-extract, andartifact-file-manifest-generate; - exact fixed OpenClaw dependency identity, safe archive snapshot parsing, bounded member counts, and complete special-member pre-scan;
- strict publisher-unlock receipt/evidence/OID binding and path-safe quarantine validation;
- cache-gate integration and tamper coverage;
- durable full Anchor PASS/FAIL evidence envelopes with digest and chain validation;
- root-broker enforcement of an existing Anchor reservation and exact campaign state, with Anchor-resolved predecessors delivered through a sealed memfd;
- caller-predecessor rejection and thin AF_UNIX broker passthrough wrappers;
- Writer-role hosting of the loopback metadata Writer and its isolated credentials;
- live pre-switch rollback artifact/worktree/production-health verification and verified restoration reporting;
- a content-addressed fresh-acceptance derivation contract that binds templates and the dynamic JSON pointer without predicting a future evidence digest.
Validation totals and package/component hashes are generated by the final closure run and recorded in its machine-readable reports. This development report does not predict those values. Package rebuild, digest generation, human Phase B approval, live deployment, and fresh production acceptance remain separate release gates.
No AIOS/Gitea ref, system service, account, token, ACL, production Artifact, tag, registry, or baseline was changed during development.
Digest status
Stale V4 component digest claims have been removed. Every V5 package/component digest is closure-generated and is recorded only after the final rebuild. Fixed product source and input-artifact hashes remain unchanged and are not replaced by future V5 package digests.
No production action is authorized by this report. The human Phase B gate is mandatory, and no production effect may occur before exact approval is present, current and independently observed.