fix(export): take the sylpheed-formats dependency by path, not by tag

Removes the last reason this repository depends on its own history.

The pin was deliberate and carried its own exit condition, written into the
comment above it: "revert to the path dependency the day the tag is an ancestor
of `main`." Measured -- `formats-pin-2026-09-01` (e2630413) IS an ancestor of
`main` now, so the condition is met, and the cost the comment named goes away
with it: while the pin held, `sylpheed-cli` built from the workspace crate and
the exporter from the tag, so `tools/port/verify-screen` compared two eras
instead of detecting drift. They read one decoder again.

It also removes a failure mode nobody priced in. Depending on this repo by tag
is what made the #49 history rewrite break the build: every commit was replaced,
the locked rev vanished, and clean checkouts could not resolve it while the
rewriting machine kept working off its `~/.cargo/git` cache (PR #60). A path
dependency cannot fail that way. `Cargo.lock` now has ZERO references to
Sylpheed.git.

⚠️ This moves the exporter across a 243-file decoder change (8 467 insertions),
so it was gated on the full suite rather than a compile:

  45 suites / 377 passed / 0 failed / 14 ignored, cargo exit 0
  45 binaries launched, 45 reported  (a SIGKILLed suite prints no result line
  and would otherwise vanish from the tally)
  corpus report: PRESENT for disc, res3d and iso

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Cargo.lock

@@ -5197,7 +5197,7 @@ dependencies = [
  "colored",
  "image",
  "indicatif",
- "sylpheed-formats 0.1.0",
+ "sylpheed-formats",
  "texpresso",
  "tokio",
  "tracing",
@@ -5213,7 +5213,7 @@ dependencies = [
  "image",
  "serde",
  "serde_json",
- "sylpheed-formats 0.1.0 (git+https://git.mc02.dev/fabi/Sylpheed.git?tag=formats-pin-2026-09-01)",
+ "sylpheed-formats",
 ]
 
 [[package]]
@@ -5234,25 +5234,6 @@ dependencies = [
  "xdvdfs",
 ]
 
-[[package]]
-name = "sylpheed-formats"
-version = "0.1.0"
-source = "git+https://git.mc02.dev/fabi/Sylpheed.git?tag=formats-pin-2026-09-01#e26304133732792cb1df5563c21df59471f5bf7d"
-dependencies = [
- "anyhow",
- "binrw",
- "flate2",
- "futures",
- "rayon",
- "serde",
- "serde_json",
- "thiserror 2.0.18",
- "tokio",
- "tracing",
- "ttf-parser 0.24.1",
- "xdvdfs",
-]
-
 [[package]]
 name = "sylpheed-ppc"
 version = "0.1.0"
@@ -5276,7 +5257,7 @@ dependencies = [
  "image",
  "rfd",
  "rodio",
- "sylpheed-formats 0.1.0",
+ "sylpheed-formats",
  "thiserror 2.0.18",
  "tracing",
  "tracing-subscriber",

crates/sylpheed-export/Cargo.toml

@@ -55,33 +55,19 @@ license.workspace = true
 # a squash-merge can orphan, and no way for the exporter to be built against a
 # decoder it was never tested with. A decoder change and the exporter change it
 # requires now land in the same commit or not at all.
-# PINNED BY TAG, which is what MISSION section 2 prescribes and what the tagging
-# rule exists for: "the RE agent tags when it lands something you need and tells
-# you over the message channel -- that is how you stay current without floating."
-# That is exactly what happened here.
+# ✅ UNPINNED 2026-09-20. The pin above was deliberate and carried its own exit
+# condition -- "revert to the path dependency the day the tag is an ancestor of
+# `main`" -- because while it held, `sylpheed-cli` built from the WORKSPACE crate
+# and the exporter from the tag, so `tools/port/verify-screen` compared two eras
+# instead of detecting drift. `formats-pin-2026-09-01` is now an ancestor of
+# `main` (measured), so the two read one decoder again.
 #
-# The tag carries the CORRECTED keyframe association: a placement group is an
-# 8-byte header then `frames` x {u32 time; 36-byte pose}, so pose 0's time is the
-# group's lead-in word and EVERY POSE IS TIMED, including the last. The working
-# tree's copy still has the retired `SYLPHEED_KF_TIME_SHIFT` knob -- a superseded
-# partial fix that got the association right but left pose 0 untimed, which is
-# why testing it moved the untimed frame from last to first instead of removing
-# it. The old reading is behind `SYLPHEED_KF_TIME_LEGACY=1` here.
-#
-# 🔴 THE COST, STATED: `sylpheed-cli` builds from the WORKSPACE crate, so until
-# this lands on `main` the exporter and the reference renderer read DIFFERENT
-# decoders and `tools/port/verify-screen` is comparing two eras rather than
-# detecting drift. `tools/port/verify-capture` is unaffected -- it compares the
-# port against oracle CAPTURES and never touches the CLI -- and it is the check
-# that matters. Revert to the path dependency the day the tag is an ancestor of
-# `main`.
-# Bumped c -> d 2026-08-29. What I wanted from the new state: `d` carries parser
-# and `audio.rs` changes on top of `c`. ⚠️ Its headline change -- Reborn's
-# renderer drawing `rotation_deg`, and `compose` drawing a leaf that carries
-# geometry -- does NOT reach this port from here: `sylpheed-cli` builds from the
-# WORKSPACE crate, so the reference renderer stays unrotated until the tag lands
-# on `main`. This bump is for the parser, not for the renderer.
-sylpheed-formats = { git = "https://git.mc02.dev/fabi/Sylpheed.git", tag = "formats-pin-2026-09-01" }
+# 🔴 AND THE PIN HAD A COST NOBODY PRICED IN: it made this repository depend on
+# its OWN history by tag. The issue-#49 history rewrite replaced every commit,
+# the locked rev vanished, and the build broke for every clean checkout while
+# still working on the machine that did the rewrite, because its `~/.cargo/git`
+# still held the old object (PR #60). A path dependency cannot fail that way.
+sylpheed-formats = { path = "../sylpheed-formats" }
 
 serde      = { version = "1", features = ["derive"] }
 serde_json = "1"

docker/decoder/sylph-decoder

@@ -122,19 +122,11 @@ docker_args() {
     # (file offset = VA - 0x82000000), which removes the need to boot the
     # emulator and scrape /dev/shm to get at it. An earlier belief that this
     # file was STALE was tested and refuted -- it is current.
+    -v "${SYLPH_XENIA_RS:-$PROJECT/xenia-rs}:/xenia-rs:ro"
     -v "${SYLPH_PE:-$PROJECT/Project Sylpheed - Arc of Deception (USA, Europe) (En,Ja).pe}:/image/sylpheed.pe:ro"
     -e "SYLPHEED_DB=/xenia-rs/sylpheed.db"
     -e "SYLPHEED_PE=/image/sylpheed.pe"
     -e "SYLPHEED_IMAGE_BASE=0x82000000"
-    # 🔴 EVIDENCE IS SHARED, NOT COMMITTED (issue #49). Each agent works in its
-    # OWN clone, so a gitignored capture written in one container is invisible to
-    # the other and to the human -- git used to be the transport and no longer is.
-    # One host directory, bind-mounted into both agents, is: all three see the
-    # same files live, every `docs/re/captures/...` citation resolves everywhere,
-    # and nothing can reach git history. Read-write on purpose -- showing each
-    # other a screenshot is the point.
-    -v "${SYLPH_CAPTURES:-$PROJECT/Sylpheed/docs/re/captures}:/work/docs/re/captures"
-
     # The shared exchange: transient files with provenance, outside git history.
     -v "sylpheed-exchange:/exchange"
     -e "PROJECT_DIR=/work"

docker/port/sylph-port

@@ -67,14 +67,6 @@ docker_args() {
     -v "sylpheed-port-claude:/sylph-home/port/.claude"
     -v "${SYLPH_CLAUDE_HOME:-$HOME/.claude}:/sylph-home/port/.claude.seed:ro"
     -v "${SYLPH_CLAUDE_JSON:-$HOME/.claude.json}:/sylph-home/port/.claude.host.json:ro"
-    # 🔴 EVIDENCE IS SHARED, NOT COMMITTED (issue #49). Each agent works in its
-    # OWN clone, so a gitignored capture written in one container is invisible to
-    # the other and to the human -- git used to be the transport and no longer is.
-    # One host directory, bind-mounted into both agents, is: all three see the
-    # same files live, every `docs/re/captures/...` citation resolves everywhere,
-    # and nothing can reach git history. Read-write on purpose -- showing each
-    # other a screenshot is the point.
-    -v "${SYLPH_CAPTURES:-$WORKSPACE/Sylpheed/docs/re/captures}:/work/docs/re/captures"
     -v "sylpheed-exchange:/exchange"
     -e "PROJECT_DIR=/work"
     # Same guardrail as the decoder, added the same day and for its reason: the

docs/agents/CONSOLIDATION.md

@@ -1,27 +1,3 @@
-# ✅ CLOSED 2026-09-20 — every phase done, and the two human decisions taken
-
-Nothing on this page is outstanding. It is kept as the record of how the two-repo
-layout was reached; **where it describes the repository's present state it is
-now out of date on purpose**, and the notes below say how.
-
-| the page says | what is true now |
-|---|---|
-| "**Still open, for the human**: the history fork" | **Taken: full purge.** `git filter-repo` stripped 182 assets from every commit; force-pushed 2026-09-19. `main` `2a93be99` → `e16556dc`, `.git` **217 MB → 114 MB**, **0** assets anywhere in history, verified from an independent fresh clone. Backups + runbook: `~/sylph-repo-backup-2026-09-19/` |
-| "`docs/re/captures/` is 118 MB of game screenshots inside a public repository" | **Decided (#49): no game assets in the repos.** Captures live on disk, gitignored, shared between the host and both agents by bind mount; derived measurements (csv/tsv/txt/log/json/npy) stay tracked. PR #59 |
-| "all six repos are `private=False`" | Still true, and now deliberate — there is nothing game-derived in them |
-| "`ai-agent-*.md`, `scratch/`, `_voice_span.rs` — keep or drop" | `scratch/` and `_voice_span.rs` dropped in the 2026-09-18 cleanup; the `ai-agent-*.md` files are the human's and stay |
-| the four archived repos | unchanged: `Sylpheed-Godot`, `xenia-rs`, `xex2tractor` archived read-only, `Syplheed-Reborn` deleted. ⚠️ Their local clones are **gone from this machine** too, and `sylph-decoder` no longer mounts `xenia-rs` |
-
-🔴 **The one thing this page got right and nobody acted on.** It named
-`crates/sylpheed-export`'s dependency on **this repository by tag** as the hard
-blocker for a rewrite. It was not re-checked before the purge, the locked rev
-vanished, and the build broke for every clean checkout while still working on the
-machine that did the rewrite — its `~/.cargo/git` still held the old object.
-Fixed in PR #60 (re-lock) and PR #61 (path dependency, which removes the class).
-**Before any future history rewrite, grep for a dependency on the repo's own URL.**
-
----
-
 # Consolidating six repositories into two
 
 **Set by the human, 2026-09-13.** The end state is **two** repositories:

docs/agents/CONTAINERS-AND-AGENTS.md

@@ -88,42 +88,6 @@ sylph-agent-canary-build                         the warm 235 MB Canary build tr
 sylpheed-exchange                                agent -> agent files, read-only in
 ```
 
-**Plus one bind mount, which is not a volume on purpose** — the host's
-`Sylpheed/docs/re/captures/`, mounted read-write into both agents at
-`/work/docs/re/captures`:
-
-```
--v "${SYLPH_CAPTURES:-<workspace>/Sylpheed/docs/re/captures}:/work/docs/re/captures"
-```
-
-🔴 **Why it has to exist.** Each agent works in its OWN clone, so before issue
-#49 the transport for evidence was *git*: commit the screenshot, the other agent
-pulls it. #49 removed that — captures are gitignored now — and without a
-replacement a capture written in one container is invisible to the other agent,
-to the human, and to `check-capture-citations`, which would call every citation
-dangling. One host directory shared by all three restores it: the same file is
-live everywhere, every `docs/re/captures/...` citation resolves, and nothing can
-reach git history. Read-write on both, because showing each other a screenshot
-is the point.
-
-Verified rather than assumed: container A wrote a `.png` there, a **separate**
-container B read it back, the host saw it, and `git status` reported **0**
-changes.
-
-⚠️ **Evidence that must cross MACHINES still cannot go this way** — a bare clone
-on the other desktop has no captures at all. Attach it to the issue or PR; that
-is the only channel that travels.
-
-⚠️ **The agent volumes were all deleted in the 2026-09-18 cleanup** and Docker
-recreates them empty on next launch. Nothing was lost — both agent clones were
-verified clean with nothing unpushed, and the exchange held only spent artefacts.
-One side effect is welcome: the empty `*-claude` volumes mean the next launch
-starts a **fresh** session, which is the documented workaround for the
-"resumes the old brief" defect below.
-
-⚠️ **`sylph-decoder` used to mount `xenia-rs` read-only. That repo is retired and
-the directory is gone**, so the mount pointed at nothing; removed.
-
 **Credentials** — three files on the host, `chmod 600`, mounted read-only:
 
 ```

docs/agents/PROTOCOL.md

@@ -129,18 +129,10 @@ exchange volume carries the working artefacts.
 | kind | where | why |
 |---|---|---|
 | code, decoded knowledge | **git** | history, review, permanence |
-| evidence cited by a finding — a screenshot, a frame, a savegame | **`docs/re/captures/`, present but NEVER committed** | it is the proof, but it is game content. The directory is gitignored and shared between the host and both agents, so all three see the same file; `tools/re/check-capture-citations` fails if a citation has no file, and fails again if an asset is tracked |
-| a measurement you derived — csv, tsv, txt, log, json | **git** | our own numbers, not game content, and most findings rest on them |
-| evidence that must cross machines | **attached to the issue or PR** | captures are local-only now, so a bare clone has none of them. Attaching is the only channel that reaches the other desktop or a reviewer |
+| evidence cited by a finding | **git** | it is the proof |
 | **evidence a human must look at** — the screenshot or film behind a `state/needs-human` item | **attached to that issue** | it travels *with* the item, a person sees it in a browser, and it cannot be orphaned from the claim it supports |
 | exploratory captures, work in progress, "look at this" | **`share`** → `/exchange` | no history; would bloat the repo forever |
 
-⚠️ **This table's first row used to say "git", and that is how 76 MB of
-screenshots accumulated** — directly above the rule forbidding exactly that. The
-two contradicted each other for months and the table won, because it was the one
-that told you what to *do*. Issue #49 settled it and the history was rewritten;
-if you find yourself reaching for `git add -f` on a capture, the answer is no.
-
 🔴 **Never commit game content.** Not sprites, not audio, not transcoded video,
 not a capture of the running game — under *any* directory name. On 2026-09-04
 this rule was live, and freshly tightened, while **545 MB of extracted disc

tools/re/check-capture-citations

@@ -235,21 +235,6 @@ def main() -> int:
     print("  cited by a page or a tool : %d" % (len(files) - len(orphans)))
     print("  cited by nothing          : %d  (reported, not failed —" % len(orphans))
     print("                               an orphan may be evidence a page owes)")
-    # 🔴 A BARE CLONE HAS NO CAPTURES AT ALL, and that is not a defect.
-    # Since #49 the assets are never committed, so a fresh clone, a worktree or
-    # a CI checkout legitimately has none — and the naive check calls all 134
-    # citations dangling and exits 1. A gate that is red on every clean checkout
-    # is one people learn to ignore, which is how the last wrong-by-default
-    # check in this file cost a session. Distinguish "none here" from "this one
-    # is missing": with some assets present, a gap is real and still fails.
-    assets_here = sum(1 for f in files if f.lower().endswith(ASSET_SUFFIXES))
-    if assets_here == 0 and dangling:
-        print("  ⓘ no captures on this checkout: %d citations unresolved" % len(dangling))
-        print("     Expected — captures are local-only (#49) and a fresh clone has none.")
-        print("     Copy them in, or read the evidence on the issue it is attached to.")
-        print("  🔴 game assets TRACKED    : %d" % len(stowaways))
-        return 1 if stowaways else 0
-
     rc = 0
     if dangling:
         print("  🔴 cited but NOT present  : %d" % len(dangling))