Migrate bench-bsp-le-track2.rkt to current ATMS API (CI unblock)

[kumavis]

Summary

raco pkg install --auto (the CI install step) was failing with:

benchmarks/micro/bench-bsp-le-track2.rkt:47:3: tms-write: unbound identifier

The file targeted the pre-D.5b TMS API (tms-write, tms-cell-value, tms-read, tms-commit) which was removed when the TMS was refactored into the tms-cell struct + atms-write-cell interface.

This PR migrates the benchmark to the current API rather than skipping it (the originally-considered approach in PR #2's commit f3a3ca3). The benchmark stays in the suite and continues to provide pre-Track-2 baseline data on the now-current ATMS API.

Migration shape

Old (deleted)	New
tms-read tcv stack (depth-N walk over per-cell stack)	atms-read-cell a key (walk values list until support ⊆ believed); depth N modeled by atms with N supported values + believed worldview = N-element assumption set
tms-write tcv stack value (push depth-N frame)	atms-write-cell a key value support (O(1) struct-copy); cost dominated by support-set construction (hoisted out of the timed loop, mirroring the old benchmark's structure)
tms-commit tcv aid (promote contingent value to permanent)	No direct analog. Replaced with atms-with-worldview benchmarks (alone, and switch + read) — the closest behavioural shape: changing the believed set so subsequent reads re-resolve

Other helpers (atms-empty, atms-assume, atms-amb, atms-add-nogood, atms-consistent?, set operations, make-prop-network, net-new-cell, net-add-propagator, run-to-quiescence) are unchanged — those names still exist on the post-refactor API.

Verification

• raco make racket/prologos/benchmarks/micro/bench-bsp-le-track2.rkt succeeds on Racket 8.10 (CI uses 8.14)
• Full bench runs end-to-end: 19 timed benchmarks reporting stable results
• Sample from end-to-end run:
  • atms-read-cell depth=1 x100000 median 7.40 ms
  • atms-read-cell depth=10 x100000 median 57.34 ms — confirms the design intuition that read cost scales with depth
  • atms-write-cell depth=10 x50000 median 4.00 ms — write cost is roughly depth-independent, dominated by struct-copy

Why this approach instead of the skip

The earlier-considered fix on PR #2's commit f3a3ca3 adds compile-omit-paths to skip the file. That unblocks CI but loses a useful pre-track baseline. Migrating preserves the data the benchmark was intended to gather, on the API the system actually uses now.

Cross-PR impact

PRs #4, #5, #6, #7, #8, #9, #11, #12 all currently carry the compile-omit-paths skip as a CI-unblock commit. Once this PR lands, those PRs can drop their skip commit (it becomes redundant: the bench works on its own). Strictly merge this first, then rebase the others to drop the duplicate.

Commits

1. 3e03516 — migrate bench file (97 insertions, 33 deletions)

https://claude.ai/code/session_01MbncYJnrvjzhbVWw4xGi5x

[hierophantos]

Thanks for the careful migration. Three things I appreciated: the honest "no direct analog" note for tms-commit (forcing an analog would have produced misleading numbers), the string->symbol correctness fix that the old benchmark was getting away with by accident, and the merge-this-first sequencing call in the PR body — saved us a rebase round. Approving and merging.