Audit found the helper's platform tags hardcoded in four release paths rather than imported from solstone/think/probe.py, where criterion 5 requires them to be declared exactly once. The drift this prevents is concrete: if the measured floor moves and probe.py is updated, a literal selector keeps matching the OLD filename. The release path then silently selects nothing, or the wrong artifact, and proves nothing while reporting success -- the same silent-wrong-answer shape the wheel's own tag discipline exists to prevent. Product selectors now derive from SOLSTONE_CORE_SPEAKERS_ANALYZE_PLATFORM_TAGS: release_install_smoke.py, release_build_host.py, release_candidate_driver.py, and the Makefile's macOS helper lane. The Makefile derives via a $(shell) import, which works precisely because probe.py is stdlib-only and needs no venv. Pre-existing root/core literals are left alone; they predate this lode. Left as literals deliberately, because they are not tag declarations: maturin `--compatibility manylinux_2_27` build arguments and the lane validator's expected token tuples, which are build inputs rather than selectors; and the upstream `onnxruntime-1.25.0-...whl` filenames in the staging script's digest-pinned provenance table, which identify exact third-party bytes. The constants test no longer pins tag literals. Comparing a tag against the string the code just produced passes whether or not the tag is honest. It now asserts the properties that can actually fail: that the dict cannot drift from its derivation function, that the Linux helper tags are NOT equal to the core's (copying them is the specific defect this coverage set exists to prevent, since the core is static musl with no glibc floor), and that the parsed floor is at least the measured 2.27. Both mutations were verified to fail the test before landing. Fixture writers and their selectors derive together, so neither can drift from the other. make ci: 15539 passed, 17 skipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>