[BitmapAsset]

The release PR for probbit 0.14.0 (RELEASING.md step 1). Stacked on #78: this branch starts at #78's head (with main
merged into it), so until #78 merges the diff here shows #78 too; once #78 is on main and this branch is rebased on it, the
diff shrinks to the one bump commit. Draft until #78 is merged.

The bump commit (Release probbit 0.14.0):

• Cargo.toml version and every internal path dependency's version (probbit-cli, -decide, -ir, -core, -persona, the
  probbit-nostd entries) 0.14.0-dev → 0.14.0; Cargo.lock (cargo update --workspace --offline leaves it equal);
  docs/probbit.1 generated by the release build (probbit man);
• npm/package.json 0.14.0; the example tag v0.14.0 in install.sh, install.ps1, action.yml,
  .github/workflows/bench.yml, scripts/bench/test_install_ps1.ps1, scripts/tests/test_install_contract.py;
  docs/CHEATSHEET.md title; the strand header example in docs/persona.md §5.7; CITATION.cff 0.14.0, 2026-10-29;
  REPRODUCE.md and the receipts example name 0.14.0;
• CHANGELOG.md: an empty ## Unreleased above ## 0.14.0 - 2026-10-29, which holds the shaped section as it was, with
  the amplitude register's rounds as a seventh group, "The amplitude register, an optional tier (off by default)": a
  simulated amplitude register, exact, on a CPU; the measured replay, its cost, and one caveat for register strands of
  earlier 0.14.0-dev builds;
• docs/persona.md: engine.schedule and engine.amplify are an optional tier, off by default (engine: {tier: amplitude}
  the opt-in), with the measured replay and cost; RFC 0011 and RFCs 0013–0016 status lines name the release;
• README.md landing page: "The current release is v0.14.0.", the Action tag and version input, "What's new in 0.14.0"
  (the library crate for std and no_std hosts, the expectation cache, the self layer off by default, the optional tier),
  and the no_std row of the surfaces table.

Pre-merge checks (RELEASING.md step 1):

check	result
git grep -n "0.14.0-dev"	8 hits: the 2 recorded fixtures examples/persona/demo/register.strand and thermal.strand (header engine); 6 texts that are not a version: CHANGELOG (the dev-build history bullet; the register caveat), README (the register caveat), docs/embedding.md ×2 (what the -dev suffix means), the engine-version parser's unit test in probbit-cli/src/live.rs
python3 bench/individuality/p0.py check (release build)	653 outputs, 0 differ (629 identical, 24 stderr-warning-only), 8 strands verified
cargo publish --dry-run --workspace --locked	exit 0: probbit-nostd, probbit-core, probbit-ir, probbit-decide, probbit-persona, probbit-cli packaged and verified at 0.14.0 (probbit-wasm: publish = false)
(cd npm && npm pack --dry-run)	probbit@0.14.0, 5 files: LICENSE, README.md, bin/probbit.js, install.js, package.json
cargo test -p probbit-cli --test readme_release --test cli_man (release build)	4 passed, 0 failed; docs/probbit.1 is the release build's probbit man byte for byte; cargo update --workspace --offline leaves Cargo.lock unchanged
REPRODUCE.md thirty-second tier (release build)	two passes identical; MATCH results.tsv, bars.tsv, strands-verify.tsv (the committed sha256s); git status --short tables empty
CI on this head (7db9786)	20/20 (ci 16 + check 4), first attempt; #78's head 7cf5afa: 20/20

Merge with gh pr merge <this PR> --squash --subject "Release probbit 0.14.0 (#<this PR>)", then tag that commit (RELEASING.md
step 2). A declared, replayable self; it does not feel.