fix(ledger): map gone-repos|repo-gone — it is world, not instrument (#1676)

A `gone-repos|repo-gone` row landed in the committed ledger with no KIND_OF
mapping, so it fell to DEFAULT_KIND (instrument) and the parity test went red.
That test gates the pre-push hook, so main currently refuses every push.

It belongs in `world`. check-gone-repos writes the `gone` state ONLY when
GitHub answers 404 to a direct read of the repository — rate limits, 5xx and a
missing token all classify as unchecked and can never produce it. So the
finding is a repository actually deleted upstream, which is the ecosystem
moving past our record and the product doing its job. Reading it as
`instrument` says our scanner broke, which is exactly the confusion that state
was introduced to end.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: theboycoder

src/lib/improvement-ledger.ts

@@ -435,6 +435,11 @@ const KIND_OF: Record<string, FindingKind> = {
 	"scf-crosscheck|scf-understated": "world", // …or more
 	"scf-crosscheck|scf-round-overclaim": "world",
 	"engine-d-demand|coverage-gap": "world", // real demand for a project we do not hold — a curation add
+	// check-gone-repos writes `gone` ONLY on a direct GitHub 404; rate limits,
+	// 5xx and a missing token classify as unchecked and can never produce it.
+	// So this is the repository actually deleted upstream, not our scanner
+	// failing — that distinction is the reason the state exists.
+	"gone-repos|repo-gone": "world",
 	// ── instrument: our measurement or serving broke ──
 	"golden-eval|golden-fail": "instrument",
 	"engine-a-recall|recall-miss": "instrument",