statuslisted

# System Status Show the current state of the ODD Team maintenance system. ## Protocol 1. Read `state/PROGRESS.md` and display its contents 2. Count actual files to verify accuracy: - Scanner completion: check `findings/` for output from each scanner - Backlog counts: count files in `backlog/{category}/` by status (grep frontmatter) - Navigation coverage: count domain files with vs. without populated code entry points 3. If counts don't match PROGRESS.md, update it 4. **Release trains** (`adrs/drafts/release-train-doc-gating.md`) — derive, never from a state file: - open trains: `grep -rl 'milestone:' backlog/ contributor/` grouped by version × status (**`contributor/` is not optional** — CTRIB items are the largest producer of release-gated work; a `backlog/`-only grep hid 22 stale items for 10 weeks, LSN-041) + `git -C ../documentation branch -r --list 'origin/release/*'` - when network allows: `curl -s https://api.github.com/repos/opendatadiscovery/odd-platform/releases/latest` + `.../milestones?state=open` - **reverse check (LSN-041)** — merged upstream work with no workspace record: `GET /search/issues?q=repo:opendatadiscovery/odd-platform+author:app/odd-contributor+type:pr` and diff the head branches (`contrib/CTRIB-NNN-*`) against `ls contributor/CTRIB-*.md`. A merged PR with no record is invisible work; book it before anything else. - a published release with a still-existing train, or a closed milestone with `pending-release` items → **Next ac