Repository navigation
Description
Work level: Delivery · Track: Active delivery · Intended Status: In progress
Owner
Root coordinator integrates and owns native adoption; hardness5273 owns source, tests and the same source chain. Independent source review follows the frozen candidate.
Done when
- Coordination Project 3 stores a versioned Delivery hardness category and shows it on cards, including explicit Unknown. Categories derive from the accepted LEARN-02 rubric without conflating routing safety floors or missing scores with measured difficulty. Dimension scores and classification provenance remain recoverable.
- Closed Deliveries retain the actual model and reasoning effort that worked them, preserving worker/critic roles and multiple execution identities. Requested routing and observed execution remain distinct; historical missing facts stay Unknown. Authoritative evidence supports every backfilled value.
- New dispatch/completion recording and maintained card projection keep values current. Closing or archiving preserves durable provenance on the owning issue. Existing closed items receive evidence-based backfill within the qualified complete selected population, with coverage and gaps reported honestly.
- The maintained schema/view migration and guarded writer preserve existing enrollment, fields, values, view settings and installed automation. Relevant tests, independent source review, exact-head CI, actual native card readback and visible-field verification establish adoption; source merge alone is insufficient.
Current deliverable
Source accepted through PR #5275, merged on 2026-11-03 as 5c85692721c45ee929fab4f6e600ac3226e3b631. Protected main has the exact reviewed/tested tree 8ff62fa379379416e0147837dd8b1362db8011f5. Independent review passed the cumulative provenance guards and coherent native report producer/consumer path. All 65 corrected original CI runs passed on attempt 1; 91 native checks passed and five were skipped by explicit event guards. All ten required contexts passed for the exact head and GitHub Actions App. Post-merge original CI is being observed separately. No LEARN fields, card views, historical metadata, installed caller, routing policy or timer has been activated by source acceptance.
The v1 lexical hardness categories remain provisional and unvalidated across models and reasoning effort. Source/unit/native mechanism checks do not establish measurement validity. #5276 now carries the priority validity assessment; no learned routing or validated-difficulty claim follows from this merge.
Next action
Prioritize #5276's cross-model/effort validity assessment before Root decides native category rollout. Separately prepare normal coherent publication and qualify the actual installed compiled migration caller. Before native adoption, record exact hub-helper discovery: the Coordination Project3 lifecycle owner runs the Python recorder/projector from an explicitly selected protected accepted FS-GG/.github checkout, verifies origin and exact revision, and uses absolute helper paths; Drivers do not package these helpers. Product consumers delegate this Project3 boundary to the hub owner. Source-helper adoption is distinct from installed migration CLI qualification.
Then, only under Root's separate selected effects, refresh the complete qualified native metadata population and exact field/view preimages; create/read back additive fields, supported visible-field projection and evidence-based current/closed Delivery metadata. Preserve all enrollment, values, view identities/configuration and existing automation. Retain missing historical facts as Unknown, verify actual cards and durable owning-issue provenance, and carry archived-history gaps explicitly. Publication, installed adoption, metadata backfill and visible-card verification remain acceptance work.
Blocked on
Source integration is complete. Native annotation adoption requires normal publication, actual installed caller qualification and separately selected guarded native effects. Native hardness category rollout additionally awaits Root's disposition after the #5276 validity assessment. Historical execution gaps remain Unknown. The Delivery remains OPEN / In progress.
Acceptance evidence
Baseline #5249 / PR #5250; accepted source PR #5275. Corrected original CI: always-gates, coord-github, and tested checkout / coherence. All 65 corrected runs passed attempt 1, with exact-head required checks and matching reviewed/tested tree. The original failed cohort and its determining errors were retained; no rerun replaced it. Source acceptance does not satisfy the native adoption or hardness-validity remainder.
Refs #5248
Activity
EHotwagner commentedon Nov 3, 2026
Root admits this user-prioritized Delivery pending normal batch enrollment. Source preparation may proceed under this issue; native fields/views, enrollment changes and installed activation retain their qualified effect routes. This is the next new feature priority. Historical actual model/effort facts require authoritative execution evidence; missing values stay Unknown.
EHotwagner commentedon Nov 3, 2026
Source acceptance: PR #5275 merged as
5c85692721c45ee929fab4f6e600ac3226e3b631; protected main tree8ff62fa379379416e0147837dd8b1362db8011f5exactly matches the independently reviewed and tested source. All 65 corrected original CI runs passed on attempt 1 (91 passed checks; five event-guard skips); all ten required contexts join the exact head and GitHub Actions App. The original failing cohort and fixes remain preserved. Post-merge CI is a separate bounded observation.This Delivery remains OPEN / In progress with its entire Done when unchanged. Publication, actual installed compiled migration caller qualification, separate guarded fields/views/backfill, durable historical provenance, complete-scope coverage and actual visible-card readback remain outstanding. No native category, routing policy, timer or installed fleet change is claimed.
The Python recorder/projector are hub-source helpers: the Coordination Project3 lifecycle owner selects a protected accepted FS-GG/.github checkout through its owning session/handoff, verifies origin and exact HEAD, and invokes absolute
scripts/learn-dispatch.py/scripts/learn-projection.pypaths from that checkout. They are not Drivers workspace payload. Product consumers delegate this Project3 boundary to the hub owner. Their adoption is distinct from normal publication and physical qualification of the compiled migration CLI. This discovery/receiver distinction must be explicit in the native-adoption runbook and record before that boundary.Hardness v1 remains provisional and unvalidated across model/effort profiles. Passed source, unit and native mechanism checks do not establish measurement validity. #5276's validity work has priority; Root must dispose that result before selecting category rollout. No learned routing activation or validated-difficulty claim is made.
Evidence: PR #5275, always-gates, coord-github, tested checkout.
EHotwagner commentedon Nov 3, 2026
Root accepts the bounded source/native setup: PR #5282 merged0c1d4e7442256b0b9232269b053c3dbdb39da7c9 with all38 original runs/ten required contexts successful and exact independently verified14 delivered blobs. The protected producers default native hardness to Unknown while retaining original provisional assessments; this establishes no validated predictor.
Qualified installed0.115 migration created exactly four additive fields: Hardness, Actual models, Actual effort, Execution provenance. All17 pre-existing fields are preserved. Five existing views now append these four independently resolved field IDs; all names/layouts/filters/Status vertical grouping/sorts and the other five views are preserved. Both mutation stages completed; independent native schema/configuration readback passed. Original null-ID creation readback exit3 is retained; creation is supported by correlated per-effect readbacks plus a genuinely fresh resolved-ID zero-change observation. Original five-view readback exited0. No creation or mutation was replayed.
No annotation values, model/effort claims, provenance comments/telemetry, enrollment, bindings or timers were changed in those stages. This accepts additive fields and native view configuration only. Populated-card/rendering acceptance, genuine cumulative execution records, future lifecycle maintenance and qualified historical backfill remain; actual model/effort stays Unknown without authentic evidence. Use protected policy helper source before selecting any assignments. Delivery5273 and Outcome5248 remain OPEN.