Feature flag library

Flag-by-flag tracking with built-in cleanup discipline.

## How to use

- Every new flag gets a row in **Flags** AND a section in the decision log.
- Cleanup-by date is mandatory.
- Once a flag is at 100% rollout for 30 days OR cut entirely, it goes to **Cleanup queue**.

## Flags

Use the **Flags** surface. Columns: name, owner, status (off / rolling / 100% / cut), default value, rollout %, cleanup-by date.

## Cleanup queue

Use the **Cleanup queue** surface. Auto-populated from Flags. Columns: name, removed-by, owner, removal PR.

## Decision log

One section per flag. What problem the flag solved, what hypothesis it tested, what we learned.

### [Flag name]

- **Created:** date
- **Why:** the problem it solved
- **Hypothesis:** what we expected to learn
- **Outcome:** what we learned
- **Removal:** when, how, link to PR

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.