Rescued: two untracked ledgers

Both files were untracked and not gitignored, which means one git clean would have deleted them with no warning.

What was at risk

File	Size	What it holds
`.claude/ORANK-EVIDENCE-2026-08-23.md`	5.3 KB	orank report refutations probed against live prod, not inferred
`docs/conductor-ledger.md`	41.6 KB	read-only repo-state triage ledger, 818 lines

Why this is a real hazard, not tidiness

Untracked and un-ignored is the worst of both. Git will not protect the file, and it will not warn you about it either. git check-ignore returned rc=1 for both, so neither was a deliberate exclusion. They simply were never added.

How they were checked before landing in a public repo

OrchestKit is public, so both were scanned before being committed: zero secret-shaped tokens, zero email addresses, zero client names. Content is engineering triage only.

The pattern worth reusing

The same hazard was fixed for two playground pages in #3703 hours earlier. Preserving a file needs no decision from anyone. Deleting one does. When work is unpushed or untracked, push or commit it first, then decide its fate with nothing at stake.