Repository navigation
Closed
Labels
area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.priority: P2Medium; normal planned work.Medium; normal planned work.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
Description
Parent
Rewrite the spec and the compiler in place, release 1.0.0, and hand over every Project
What to build
The model breaks once. One pull request carries every removal and every change of meaning that Decide what is cut, merged or deferred from the spec and the register, Decide between a spec/v2 and reworking v1 in place and the live-need decisions settled, and releases package 1.0.0. No Project hands over before it.
Acceptance criteria
- Codes: the seven compiler self-invariants are tests and no longer codes; the two dead names are gone;
E_DUPLICATE_ROUTEis folded intoE_DUPLICATE_ROUTE_MATCHandE_DUPLICATE_APEXintoE_DUPLICATE_HOST; the six ledger codes are gone. The same bar (a code refuses authored input that is a real hazard at this scale) is applied to every exercised code. - The reconciliation ledgers are gone: the coverage ledger, accepted fragment drift, unmanaged surfaces and their review dates, with chapter 30's sections on them. The Handover ledger stays.
-
alertClassis gone andobservabilityholdsscrapeonly. The soft placement preferences are gone. - Secret delivery
selfis accepted only for an Application that talks to Vault itself. - The per-cluster env overlay is gone: env is one file per scope, and Project Intent never names a Cluster. The term Cluster Target is retired.
- The intent, effective and dependencies goldens are gone. The resolved artifact, the rendered tree and the diagnostics files stay.
- Register: 0007 is rewritten for the lockstep; 0044 is folded into 0032; 0038 is deleted; 0024 loses unmanaged surfaces; 0025 is rewritten. 0044 and 0038 join the Retired numbers table.
-
CONTEXT.mdloses every term the specification no longer uses. -
schemaVersionstays1.0.0. From this release on it equals the package version a fragment was validated with; admission stays same major, and a minor no newer than the toolkit's. - The squash commit's body ends with the
Release-As: 1.0.0footer, and release-please proposes 1.0.0. No version is edited by hand. - Every worked example, oracle file and JSON Schema agrees with the cuts, and
npm run verifypasses.
Blocked by
Metadata
Metadata
Assignees
Labels
area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.priority: P2Medium; normal planned work.Medium; normal planned work.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
Activity
23 remaining items
ExtraToast commentedon Oct 19, 2026
Held by maintainer decision on 2026-10-19 until after Task 3 is submitted on 30 October and
emf/is deleted (#347), as #348 planned: the contract pull request carries no parity cost then. #385 no longer waits for it; it lands first as an additive release.feat(model)!: cut the model to what 1.0 keeps
feat(model)!: cut the model to what 1.0 keeps
feat(model)!: cut the model to what 1.0 keeps
feat(model)!: cut the model to what 1.0 keeps
feat(model)!: cut the model to what 1.0 keeps (#628)
ExtraToast commentedon Oct 27, 2026
Resume here (updated 2026-10-27)
v1.0.0, Release run 40523904774). Checked by pulling@jorisjonkers-dev/deploy-kit@1.0.0from GitHub Packages: itspackage.jsonreads1.0.0and itsSCHEMA_VERSIONis"1.0.0".headRefName(release-please--branches--main--components--deploy-kit), never by title.