move the feature catalogue out of docs, and replace the queue with a plan

Two structural changes, both about what an agent may pull into context.

exploration.md catalogues engine features nobody has asked for. That is storage,
not working material, so it moves to ideas/ where nothing sweeps it and it is
opened only when named — the same rule the other parked material already
follows. Six references repointed; the ideas gates then demanded an index line
and a status, and both were supplied rather than exempted.

build-queue.md was 516 lines, nearly all of it entries 0-23 finished months of
work ago, with the plan buried at the top. It becomes .scratch/continue.md at
49: where the code is, what is planned, and the findings worth carrying that no
doc owns — chiefly that silent damage to prose is this engine's recurring
failure mode, and that three defects this arc were invisible to curl.

Docs and HARNESS point at the new names. No rule, gate or threshold changed.

.claude/commands/leaf.md

@@ -2,7 +2,7 @@
 description: Decide whether a catalog item is a leaf worth building, or a trunk that waits
 ---
 
-Evaluate `$ARGUMENTS` against the leaf/trunk test in `docs/exploration.md`.
+Evaluate `$ARGUMENTS` against the leaf/trunk test in `ideas/exploration.md`.
 
 Research it only as far as needed to answer accurately — what it actually requires, not what its
 homepage claims. If it is a protocol or spec, state which parts are mandatory versus optional.
@@ -20,5 +20,5 @@ Answer these, briefly:
    a legitimate answer for a cheap leaf and a disqualifying one for anything expensive.
 7. **Verdict:** build now / build when gate X opens / trunk, needs an ADR / no.
 
-Write the verdict as one row in the Verdicts table in `docs/exploration.md`. Do not implement
+Write the verdict as one row in the Verdicts table in `ideas/exploration.md`. Do not implement
 anything in this pass.