T-0RW4-index-generator-status-bucket-coverage
Status: closed/done · Impact: medium · Complexity: small
The index generator’s Active/Emerging/Obsoleted bucket map does not account for the Driver and Capability on-disk statuses, so both sections render entirely in the follow-up (emerging/obsoleted) table rather than showing their entities as active. A human decision is needed on the fix and then its implementation. Originates from T-VWH3-ts-index-generator-script in git@github.com:sksizer/dev.git.
The index generator’s Active/Emerging/Obsoleted bucket table omits the Driver and Capability on-disk statuses (validated/verified), so both sections render entirely in the follow-up (emerging/obsoleted) table. Decide and implement: either bless those statuses into the Active bucket (generate_index.ts bucket map) or normalize the source entities’ statuses. Needs a human decision, not silently fine.
— T-VWH3-ts-index-generator-script post-mortem
TBD — receiver to fill before promoting from planning/draft.
Proposed
Section titled “Proposed”TBD — receiver to fill before promoting from planning/draft.
Approach
Section titled “Approach”TBD — receiver to fill before promoting from planning/draft.
Files to touch
Section titled “Files to touch”TBD — receiver to fill before promoting from planning/draft.
Acceptance criteria
Section titled “Acceptance criteria”TBD — receiver to fill before promoting from planning/draft.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”Spawned by /sdlc:spawn-task-pr on 2026-06-03 UTC from T-VWH3-ts-index-generator-script in git@github.com:sksizer/dev.git.