fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

chore: hand the workspace over — the gated launchers, and the state of play #55

Merged
fabi merged 1 commits from chore/handoff-2026-09-18 into main 2026-09-19 18:48:08 +00:00
Conversation 0 Commits 1 Files Changed 9 +580
fabi commented 2026-09-18 05:18:02 +00:00
Owner
Copy Link

Work resumes on the original machine, so this brings into the repo everything that lived only in this workspace, and writes down the rest.

The gated launchers (tools/)

run-canary-safe.sh (Wine) and run-canary-native-safe.sh (native) are the only sanctioned way to start Canary from the editor: both force software Vulkan and refuse to launch while a hardware Vulkan device is visible, because Canary on the AMD GPU takes VS Code down with it. They sat in the workspace root, outside git, hardcoding one machine's absolute paths — which is why they were never checked in.

They now derive the workspace from their own location and honour $SYLPHEED_ISO / $CANARY_BIN, so the layout is a default and not a requirement. run-canary-native.sh (interactive, hardware Vulkan, not from the IDE), diagnose-freeze.sh, live-guest-state.sh, heaptrack-wrap.sh and the asound-null.conf the native launcher needs beside it come along.

Run from tools/ before committing, rather than argued from the diff:

launcher result
tools/run-canary-native-safe.sh 20 pre-flight OK (llvmpipe only), title=1 xma=25398 faults=0 guest_throw=0 → VERDICT: HEALTHY
tools/run-canary-safe.sh "" 25 pre-flight OK, rc=124 (the timeout), ADV.wmv=4, 3.9 MB log

The dead run-canary.sh in the workspace root is not brought over: it pointed at xenia-rs/sylpheed.iso and a path spelled without the dash. tools/run-canary.sh already replaced it.

docs/agents/HANDOFF-2026-09-18.md

State of play, what changed since 2026-09-16 (consolidation closed, the recovery branches, the tracker cleanup, the corpus control, the toolchain pin), what cannot travel through git — agent memory, CLAUDE.md, .claude/, .env, game data, the token, the Canary builds — and the traps this machine paid for. The sharpest one: the guest-PC branch probe exists only on the fork's snapshot branch, so rebuilding Canary from sylpheed-re silently loses the project's main dynamic-RE instrument (fork #1).

HANDOFF-2026-09-06.md gets a correction note appended rather than an edit — a plain clone works again now that the 545 MB branch is gone, and its baselines are two baselines old.

Not in this PR

#53 and #54 are still open and still want a human. Nothing here depends on them.

🤖 Generated with Claude Code

Work resumes on the original machine, so this brings into the repo everything that lived only in this workspace, and writes down the rest. ### The gated launchers (`tools/`) `run-canary-safe.sh` (Wine) and `run-canary-native-safe.sh` (native) are the only sanctioned way to start Canary from the editor: both force software Vulkan and **refuse to launch while a hardware Vulkan device is visible**, because Canary on the AMD GPU takes VS Code down with it. They sat in the workspace root, outside git, hardcoding one machine's absolute paths — which is why they were never checked in. They now derive the workspace from their own location and honour `$SYLPHEED_ISO` / `$CANARY_BIN`, so the layout is a default and not a requirement. `run-canary-native.sh` (interactive, hardware Vulkan, not from the IDE), `diagnose-freeze.sh`, `live-guest-state.sh`, `heaptrack-wrap.sh` and the `asound-null.conf` the native launcher needs beside it come along. **Run from `tools/` before committing**, rather than argued from the diff: | launcher | result | |---|---| | `tools/run-canary-native-safe.sh 20` | pre-flight OK (llvmpipe only), `title=1 xma=25398 faults=0 guest_throw=0` → `VERDICT: HEALTHY` | | `tools/run-canary-safe.sh "" 25` | pre-flight OK, `rc=124` (the timeout), `ADV.wmv=4`, 3.9 MB log | The dead `run-canary.sh` in the workspace root is not brought over: it pointed at `xenia-rs/sylpheed.iso` and a path spelled without the dash. `tools/run-canary.sh` already replaced it. ### `docs/agents/HANDOFF-2026-09-18.md` State of play, what changed since 2026-09-16 (consolidation closed, the recovery branches, the tracker cleanup, the corpus control, the toolchain pin), **what cannot travel through git** — agent memory, `CLAUDE.md`, `.claude/`, `.env`, game data, the token, the Canary builds — and the traps this machine paid for. The sharpest one: the guest-PC branch probe exists only on the fork's snapshot branch, so rebuilding Canary from `sylpheed-re` silently loses the project's main dynamic-RE instrument (fork #1). `HANDOFF-2026-09-06.md` gets a correction note appended rather than an edit — a plain clone works again now that the 545 MB branch is gone, and its baselines are two baselines old. ### Not in this PR #53 and #54 are still open and still want a human. Nothing here depends on them. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fabi added 1 commit 2026-09-18 05:18:02 +00:00
chore: hand the workspace over — the gated launchers, and the state of play
All checks were successful
CI / Native — linux (pull_request) Successful in 2h16m47s
Details
CI / WASM — Web (pull_request) Successful in 31m15s
Details
CI / Formatting (pull_request) Successful in 1m19s
Details
94f84b1356 
Resuming happens on the other machine, so anything that lived only in this
workspace either comes into the repo or gets named as something to carry.

**The launchers come in.** `run-canary-safe.sh` (Wine) and
`run-canary-native-safe.sh` (native) are the ONLY sanctioned way to start Canary
from the editor — they force software Vulkan and refuse to launch while a
hardware Vulkan device is visible, because Canary on the AMD GPU takes VS Code
with it. They sat in the workspace root, outside git, hardcoding one machine's
absolute paths, which is exactly why they could not be checked in. They now
derive the workspace from their own location and honour `$SYLPHEED_ISO` and
`$CANARY_BIN`, so the layout is a default rather than a requirement. Same for
`run-canary-native.sh` (interactive, hardware Vulkan — not from the IDE),
`diagnose-freeze.sh`, `live-guest-state.sh`, `heaptrack-wrap.sh` and the
`asound-null.conf` the native launcher needs beside it.

Both safe launchers were run from `tools/` before this commit: the native one
reached content in 20 s (`VERDICT: HEALTHY`, title + 25,398 XMA lines, no
faults), the Wine one ran 25 s and logged 4 `ADV.wmv` hits.

**`docs/agents/HANDOFF-2026-09-18.md`** records what changed since 2026-09-16,
what is on the server, what cannot travel through git, and the traps this machine
paid for — chiefly that the guest-PC branch probe exists only on the fork's
snapshot branch, so a rebuild from `sylpheed-re` silently loses it.

**`HANDOFF-2026-09-06.md`** gets a correction note rather than an edit: a plain
clone works again now that the 545 MB branch is gone, and its baselines are two
baselines old.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
fabi merged commit 9031b553c3 into main 2026-09-19 18:48:08 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
agent/decoder
Owned by the Decoder (disc to meaning; runs the emulator)
 agent/port
Owned by the Port (disc to playable; no RE)
 kind/ask
One agent asking the other for something it cannot answer in role
 kind/bundle
A bundle the human defined; agents decompose it into items
 kind/defect
Found by a play-test or a check
 kind/item
One unit of work, small enough to finish in a single session
 state/approved
Human approved the shape; an agent may start
 state/blocked
Waiting on another item; use the Depends-On field, not prose
 state/in-progress
An agent is working it now
 state/needs-human
Done as far as an agent can tell -- a person must look. The body says what to look at
 state/proposed
Agent proposed this item; awaiting the human's approval to start
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sylph-decoder sylph-pi sylph-port fabi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fabi/Sylpheed#55
Delete Branch "chore/handoff-2026-09-18"

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?