fix: canonical component runtime integrity

[adrianwebb]

Outcome

Repair canonical component release integrity under treeseed-ai/deployment#666.

Work authority

• Work item / Issue: Canonicalize component runtime before computing its release digest #103
• Proposal / decision: Approved Identity/shared PostgreSQL plan; pre-cutover integrity recovery.
• Assignment / checkpoint: Canonical runtime producer and preflight correction.
• Actor: adrianwebb
• Human authority: adrianwebb
• Agent / capacity provider: Codex local development session
• Exact base ref: 585e31f
• Exact head ref: cc0d8fc

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Reject malformed metadata before writers stop; publish corrected immutable owner artifacts through normal staging gates. Never edit prior release assets or relax integrity.

Changes and commits

Parse the runtime through SDK packageRuntimeSchema before hashing, preventing defaulted fields from invalidating the emitted digest. No application behavior or image build inputs changed.
Commit cc0d8fc.

Verification

Full release:verify passes: independent build and 180 tests across 35 files. Producer subprocess test hashes emitted bytes and verifies schema reparse.
Required Actions pending this PR. No live database transfer accepted; automatic rollback restored generation 19. API development targets restored and AI awake.

Risk and rollback

Bounded release metadata/preflight change. Previous component artifacts remain immutable. Replace selection only via exact Platform composition after Actions. Revert before publication if needed; retain known-good host configuration. No purge/bootstrap reinstall or training workload.

Completion summary

Implementation and local verification complete; Actions, staging merge, replacement metadata release and managed acceptance remain. Issue stays open through acceptance.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.