Snapshot: November 3, 2026. Read each list from top to bottom: quick wins first, then the remaining ready work in priority/dependency order. Quick wins are bounded candidates, not time estimates. Recheck the live issue and current source before starting; this index does not mark acceptance complete. Existing notes below are context and may reference issues that have since closed.
Ready means a concrete engineering slice can start without a new owner decision or external account/host. Where an issue mixes local work and external acceptance, only the named local slice is ready. Blocked entries state what releases the block; fixture preparation and investigation can continue independently.
- #268: P1: Attach rust-cache inputs to rust-cache instead of install-action — P1 move cache inputs to the correct action.
- #265: Epic: Complete dependency-update coverage and consistent CI caching — Updater/action/cache work independent of owner decisions.
- #264: Epic: Validate and finalize Cargo profiles, output paths, and linker policy — Local profile/path measurements; external hosts still needed for platform gates.
- #259: Epic: optional library, CLI, and coverage follow-ups — Optional follow-ups after CI defects; choose one focused child at a time.
None currently open.
Open work is tracked in GitHub Issues. Keep one topic per issue, except epics, with a problem, task list, and acceptance criteria. Record status and validation evidence in the issue rather than duplicating checklists here.
None currently open.