Exact identifiers are found, an Edit is not proof of verified, and a package is not a file

[Coder8124]

Three 0.5.1 fixes, each with a test that fails on the old code.

Searching for WG-4471, ENG-1234 or 0.4.10 finds the note that contains it (34ae500)
ftsQuery stripped punctuation and glued the pieces into one token (WG4471), which the FTS index never holds — it indexed wg then 4471. A word with punctuation in it now becomes a phrase, "WG 4471", which matches the identifier as a unit and not a note that has wg and 4471 apart. With embeddings off, the old binary said "Nothing in the vault matches".

A successful file edit is no longer proof that a distilled claim was verified (30b11a6)
The citation filter accepted any tool turn with status ok, and Claude Code reports an Edit as ok. So "the crash is gone (turn 3)", citing the edit that tried to fix it, was kept as verified. A verified claim now needs a cited turn whose tool ran a command (isShellTool, the existing per-harness list). Matching the runner names rather than excluding edit names fails safe: an unknown runner costs a claim, an unknown edit tool would let a false one through. The distiller prompt and the ingest_distil description now say a file edit is not a demonstration.

A package or directory a command names is no longer listed as a touched file (e990ed3)
filesInCommand took any argument with a slash as a file, so go test ./cart put cart in Files, alongside cd directories and sed expressions. A slashed argument now needs an extension. An extensionless file named only in a shell command drops out of Files but stays in Commands.

Verified

• go build ./... && go vet ./... && gofmt -l . && go test ./..., go test -tags chaos ./chaos/..., staticcheck ./... — clean
• Scratch MCP run over a Claude Code transcript (Edit cart.go, then go test ./cart): the old binary kept 2 verified claims and listed cart; the new one kept 1, reported the dropped claim with its reason, and listed only cart.go