# Cursor Optimization Backlog

**Last Updated:** 2026-04-03

Prioritized carry-forward queue for items not safely completed in the originating run.

## Priority Levels

- `P1`: quality/safety risk
- `P2`: token/cost high impact
- `P3`: governance cleanup / low risk

## Backlog Item Template

- ID:
- Priority:
- Source Run ID:
- Slice:
- Summary:
- Root-cause hypothesis:
- Required preconditions:
- Risk level:
- Owner:
- Target run:
- Status: `open|in_progress|blocked|closed`

## Current Queue

- ID: `BL-0001`
- Priority: `P2`
- Source Run ID: `OPT-RUN-2026-04-03-01`
- Slice: `A`
- Summary: Reduce remaining intentional overlap in `v2/data/blog/posts/**/*.json` while preserving JSON safety guardrails.
- Root-cause hypothesis: advisory/runtime concerns still share broad globs.
- Required preconditions: validated split map for critical vs advisory guidance.
- Risk level: medium
- Owner: unassigned
- Target run: next Slice A run
- Status: `open`

- ID: `BL-0002`
- Priority: `P3`
- Source Run ID: `OPT-RUN-2026-04-03-01`
- Slice: `B`
- Summary: Consolidate high-volume `NEXT_STEPS` docs further into domain changelog pointers.
- Root-cause hypothesis: historical content growth outpaced consolidation.
- Required preconditions: domain SSOT map review complete.
- Risk level: low
- Owner: unassigned
- Target run: next Slice B run
- Status: `open`