You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor: cut os-stack.bst over to the Flatcar base and delete displaced FSDK elements #131
Kept unchanged - these are OS policy, not upstream software: os-release-flatcar.bst (now truthful rather than a compatibility fiction), os-sysupdate.bst, os-k0s-sysupdate.bst, os-sysupdate-keys.bst, os-networkd.bst, os-k0s-first-boot.bst, os-creds-prov.bst, os-kured-hook.bst, os-justfile.bst, os-issue.bst, os-image-info.bst, os-countme.bst, os-sshd-preset.bst, os-sshd-config.bst.
Also remove the os-base option once the Flatcar path is the only path.
Acceptance:
No FSDK userspace component remains in the OS payload graph; the installer keeps its FSDK stack.
just validate, pytest tests/unit, and the phase 4 boot gates all pass.
Affected skills updated; no orphaned references to the deleted elements.
Closing: superseded by the version-parity reframe in docs/superpowers/specs/2026-09-13-flatcar-base-migration-design.md (PR #123).
There is no cutover to a Flatcar base, because the base stays FSDK 26.08. The displaced-elements table in this ticket assumed replacing FSDK userspace with Flatcar's tree; that is now an explicitly rejected alternative.
The replacement work is phase 6, Substitution: working down the parity matrix, replace each imported reference binary with an FSDK-built component at Flatcar's version, re-running the boot proof after each swap. That needs the parity matrix first (#140), so it will be filed per-component rather than as one sweep.
Activity
castrojo commentedon Sep 13, 2026
Closing: superseded by the version-parity reframe in
docs/superpowers/specs/2026-09-13-flatcar-base-migration-design.md (PR #123).There is no cutover to a Flatcar base, because the base stays FSDK 26.08. The displaced-elements table in this ticket assumed replacing FSDK userspace with Flatcar's tree; that is now an explicitly rejected alternative.
The replacement work is phase 6, Substitution: working down the parity matrix, replace each imported reference binary with an FSDK-built component at Flatcar's version, re-running the boot proof after each swap. That needs the parity matrix first (#140), so it will be filed per-component rather than as one sweep.
refactor: switch OS payload to Flatcar base, drop displaced FSDK comp…