seed: versioned packages with a holistic integration spec #127
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!127
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "seed/packages-integration-spec"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seeds become published, versioned artifacts. manifest v2 = holistic integration spec: per-bundle sha256 + the platform versions the seed integrates (read from the squashed gitops bundle itself — spec cannot drift from tree) + toolchain floor + the gate it answers to.
PUBLISH=1→ generic packageplat/seed/<version>(tarball + standalone manifest);SEED=latest|r<serial>resolves in up/germinate; germinate verifies every bundle hash (tamper-evident, proven: corrupted bundle refuses). Reseed publishes only post-verification. genesis/ blob = air-gap fallback; v1 seeds untouched. Live-tested: build ✓ integrity+tamper ✓ publish ✓ anonymous resolve+fetch ✓ (test versions deleted from the registry).🤖 Generated with Claude Code
Gate triage: both failures here (and #126's) are NOT this PR — main's nightly went red 08-14 04:25. Root: reseed r187 pulled the fleet-edge gitops into the seed and
fork_regen_secretsdid not coverplat-auth-secrets.yaml, so every fork fails Flux decryption on a parent-sealed secret. This branch now carries the fix (placeholder seal + PAT user:token form + post-handoff plat-auth OAuth registration, all no-ops on pre-edge seeds). Re-firing the gate.Gate attempt 5 red. The branch now dumps cluster state on any failing exit — autopsy is in the newest ~/ci-gate-logs/run*-up.log on the host. (Prometheus OOM spiral fixed in gitops ~21:30; if this run overlapped the restart, one re-fire is warranted.)