SwanSong 0.7.1 — Follow the Evidence

SwanSong 0.7.1 — Translation Lab Finds the Real Source

SwanSong 0.7.1 turns one of Translation Lab’s hardest questions—“where did
these pixels actually come from?”—into a guarded, replayable workflow. Point
at a visible rectangle, choose the part you care about, and SwanSong can follow
the evidence back through the exact captured frame while keeping private game
details inside your project.

Expected app identity: SwanSong 0.7.1 (14).

The short version

• Source probing now runs through SwanSong’s installed, signed helper chain.
• Each probe is tied to the exact project, ROM, plan, frame, rectangle, and
  engine that produced it.
• CPU and DMA reads keep honest private provenance instead of filling gaps with
  guesses.
• Capture Intake handles mixed-case names consistently from command to receipt.
• SwanSong’s runtime and local tools are release-checked to stay away from the
  login Keychain, so ordinary use does not summon a password dialog.

Select a rectangle. Follow the evidence.

Translation Lab can isolate map, raster, palette, or sprite ownership for a
small native rectangle. It still discovers other display elements that share
the same source, which makes it much easier to change a title, heading, or
menu label without accidentally disturbing something elsewhere.

The detailed lineage stays in the linked private project. Local automation
receives only safe summaries: counts, hashes, geometry, status, and explicit
completeness. Cartridge ranges, mapper state, source bytes, addresses, and
executed-read details never leave through MCP.

Proof tied to the frame you actually captured

Commercial probes no longer depend on coordinates from one game. SwanSong
derives the frame, rectangle, orientation, and selected components from the
authenticated Original capture, then requires the capture, authorization,
plan, ROM, project, engine, runner, and replayed frame to agree.

If the frame is wrong, the probe stops before asking the engine a source
question. If the request is too large, altered, incomplete, or missing its
reader context, it stops without producing a finished evidence closure.

A signed path from helper to evidence

The installed MCP helper can launch only the SwanSongRouteRunner beside it
inside the app. The completed evidence binds that helper, the runner, and the
loaded engine. SwanSong writes the final closure last, reads it back, validates
the completed tree, and returns only the authorized public report.

The release gate exercises this through the actual bundled helper after code
signature verification and before notarization. It covers successful and
blocked lineage, exact size limits, wrong frames, altered inputs and
executables, missing CPU or DMA context, private-field leakage, and final-tree
closure.

No surprise password box

Homebrew Catalog anti-rollback state lives in a locked, owner-only file—not a
login-Keychain item. SwanSong 0.7.1 also adds a release-blocking check that
rejects Keychain item APIs or the retired catalog trust service anywhere in
the shipped runtime. Non-interactive local tools must explicitly disable
SwiftPM Keychain lookup as well.

Install or update

Existing users can choose SwanSong > Check for Updates…. A manual install
can download SwanSong-0.7.1-macOS-universal.zip from the GitHub Release and
verify it with SHA256SUMS.txt and SwanSong-0.7.1-release.json.

SwanSong requires macOS 14 or newer. It includes no games or original system
firmware. Use only software and hardware you own or are authorized to use.

If anything feels wrong, open Help > SwanSong Support and create a
privacy-safe Support Bundle. The support guide,
privacy policy, and complete changelog
have the deeper details.