# Nido Handoff Index
This folder is the repo-local continuation map for Nido-first work. Keep
handoffs short, current, and tied to a task or workstream. Prefer updating an
existing workstream folder over adding a new top-level folder.
## Active Workstreams
- `fop-to-nido-consolidation/` - migration from legacy fop-first surfaces to
Nido-first CLI, docs, MCP tools, deploy, state, and queue/resource management.
Current full residual audit: `fop-to-nido-consolidation/2026-05-22-full-fop-to-nido-audit-plan.md`.
- `nido-capability-wave/` - capability-wave integration notes, GraphRAG inputs,
and E2E audit trail.
- `nido-dioxus-ui/` - Dioxus UI foundation checkpoints awaiting or following
green verification windows.
- `nido-web-ui-goal/` - web cockpit, BFF, PWA, deploy, and fop-web-ui port
program. This lane owns dirty UI/BFF files; avoid overlapping edits.
## Cleanup Rules
- Keep historical handoffs that are cited by `docs/knowledge/nido-research-inputs.toml`.
- Move superseded work into the owning folder rather than scattering root files.
- Do not delete another tab's handoff without first confirming its task is done
and checkpointed.
- When a handoff becomes an implementation source, register it in
`docs/knowledge/nido-research-inputs.toml` so `nido graphrag inputs list` can
prove it remains discoverable.