[wchwawa]

Related Issue

No issue: this is a release chore, which the template exempts. It ships the fix in #555 for a client defect that #552 introduced in 0.12.0.

Summary

• Bump crates/nokv and crates/nokv-python to 0.12.1. The same change updates the workspace dependencies on nokv and nokv-python, their Cargo.lock entries, and the build identity test in crates/nokv/src/build_info.rs. Both release workflows require the tag and these versions to agree.
• 0.12.1 ships fix(client): authenticate inline publication receipts; regrade the append gates #555. In 0.12.0, an inline publication that reused an operation id with other inputs returned the earlier publication's receipt as a success, and the new body was not written. An inline publication is one with a body of at most 16 KiB.
• The wire protocol (nokv.workspace.rpc.v14) and the metadata format (System format 14) are unchanged, so 0.12.1 and 0.12.0 interoperate.
• The Python SDK install notes use 0.12.1 and describe the 0.12 releases as a whole.
• docs/development/loopx-stage2a-stack.md still installed the 0.11.1 wheel. The stack script refuses a wheel whose version differs from the owner's, so the example failed next to a 0.12 owner. It now names 0.12.1.

Scope

• This PR changes one logical boundary only (the release identity and its install notes).
• No unrelated refactor, benchmark, metadata model, Holt layout,
  object-store, agent interface, or docs change is mixed in.
• The linked issue describes the user-visible problem, design decision, or
  maintenance task this PR resolves (release chore; see above).
• Any breaking change is intentional and documented (none: the protocol and format are unchanged).
• No compatibility shim, deprecated alias, or forwarding wrapper was added without a removal condition.

Change Size And Review

• I checked GitHub's additions plus deletions for this pull request: +17 / -15 (32 lines).
• If the total is more than 5,000 lines, one core maintainer other than the
  current-head pusher approved the exact current head commit. Not applicable: under 5,000 lines.
• This change is still small enough for a focused review; approval count is
  not being used to justify mixed package or lifecycle boundaries.

Code Contract (Code Changes Only)

• Not applicable; this is a docs/config-only change.

Claims and Evidence

• User-facing documentation distinguishes current, experimental, and
  planned capabilities.
• Security claims do not treat a Workbench root or Agent scope as tenant
  authentication or authorization (no security claims).
• Performance claims state the topology, comparison boundary, cache state,
  run count, and raw-evidence location (no new performance claim).
• Benchmark-only behavior does not alter product semantics.

This PR makes no new performance claim, and 0.12.1 was not re-measured. The fix in #555 changes only what an inline publication does after its request fails; the success path is unchanged. The 0.12.0 release check and its raw data stay in the evidence gist.

Validation

• Command and result: python3 scripts/release/test_python_sdk_release.py (13 tests) and python3 scripts/release/test_homebrew_source_release.py (15 tests) pass.
• Command and result: python_sdk_release.validate_version(repo, "v0.12.1") returns 0.12.1. The Homebrew identities agree:
  • the workspace nokv dependency is 0.12.1;
  • the single nokv entry in Cargo.lock is 0.12.1;
  • the Holt pin =0.8.7 matches the lock.
• Not run (with reason): the Rust test suite locally. CI runs it on this PR. fix(client): authenticate inline publication receipts; regrade the append gates #555 describes its own validation: four regression tests, a live probe, and the three append gates.

Contributor Sign-off

• Every commit in this PR includes a DCO Signed-off-by trailer.