# NousResearch/hermes-agent · SQLite runtime repair outcome in update receipts

## Open now

- Nothing open on GitHub.

These items concern a bug where the result of SQLite runtime repair during updates was not correctly recorded in receipts, and the associated fix to capture and surface that outcome.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #112229. Verify it addresses your case.
- **Recommended:** read PR #112229 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-112229`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #111497: Update receipts never carry the SQLite runtime repair outcome: a failed repair records only 'partially complete'

## Prior & competing PRs

- **#112229: fix(update): SQLite runtime repair completes on uv 0.11–0.12.9 installs and its outcome reaches the console and receipt (#111417, #111497, salvage #111419, #111521)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/[redacted:email]`, `hermes_cli/managed_uv.py`, `tests/hermes_cli/test_managed_uv.py`, `tests/hermes_cli/test_runtime_repair_receipt.py`, `website/docs/getting-started/updating.md`
- **#111521: fix(update): record SQLite runtime repair outcomes in receipts**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `e2fb6cc765`, `#112229`

## Fix status

- Merged to main in PR #112229 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.