wowbagger 0.1.0-alpha.9 → 0.5.0

package/docs/adapter-contract.md

@@ -1477,7 +1477,7 @@ error registry. It changes only this versioned surface:
 The core capability probe adapter contract version 2 requires is core
 contract version 5. It adds exactly
 `operations.patch: {"supported":true,"write_scope":"single-item","cas_scope":"exact-byte-sha256"}`,
-`operations.work_claim.api_version: 2`, and
+`operations.work_claim.api_version: 3`, and
 `limits.max_item_source_bytes: 8388608` as the first member of
 `limits`.
 Its mutation backend scope is always

package/docs/host-contract.md

@@ -26,10 +26,13 @@ shell: an absolute Node executable, the absolute `wowbagger.js` the package
 installed, an argument array, and `shell: false`. Neither path is discovered by
 searching a global npm directory, and neither is a platform command shim.
 
-Wowbagger requires Node.js 20 or later. The package declares that floor in
+Wowbagger requires Node.js 24 or later. The package declares that floor in
 `engines.node`, and the launch seam exports it as `MINIMUM_NODE_MAJOR` for a
 host that resolves its own runtime instead of reusing the one it is running on.
 
+The supported release matrix is Node 24.20.0. Node 26 is excluded until the
+separate Vitest incompatibility reported by Lee is resolved.
+
 ~~~js
 import { resolveCoreLaunch } from 'wowbagger';
 
@@ -258,6 +261,9 @@ not a fetch URL.
 | `bare-ready-result.json` | bare result | a `ready` success |
 | `ledger-mutation-refusal.json` | ledger-mutation 1 | the legacy-write fence refusals |
 | `report-config-v1.json` | report config 1 | `<ledger>/.wowbagger/report.json` at version 1 |
+| `ledger-repair-request.json` | ledger-repair 1 | the strict `number-repair` request |
+| `ledger-repair-proposal.json` | ledger-repair 1 | the read-only `number-repair-proposal` result |
+| `ledger-repair-response.json` | ledger-repair 1 | every `number-repair-proposal` and `number-repair` response |
 | `report-config-v2.json` | report config 2 | the same file at version 2, which names views |
 
 Every schema fixes its root members exactly and pins the version of its own