Release · Cut & publish Phosphor 0.7.0 — trace pipeline

[wow-miley]

Suggested model tier: human-driven; agent assist only for changelog drafting

Context

AMPERE-first sequencing: Socket integrates against a published, immutable Phosphor artifact, never a snapshot. This release carries the trace pipeline (:phosphor-trace, :phosphor-workbench excluded from publication, FrameProbe).

Version note: #66 (0.6.0, morphology renderer) is still in Backlog. If 0.6.0 ships first, this is 0.7.0; if the trace pipeline lands first, renumber accordingly — do not block on #66, just keep semver honest.

Objective

Cut and publish the Phosphor release containing the trace pipeline.

Checklist

• T1 · :phosphor-trace module — VoxelTrace format, TraceSegment, versioned codec #71, T2 · Oscilloscope — deterministic headless capture of VoxelFrame streams #72, T3 · TracePlayer + sealed LumosSource — replay traces behind the existing render path #73, T5 · TraceStateMachine — segment looping, transition policies, pop-free state switching #75 merged and green (T4 · Workbench — Compose Desktop tuning studio, recording & prototype-parity sign-off #74 Workbench merged but excluded from published artifacts — verify publication config).
• FrameProbe (T0 · FrameProbe — build/project/draw phase timing + baseline capture #70) merged.
• Golden equivalence test (T3 · TracePlayer + sealed LumosSource — replay traces behind the existing render path #73 Task C) green on the release commit — this is the release's keystone check.
• CHANGELOG entry: new :phosphor-trace module, VoxelTrace format v1, Oscilloscope, TracePlayer, LumosSource, TraceStateMachine, FrameProbe; explicit note that format v1 may gain delta/quantization in v2 behind the version field.
• Version bumped, tagged, published to the artifact repository; Socket can resolve it.
• Verify :phosphor-trace has no Compose dependency in the published POM.

Validation / DoD

A clean consumer project resolves the new version and round-trips a .vxt file using only published artifacts.

Out of scope

Any code changes — if something's broken at release time, it goes back to its ticket. Closing this ticket with known-red checks is the #67 anti-pattern; don't.