fix: separate bounded wait rechecks from productive continuation budget #144
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/wait-accounting-budget"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Separate host-issued bounded status rechecks from the 20 productive follow-up budget. Persist wait claim sequence and charge productive tools before effects; preserve termination details without routine operator-alarm spam. Eight files only; no notification/dedicated-host integration, configuration, deployment or restart.
Exact independent review
Base:
eee4da08eeb3b2f3e671e1c7b11656faedfc65edHead:
4b1c85c5e4c14345cabd6af33f6b82d95dd5cbfeComplete committed patch SHA256:
a129d1b61c9669a51f0c2f5eb1e0a346d5294455d4b40ea9305cf0d9c58534c2— byte-identical to frozen independently reviewed patch. Independent review 7d250b3f found no concrete P0/P1. Frozen original retained unchanged. Existing root review ledger is a different changeset and is not claimed as approval.Verification
Delivery checkout: npm ci --include=dev (prepare/build passed), npm run typecheck passed, focused wait tests 12/12, full suite 801/801. Independent review additionally exercised three adversarial probes. All eight source hashes matched the reviewed candidate before commit. No claim of remote CI success; actual checks and effective branch policy inspected separately before normal merge. Source merge does not activate deployment.