docs(agents): the gate that cannot see a working tree, and the Phase 5/7 checks re-run #36
Reference in New Issue
Block a user
Delete Branch "docs/consolidation-dirty-tree-finding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records a finding from 2026-09-14 that bears directly on Phases 5 and 7, both of
which are still open and both of which would have destroyed it.
⚠️ Based on
plan/consolidation(#29) — one commit on top, so the diff is just thischange. Merge #29 first.
The finding
xenia-rshad 468 uncommitted lines plus an untracked 338-lineimports.rsincrates/xenia-analysis— the very crate Phase 3 lifted. Written 2026-09-10 21:01–21:23,found four days later while pulling the repos.
It existed in exactly one place, and that place was not git — verified absent from both
iterate-4Aand the lifted crate in #32.Why the gate passed anyway
Phase 0 is titled "Secure the single-copy work". Its gate iterates
refs/headsandasks whether each branch is reachable from a remote. A dirty working tree has no ref,
so the gate is structurally incapable of seeing this. Canary's two dirty files were
secured only because a human already knew they were there — nothing found them. Phase 1
then pushed xenia-rs's four branches and declared the archive honest while this sat
beside them.
Phase 5 ends with "delete the local clone"; Phase 7 drops the emulator.
What this PR adds to the page
The finding, placed immediately before Phase 5 — the phase that would have
destroyed it.
The missing half of the gate, as a runnable snippet:
Run across all four on 2026-09-14: only
xenia-canaryis dirty, and both entries(
build-cross/,vkd3d-proton.cache) are already on Phase 7's drop list.A fifth entry in the "claims on this page that were wrong" list, and the heading
count corrected from four to five. Phase 0 was recorded as done; it was incomplete,
and its gate could not have caught the gap.
A
0brow in the status table pointing at where the work now lives.The Phase 3 residue found while porting. The sharpest was
tools/zq.pydefaulting its database path to a location inside
xenia-rs— the repositoryPhase 5 archives and Phase 7 drops. That one is now fixed in #35 (
38cc170):$SYLPH_XEXDB→<repo root>/sylpheed.db→ a refusal naming both, with no thirdfallback, because the database is an untracked build artefact and a default that
silently resolves to the wrong one is worse than no default.
SCHEMA.md'sretired-repo heading remains outstanding and stays listed on the page.
Disposition of the work itself
xenia-rsharvest/import-thunk-naming@b4f19f1, pushed — committed exactly as found,cargo check= 0feat/xexdb-import-naming, stacked on #32 — tests 10/0, clippy and fmt cleanThis page's own closing advice is "Run them again rather than trusting the results
recorded here." That is what turned this up.
🤖 Generated with Claude Code
Second commit: the Phase 5 and Phase 7 checks, re-run
This page says "Do not trust this page's ledger when you get there." So they were
run rather than read. Nothing was archived and nothing was deleted — both are
yours, and both phases stay open.
🔴 Phase 5's containment check is the wrong test for half the list it names
Syplheed-RebornSylpheed-Godotxenia-rsandxex2tractorwere never absorbed — their disposition isharvest, then archive. Run the containment check literally against
xenia-rsandit returns 42 of 42 refs "NOT PRESENT in Sylpheed": every line true, every line
unactionable. That is the failure this page already names once, about Phase 0's
first gate.
For those two the invariant is that the harvested artefacts are in Sylpheed and
the repo is archived, not deleted. Checked separately — and it turns up a
sequencing point:
maindocs/reference/xex2-format.mddocs/reference/xbox360-exports.jsonLICENSEcrates/sylpheed-xexdb(32 files)⚠️ The harvest is real but is not on
mainyet. Archiving stays safe — thebranches are pushed and archiving is reversible — but Phase 5 should follow the
harvest PRs rather than precede them.
Phase 5 · nothing outside git — re-verified, still true
0 issues / 0 PRs / 0 releases in all four retiring repos (Sylpheed: 36 / 19 / 0).
📌
has_wiki: trueis the repository feature flag, not content —/wiki/pagesreturns 404 on all six, i.e. never initialised. Read the flag as content and
you would report six wikis that do not exist.
📌 All six are still
archived: false,private: false— the retentionquestion is unchanged, now with a number:
docs/re/captures/is ~87 MB of gamescreenshots in a public repository.
Phase 7 · most of the drop list is not on this machine
agent-backups/xenia-rs/audit-runs/pi/*branchestexcompare/,ship_render/stock-oracle/Sylpheed/target/✅ Phase 7's open question is answered. It asks to confirm nothing in
docs/re/cites
texcompare/orship_render/.texcompareis cited nowhere. Fourship_rendercitations exist and all four name the example program, not theoutput directory —
cargo run --example ship_render. The directories aredroppable; the example is tracked code and stays. Same directory-vs-file
distinction that made Phase 4's "10 dangling citations" turn out to be one.
⚠️ Disk is at 90 %, 96 GB free — the page records 83 %.
Sylpheed/target/is34 GB of that and the only large item here, but deleting it is yours: it is hours
to rebuild.
docs(agents): the Phase 0 gate cannot see a working tree — it missed 468 linesto docs(agents): the gate that cannot see a working tree, and the Phase 5/7 checks re-run