get-statuslisted

# Get the ODD Loop Status Answer "where is the loop?" for this repository, from its committed memory alone. Every input is already in the clone — the stored reports, the ruling ledgers, and git — so the status costs no backend query, no running stack, and no network: it is what the loop wrote down about itself. ## Sources — and nothing else - `.odd/observe-run-reports/` and `.odd/otel-instrumentation-reports/`: frontmatters first, bodies only where a step below needs their structured tables or a verification's rulings; - git metadata about the repository and those files: report commit dates, and each report's `revision` and `tree_anchor` fields against the commits that came after it — resolved in the repository the report's `repository` field names: the store's own when the field is absent or names the store, otherwise the clone the caller named (`--repository <identity>=<path>`), and nowhere when none is named; - `.odd/decisions.md`, the findings decision ledger, and `.odd/entry-classifications.md`, the tree-entry classification ledger — both read through the ledger contract `odd-memory`'s `decisions` reference owns: that reference is the format's authority, this skill only reads what was written under it. A missing file means no decision, or no classification, has been recorded yet, which is a fact, not an error. All of them are read under the memory contract (`odd-memory`): frontmatter first, then sections, never a whole file without a stated