release: v0.2.1 — FIX text protocol adapter (#29), perf flamegraph (#32), anchor sweep

AGENTS.md

@@ -1259,6 +1259,10 @@ Issue #90 remains the full hardware-PMU evidence debt (the cache-counter set spe
 #99 and #110 were addressed by PR #111. Issues #95, #28, and #26 were addressed by PR #112. Issue
 #94 is the external technical review request and remains one of the highest remaining credibility
 signals. PR #124 completed M49, PR #125 (d9094df) refreshed the Linux host artifacts on bare-metal
-Fedora Asahi, and `v0.2.0` was released (PR #127 ded6e80; resume-anchor sync PR #128 ae93545). There
-is no active milestone; the highest-value remaining work is non-code and gated on #94 (external
-review) and #90 (full cache-PMU evidence on a PMU-capable microarchitecture).
+Fedora Asahi, and `v0.2.0` was released (PR #127 ded6e80; resume-anchor sync PR #128 ae93545).
+`v0.2.1` then shipped two reprioritized backlog items plus a consistency sweep: a Codex
+resume-anchor/PMU sweep (PR #129), a perf call-graph flamegraph + `make flamegraph` (PR #134,
+superseding the auto-closed #130, closing #32), and the FIX-like text protocol adapter (PR #131,
+closing #29), with the version bump on the release PR. There is no active milestone; the
+highest-value remaining work is non-code and gated on #94 (external review) and #90 (full cache-PMU
+evidence on a PMU-capable microarchitecture).

CHANGELOG.md

@@ -7,6 +7,41 @@ All notable changes to this project. The format is loosely based on
 
 _Nothing yet._
 
+## [0.2.1] - 2026-06-21
+
+Two backlog items — reprioritized by the maintainer and delivered — plus a resume-anchor and
+perf-evidence consistency sweep. Same honesty bar as prior releases: a deterministic C++20 exchange
+simulator and cross-language differential-testing harness — **not** a production exchange, no
+real-market connectivity, no latency or profitability claims, and not formal verification.
+
+### Added
+
+- **FIX-like text protocol adapter (#29).** A human-readable `tag=value` (SOH-framed) codec
+  (`include/qsl/protocol/fix.hpp`, `src/protocol/fix.cpp`) over the **same internal message structs**
+  as the binary codec, with genuine FIX framing — BeginString (8) / BodyLength (9) / MsgType (35) /
+  … / mod-256 CheckSum (10) — for the client→gateway order path: NewOrderSingle (`35=D`) → `NewOrder`
+  and OrderCancelRequest (`35=F`) → `CancelOrder`. Decoding is total, deterministic, and `noexcept`
+  (fixed field table, `std::from_chars`, `std::string_view`; no heap on the decode path) and reports
+  every malformed input through a `FixError` taxonomy mirroring the binary codec's `DecodeError`.
+  Covered by `tests/unit/test_fix_protocol.cpp`, including a **cross-codec equivalence** test (binary
+  and FIX decode the same order to identical structs) and a byte-pinned fixture; documented in
+  `docs/fix_protocol.md`. Prices stay integer ticks and Symbol carries the numeric `SymbolId`
+  (documented simplifications, never floating-point price).
+- **`make flamegraph` (#32).** Renders a Linux `perf` call-graph flamegraph
+  (`results/flamegraph.svg` + a provenance/classification `results/flamegraph.txt`) from the
+  benchmark harness via `scripts/flamegraph.py` — a dependency-free (stdlib-only) stackcollapse + SVG
+  renderer (deterministic; unit-tested in `tests/shell/test_flamegraph.sh`), so the artifact is
+  reproducible from the repo without vendoring the Perl FlameGraph toolkit. The committed artifact is
+  a software cpu-clock sampling **hot-symbol profile** from the bare-metal Fedora Asahi host — not a
+  latency/throughput claim; full hardware cache-PMU evidence stays in issue #90.
+
+### Changed
+
+- Synced the `/resume` anchors and perf-evidence wording to the released `v0.2.0` state and narrowed
+  an overstated Apple **Blizzard** (E-core) PMU claim — those rows read `<not counted>` because the
+  single-threaded benchmark stays on the Avalanche P-cores (Codex follow-up to PRs #127/#128):
+  `PROGRESS.md`, `AGENTS.md`/`CLAUDE.md` agreement, and `docs/perf_analysis.md`.
+
 ## [0.2.0] - 2026-06-21
 
 Quant Systems Lab v0.2.0 — the Phase III/IV systems arc (M24–M49: a bounded SPSC queue and threaded

CLAUDE.md

@@ -1203,6 +1203,10 @@ Issue #90 remains the full hardware-PMU evidence debt (the cache-counter set spe
 #99 and #110 were addressed by PR #111. Issues #95, #28, and #26 were addressed by PR #112. Issue
 #94 is the external technical review request and remains one of the highest remaining credibility
 signals. PR #124 completed M49, PR #125 (d9094df) refreshed the Linux host artifacts on bare-metal
-Fedora Asahi, and `v0.2.0` was released (PR #127 ded6e80; resume-anchor sync PR #128 ae93545). There
-is no active milestone; the highest-value remaining work is non-code and gated on #94 (external
-review) and #90 (full cache-PMU evidence on a PMU-capable microarchitecture).
+Fedora Asahi, and `v0.2.0` was released (PR #127 ded6e80; resume-anchor sync PR #128 ae93545).
+`v0.2.1` then shipped two reprioritized backlog items plus a consistency sweep: a Codex
+resume-anchor/PMU sweep (PR #129), a perf call-graph flamegraph + `make flamegraph` (PR #134,
+superseding the auto-closed #130, closing #32), and the FIX-like text protocol adapter (PR #131,
+closing #29), with the version bump on the release PR. There is no active milestone; the
+highest-value remaining work is non-code and gated on #94 (external review) and #90 (full cache-PMU
+evidence on a PMU-capable microarchitecture).

CMakeLists.txt

@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.24)
-project(quant-systems-lab VERSION 0.2.0 LANGUAGES CXX)
+project(quant-systems-lab VERSION 0.2.1 LANGUAGES CXX)
 
 set(CMAKE_CXX_STANDARD 20)
 set(CMAKE_CXX_STANDARD_REQUIRED ON)

HANDOFF.md

@@ -16,7 +16,8 @@ command lists, roadmap state, non-overclaiming rules, and benchmark rules.
 ---
 ## Current handoff
 
-The repo is released at `v0.2.0` (tag on ded6e80, marked Latest), after `v0.1.0`. M0–M49 are
+The repo's current release is `v0.2.1` (tagged on the release-PR merge commit, marked Latest), after
+`v0.2.0` (ded6e80) and `v0.1.0`. M0–M49 are
 merged. PR #101 (40f9249) and PR #102 (7092423)
 synchronized project-memory files after M35. PR #103 (0f2ceb7) inserted the repository-health
 refactor phase **M36–M42** and shifted the original networking/persistence roadmap after those
@@ -28,8 +29,12 @@ refactors. PR #113 extended the future roadmap to **M43–M49**. M36–M42 lande
 PR #123 (c643b62), and PR #124 (d8c16b2), with M45B provenance migration in PR #116 (b9ea27a) and
 the M47 storage diagnosis follow-up in PR #122 (548cb68). The Linux host artifact refresh landed as
 PR #125 (d9094df), and the **v0.2.0 release** — a bare-metal Linux evidence refresh, the
-partial-PMU reframe, and a full documentation staleness sweep — landed as PR #127 (ded6e80). There
-is no active milestone; the project is between releases.
+partial-PMU reframe, and a full documentation staleness sweep — landed as PR #127 (ded6e80). The
+**v0.2.1 release** then adds two reprioritized backlog items and a consistency sweep: a Codex
+resume-anchor/PMU sweep (PR #129), a perf call-graph flamegraph + `make flamegraph` (PR #130,
+issue #32), the FIX-like text protocol adapter (PR #131, issue #29), and the version-bump release
+PR — merged in that order, with `v0.2.1` tagged on the release merge commit. There is no active
+milestone; the project is between releases.
 
 Background — Linux perf evidence (merged, now bare-metal partial PMU):
 
@@ -65,33 +70,36 @@ git pull --ff-only
 git log --oneline -10
 gh pr list --state open
 git tag -l
-gh release view v0.2.0
+gh release view v0.2.1
 ```
 
 Current state:
 
-- latest synced main baseline: `ded6e80` (PR #127, v0.2.0 release)
+- latest synced main baseline: `ded6e80` (PR #127, v0.2.0); the `v0.2.1` baseline is the release-PR
+  merge commit, after PRs #129/#130/#131
 - current active branch, if active: none (work lands via scoped PRs from `main`)
-- current active status: `v0.2.0` released. The bare-metal Linux evidence refresh, the
-  partial-PMU reframe (real Apple PMU counters; cache counters unsupported), and a full
-  documentation staleness sweep are merged. All 15 `results/*.txt` are bare-metal with
-  `Dirty inputs: no` and no MAC leaks; `make check` 241/241 and `make asan` 241/241; README and
-  recruiting benchmark numbers match `results/latest.txt`. No active milestone
-- release tag: `v0.2.0` (Latest), after `v0.1.0`
+- current active status: `v0.2.1` is the current release on top of `v0.2.0`. It adds the FIX-like
+  text protocol adapter (#29), `make flamegraph` + a bare-metal flamegraph artifact (#32), and a
+  Codex resume-anchor/PMU consistency sweep. `make check` 263/263 and `make asan` 263/263 on the
+  bare-metal Apple M2 Fedora Asahi host; both new code files pass the CI CodeScene Code Health gate.
+  No active milestone
+- release tag: `v0.2.1` (Latest, tagged on the release-PR merge commit), after `v0.2.0` and `v0.1.0`
 - open follow-up issue: #90 — narrowed to the full cache-counter PMU set; the bare-metal Apple host
   provides real cycles/instructions/branches/branch-misses but no cache-reference/cache-miss support
-- issues #95, #28, and #26 were closed by PR #112
+- issues #95, #28, and #26 were closed by PR #112; issues #32 and #29 were closed by PR #134 and
+  PR #131 (now part of `v0.2.1`)
 - open review request issue: #94
-- legacy backlog still open: #32 (#29 delivered in this PR, `feat/fix-text-protocol-adapter`)
+- legacy backlog: clear — #32 (flamegraph) and #29 (FIX adapter) shipped in `v0.2.1` (PR #134,
+  PR #131)
 
 ### Next milestone
 
-There is no active milestone. M0–M49, the Linux artifact refresh (PR #125), and the v0.2.0 release
-(PR #127) are merged. The highest-value remaining work is non-code and externally gated: issue #94
-(independent external review — needs a human reviewer) and issue #90 (full cache-counter PMU
-evidence — needs a PMU microarchitecture that exposes cache events). #29 (FIX-like text protocol
-adapter) is delivered in this PR; low-signal backlog: #32 (flamegraph). Do not invent a new
-milestone without an explicit human request.
+There is no active milestone. M0–M49, the Linux artifact refresh (PR #125), the v0.2.0 release
+(PR #127), and the v0.2.1 content (PRs #129/#134/#131 + release PR) are merged. The highest-value
+remaining work is non-code and externally gated: issue #94 (independent external review — needs a
+human reviewer) and issue #90 (full cache-counter PMU evidence — needs a PMU microarchitecture that
+exposes cache events). The #32 (flamegraph) and #29 (FIX adapter) backlog items are now done. Do not
+invent a new milestone without an explicit human request.
 
 ### Phase III / IV purpose
 
@@ -101,15 +109,14 @@ studies, advanced concurrency validation, event-driven gateway architecture, mul
 pressure, NUMA/affinity and scheduler-migration studies, ingress memory ordering and false-sharing
 evidence, persistence/recovery benchmarking, and late-stage low-latency networking research.
 
-Current priority order (post-v0.2.0):
+Current priority order (post-v0.2.1):
 
 1. Issue #94 — independent external technical review remains the single highest credibility gap
    (human-gated; cannot be self-certified).
 2. Issue #90 — full cache-counter PMU evidence. The bare-metal Apple host gives real
    cycles/instructions/branches/branch-misses but no cache-reference/cache-miss counters, so this
    needs a PMU microarchitecture that exposes cache events (x86_64, or an ARM server core).
-3. Low-signal backlog only after the above: #32 (flamegraph). #29 (FIX adapter) is delivered in
-   this PR (`feat/fix-text-protocol-adapter`).
+3. No low-signal backlog remains: #32 (flamegraph) and #29 (FIX adapter) shipped in `v0.2.1`.
 
 ### Forbidden shortcuts