Keyring guard hardening, tvly-keyring wrapper and Tavily Research qualification receipt (follow-up to #325) - #329

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

…lly on GPU + MTP) 5x decode at equal F1, now serving (#342)

* li26 results: C2 serving profile selected and recorded, llama-cpp host receipts, served model pin

Record the preregistered local-inference-latest-20260926 comparison as run on
nativestack-5975wx-20260925 (native execution, one run per arm, frozen
protocol; speed and memory are this host's under its load at the time):

- results/: the frozen analyze.py decision (final, C2 selected,
  change_serving_profile; a rerun reproduces it byte for byte), the
  acquisition summary and every window summary and per-arm window record,
  all copied unchanged, plus results.md with the per-arm table, bootstrap
  bounds, why M failed criterion (1), B and X not run, the retained failed
  attempts and the dated operations record.
- experiment.json is now observed: adopt_within_scope for the C2 profile,
  qualified by li26-c2-w3; the acquisition's first refusal
  (state_dir_must_be_owner_only), C2's admission refusal in window 2 and
  M's failed criterion stay in failures_and_skips.
- README: a dated results section below the unchanged frozen text.
- llama-cpp install and use host receipts (catalog_revision 2e77144) with
  qualified models Qwen3.8-27B UD-Q4_K_M 4ca7207 (pass, C2 profile) and
  MiMo-V2.6-Distill-Qwen-9B Q8_0 81baddc (measured, fail); the b11057
  catalog pin is not rebound.
- evidence/receipts/local-inference-c2-serving-switch-20260926.json: the
  production switch, its post-switch checks and the rollback.
- manifests/stack.json: the generation model entry now names the served
  unsloth/Qwen3.8-27B-GGUF UD-Q4_K_M file (revision 4ca7207, sha256
  322e194f...) and the C2 serving profile flags.
- The component evidence matrix is regenerated (llama.cpp alternative:
  receipts_recorded); the li26 test now checks the recorded state and the
  results' no-document-text boundary.

manifests/evidence.json is not changed here: the coordinator registers the
19 files and the switch receipt.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* li26 repair: re-record the llama-cpp use receipt with read-only commands

Review (gpt-6-astra, medium) found that the use receipt's sixth command made
a directory with mktemp inside the checkout, wrote decision.json there
through analyze.py --out and deleted it with rm -rf, contradicting the
receipt's statement that its commands changed no file. Confirmed against the
receipt and scripts/host_receipts.py record, which runs every --cmd in the
checkout.

- The use receipt is re-recorded at catalog_revision 2e77144 (published on
  origin/main). Its first five commands are unchanged. The sixth loads the
  frozen analyze.py under python3 -B, calls its analyze() on the retained
  private state and hashes the decision serialized as main() writes it, all
  in memory. It printed the same two lines as the first recording: final,
  C2 selected, change_serving_profile, and SHA-256 672be297..., the
  committed results/decision.json. A before/after mtime scan of the
  checkout, the private state directory, the systemd user configuration and
  the model and runtime directories showed no change beyond the receipt
  file and the manifests/evidence.json registration that host_receipts.py
  record itself writes (reverted; the coordinator registers). The receipt,
  results.md and the switch receipt say that it replaces the unpublished
  first recording (11:26:21Z).
- Dependent hashes: the switch receipt's post-switch readback now names both
  receipts with their observation times (install 11:26:02Z, use 12:41:06Z)
  and the new nvidia-smi reading, and its provenance carries the new use
  receipt and results.md hashes. experiment.json's results.md artifact hash
  follows results.md.
- test_host_receipt_commands_only_read fails on the first recording
  (command 6: mktemp) and passes on this one. It also ties the sixth
  command's printed hash to the committed decision.json.

The install receipt keeps its recording: neither of its commands creates,
writes or removes a path, and the new test checks both receipts.

Checks, with the registration applied temporarily and then reverted:
validate.py passed; validate_convergence.py --all-recorded 23 valid;
host_receipts.py validate 165 passed; component_matrix.py --check checked;
uv run --no-project --with jsonschema --with pyyaml python -m unittest over
10 modules, 652 tests OK.

manifests/evidence.json is not changed. Re-register experiment.json,
results/results.md, the use receipt, the switch receipt (its receipts[]
claim and limitations too) and the li26 test file.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* li26 receipts: independent reviews; install receipt re-recorded with python3 -B

A separate headless Claude session reviewed both llama-cpp host receipts:
- use receipt: independent_session agree.
- install receipt (first generation): needs_changes. verify-arms ran without -B (a
  possible bytecode write, against its read-only limitation) and limitations[1]
  overstated the recorded source of the MiMo pin. Kept unchanged with that review.
- install receipt -2 (supersedes it): re-recorded from a clean checkout at published
  main 3822178 with python3 -B and the corrected limitations; independent re-review:
  agree. The bytecode caches present predate the recording.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Register the li26 results, receipts and stack correction (hot-file commit)

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Re-register after rebasing onto #329 (hot-file commit)

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

---------

Co-authored-by: Scout <scout@local>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>