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
Consume the staged fleet program: entitled installs compose the overlay's tuned values; unentitled stays byte-identical (fleet rearchitect P4b companion) #1131
Problem — The fleet program (amicissimo#418) lands as staged overlay data — tuned classifier/engine/queue values composing the base machinery's injectable knobs. The base ships base defaults; NOTHING currently consumes the staged program. Without the consumption wiring, the premium program is dead data.
Approach — The composition point: when the fleet entitlement stages the program manifest (the fleet_overlay dispatch pattern — the same gate fleet_staging.ts already consumes), the extension's fleet machinery composition feeds the staged values into the injectable knobs (#1070's classifier tuning, #1072's verify budget + pending cap, #1092's retries); unentitled → base defaults, byte-identical behavior (asserted). The ADR-0003 skew check is honored client-side: a program stamped against an older base revalidates field-by-field or is skipped with a recorded reason — never silently merged stale.
Scope — in: the program-manifest consumption + composition wiring + skew/validation client-side + tests · out: the program manifest itself (amicissimo#418 — build against its documented shape, fixtures modeled on it), the checkout flow (P6), any new machinery
Acceptance Criteria
Entitled + staged program → the classifier/engine/queue compose the staged values (each knob asserted receiving the program's value, not the base default)
Unentitled / program absent → base defaults, byte-identical behavior (asserted: the composed config equals the base defaults exactly)
The skew rule client-side: an older-stamped program revalidates field-by-field or is skipped with a recorded reason — never silently merged stale
An unknown field in a staged program is rejected loudly (mirroring the freeze validator — the base never silently ignores a value it doesn't understand)
Provenance renders (the program's stamps surface in the fleet status/doctor detail — the cockpit says where its tuning came from)
Typecheck + suite green at the environmental baseline; the solo floor untouched
Testing Decisions — vitest; fixture programs modeled on #418's documented shape; the F-harness where a fault-mode matters
Constraints — vitest only; no new deps; additive only; the program's SHAPE is amicissimo's (consume, never re-define — the #1068 precedent); overlay-mutation side effects uncommitted; shared checkouts + skills-agent worktrees OFF-LIMITS; worktree off origin/main only
Source — Part of approved spec spec-20260913-114814 (§3, ADR-0004 d3, ADR-0003 d7) · builds on #1070/#1072/#1092 (merged) · the program manifest: amicissimo#418 (verify its shape or build against the issue's documented contract)
Notes — RECON FIRST: the injectable knob surfaces in attach_state.ts / transport_classifier.ts / proposal_queue.ts + how fleet_staging.ts consumes manifests today. Gate discipline: director re-runs every verdict; merges per the standing green directive.
Activity
Merge pull request #1132 from harmoniqs/1131-program-consumption