26c3d304e9
`the_derived_order_puts_primitives_last_and_that_wipes_screens` asserted that switching primitives on still flattened at least one screen (`wiped_on > 0`), and said to turn `include_primitives` on by default the day it stopped. `cfcda55` made that day arrive — a keyless primitive that would hide the screen is now forced to paint first — and the wire had been red since 2026-08-29, invisible to CI because the runner has no corpus and the suite self-skips. #38 chose option A: keep the default off, and pin the fix instead. The flatness proxy stood in for "paint order is solved", and the fix's own record says that is only partly true — "This does **not** make `include_primitives` safe by default" (docs/re/structures/ui-prm-primitives.md). So: * renamed to `no_build_is_wiped_with_primitives_on` — the old name asserted the bug; it survives in the doc comment for anyone searching from #38; * `wiped_on > 0` -> `assert_eq!(wiped_on, 0)`, with a message saying what a failure now means (`forced_backdrop` regressed) and that it must not be "fixed" by turning primitives off in the test; * `include_primitives` stays `false`; no library code changes. It is the only end-to-end check of the rule: the four tests in `ui_forced_backdrop_disc.rs` pin its mechanics, and none composes with primitives on. Verified with the corpus present, including that it can fail: fix 3 passed 125 builds draw a primitive, 0 wiped forced_backdrop disabled FAILED 36 of 125 wiped — the new message fired restored 3 passed 125 builds, 0 wiped The control's 36 is exactly the "36 builds ... wiped by our own sort" that `cfcda55` and `ui-forced-backdrop.md` report — the guard independently reproduces the fix's own number, so it measures precisely what was repaired. The control was a one-line `return false;` in a scratch copy; the working tree was restored and `git diff` showed only this test file before committing. Closes #38 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sylpheed
A clean-room reverse engineering and port project for Project Sylpheed: Arc of Deception (Xbox 360, 2007).
Three things live here, in one repository so that a change spanning them lands as one commit:
| The decoders | crates/sylpheed-formats — the disc's formats, read and verified disc-wide |
| The port | port/ — a Godot 4 project, plus crates/sylpheed-export which converts a disc into the open asset tree it reads |
| The corpus | docs/re/ — what has been reverse engineered, with its evidence, its retractions and its dead ends |
You need your own copy of the game. No game content is in this repository and none ever will be. The exporter reads the disc you supply.
The oracle is the real game
sylpheed-cliand the Explorer are tools for verifying our decoding. They are hypotheses under test and they have been wrong. When something must be checked against the truth, the truth is the game running in Xenia Canary, captured — not any renderer of ours.
This is stated first because getting it backwards is the most expensive mistake this project has made.
Layout
crates/
sylpheed-formats/ the decoders. Disc-wide verified; the corpus is its spec
sylpheed-cli/ headless tools -- render a screen, dump a table, probe audio
sylpheed-viewer/ the Explorer: a human's window onto the disc. STATIC data only
sylpheed-export/ disc -> the open, moddable asset tree
port/ the Godot 4 project. Reads open formats ONLY
authored/ decisions that are NOT on the disc, each with its reason
data/
base/ generated by the exporter. Gitignored, never hand-edited
mods/ drop-in overrides. Yours
docs/
re/ the corpus: findings, refutations, method traps
game/ how the game is navigated -- menus, modals, flight
port/ the port's mission, its handoff contract, modding rules
-- and RUNNING.md, which is how you actually start it
agents/ how the agent team works together
tools/ capture harnesses, probes, the share tool
exchange/ transient inter-agent files. NOT in git
docker/ the agent containers
Where to start
docs/re/INDEX.md— what is decodeddocs/re/REFUTED.md— what has been tested and dieddocs/re/METHOD.md— traps this project has already paid fordocs/game/navigation.md— how the game is navigateddocs/port/MODDING.md— why the asset tree looks the way it does
Xenia Canary is a separate repository: it is a fork tracking upstream, and it carries our instrumentation.
Conventions
Confidence is per claim, never per document: ✅ CONFIRMED · 🟡 PROBABLE ·
❔ HYPOTHESIS · ❌ REFUTED. A withdrawn result is kept with its reasoning
rather than deleted — that is why the numbers here can be trusted.