feat(prototype): check bound documents for leaks, and filter the queue by type

[AndrejK666]

Two things from the Documents queue.

1. Leak, run from the place that knows the type

A stage can gate on any detector, but only purpose was ever recorded against a
bound file — so a stage gating on leak could never complete from this flow.

leak belongs here for a reason the service itself enforces: it refuses a
document whose type it has not been told —

422  "doc type unknown: pass doc_type, or a path naming the type
      (PRD.md, DESIGN.md, ADR/0001-x.md, features/y.md)"

— because "foreign content" means nothing until you have said what native
content would be. A bound document has a type. Nothing is guessed, and nothing
is inferred from a filename.

It runs over the documents that have a type and writes the verdict both places,
as the purpose run does: the finding to the graph, the pass/fail to the binding,
which is what the gate reads.

It runs unverified, and that was measured

The service verifies its own candidates with an LLM by default, and on this
deployment that pass clears every one of them. Two documents of known kind,
declared correctly and incorrectly, unverified:

document	declared as	passed	share
a design contract	design	✓	0.00
a design contract	adr	✗	0.68
a design contract	prd	✗	1.00
a real ADR	adr	✓	0.00
a real ADR	prd	✗	0.99
a real ADR	design	✗	0.99

Right type → passes at 0.00. Wrong type → fails, and the share tracks how wrong.

With verification on, all six pass — including the ADR read as a PRD at 0.99
raw. Omitting verify behaves the same as verify: true, which is how the
first few probes came back clean and nearly sent this out as a gate that always
opens.

A check that never fires is not evidence that documents are clean, and a gate
wired to one would open for everything while looking like it had checked. So the
run passes verify: false, and the table lives in the comment on detectLeak
so nobody has to re-measure it.

That also gives the queue a second opinion on its own classification: a document
bound to the wrong type fails its leak check.

2. Not bloat or traceability

They are set-wise: one run over a document set producing duplicates and
traces_to relations, with no per-document verdict anywhere in the response
(materializeSetwise turns them into graph edges, which is all they can be).
Gating a stage on them would mean inventing what "this document passed bloat"
means. They stay in the Analyze tab, where relations are what they are.

3. Filter by type

The queue filtered by state only — needs review, bound, not documents, all. It
now also filters by document type: the types this project's documents actually
are, rather than the whole catalogue, plus the undetermined ones.

tsc -b and the 41 prototype tests clean. Frontend only.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 5b24642a-4771-40c7-9463-4cf9d77d6fab

---

_{Comment @coderabbitai help to get the list of available commands.}