Repository navigation
Make work-board canonical and qualify outcome/delivery source closure - #4680
Merged
EHotwagner merged 59 commits intoOct 18, 2026
Merged
Conversation
EHotwagner
deleted the
routine/work-board-coordinator-migration-20261018
branch
October 18, 2026 21:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make
$work-boardthe canonical coordinator for programme and explicitly selected product V2 scope. Recovery, capacity, ownership, qualification, delivery, telemetry and progress now share that instruction boundary;work-programmeremains a finite compatibility redirect for old handoffs. Both skill mirrors, UI metadata, caller references, executable staging and generated registries/manifests are dependency-closed.Add explicit outcome/delivery source support through organization binding 5/schema 3, inspection 3 and integrator 2. Bounded hierarchy and classification gaps remain Unknown; only selected delivery identities can be proposed, a blocked sibling does not block independent source work, and source acceptance cannot close a broader parent promise. The maintained migration writer preserves existing human values/view identities and uses absent-only explicit classification. Accepted programme binding 4/schema 2/inspection 2 and product binding 3 retain their scope until separately qualified adoption. Retained 105 qualification is historical; an observed 106 global selector has unknown prior value/change timing and does not prove full runtime or instruction discovery.
Prepare coherent 107 and independently released Creator 017 source. Creator materializes the complete 11-skill driver cohort. Both existing ordinary and candidate workflows retain one fresh external build root through actual FSI, no-build packing and normal 107 eleven-project dependency validation; 16 causal controls guard the actual producer/consumer commands. Recursive mutation runs retain independent temporary roots. Published 106/Creator 016 pins and historical/frozen release profiles remain unchanged. Batch accepted independent Host 0.7 publication metadata after original 39148437514 completed all eight effects; preserve old 0.6 journal 12 intent Unknown and separate Home receiver adoption.
Validation: 217 actual managed tests passed; actual import/pair 52, all 13 programme/handoff collector suites and progress/render 7 passed. The real product materializer and fresh offline Creator 017 package passed (11 projects, 59 built files compared). Four maintained packaging/refusal controls and five independently applied staged instruction journeys passed. Original compile/test/oracle failures and repaired evidence are retained. The remaining tail also passed 735 managed tests locally (BoardOps 280, telemetry 118, Lifecycle 155, Kernel 182), the exact recorded replay (30), shim corpus (626) and resolver checks (87), plus 16 local critic fixtures. Original replay and ambient installed-caller fixture failures are retained. Historical driver fixtures now own their legacy policy input; current canonical instructions remain free of wave authority. Full hosted CI, including the seven critic mutants, and exact delivery correspondence remain acceptance-determining.
This delivery covers only the source/package qualification scope of #4677. Publication, actual installed discovery and absolute selected paths/runtime policy, native field/view/classification/enrollment application, product adoption and restart/rollback remain under #4682 and the full outcome #4641. No caller selector, active binding or native board state changes are included. All 439 + 46 original Unknown holds remain.
Closes #4677.
Refs #4641 and #4682; both remain open.