native-proof: case 17's crash-adoption status read refuses a changing pool under load

Open Beginner friendly
#4,047 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start at scripts/native-proof/reference-pool.native.ts:579, the case 17 poolStatus read expecting REFERENCE_ACCESS_CRASH_RECONCILED, and copy the bounded retry that #3236 added for case 18 so only the transient changing code is retried a fixed number of times. Read the case-18 block first to see the existing pattern, then run bun scripts/prove-reference-pool.ts to confirm. Done means ten loaded runs pass and an injected non-changing refusal still fails immediately.

Written by the indexing model from the issue text.

Description

agent-ready area: ci area: ui-sdk priority: p2 type: test

Context

Native case 17 of the reference pool proof restarts the manager after a simulated interrupted grant, then expects the next poolStatus to be qualified (REFERENCE_ACCESS_CRASH_RECONCILED, scripts/native-proof/reference-pool.native.ts:590). Under parallel host load, that read was refused because the pool was still changing:

error: REFERENCE_ACCESS_CRASH_RECONCILED
Received: { code: "changing", message: "Reference pool allocation changed between consistent reads; retry once writers settle." }

This happened in 1 of 6 loaded clean runs in draft heavy feedback run 43756278174, job 132945961843 (PR #4040 head f77a2dde7e9df4777ae317cd573813884a50cd88). Load came from a temporary #2819 receipt driver: two niced CPU spinners and a continuous 256 MiB dd ... conv=fsync writer. Earlier releases in the same proof can still be reclaimed in the background, which is the same cause as #2819 and the case-18 instance #3236. The changing refusal is transient and correct, and nothing in the pool was wrong.

Scope

Make this one status read in case 17 tolerate only the exact transient changing refusal, within a fixed finite bound, in the same bounded way #3236 settled for case 18. Every other refusal still fails at once.

Out of scope

Pool accounting, the changing refusal itself, and every other assertion and case.

Acceptance criteria

  1. Under the same parallel load, ten consecutive native runs pass REFERENCE_ACCESS_CRASH_RECONCILED.
  2. An injected non-changing refusal at that read still fails REFERENCE_ACCESS_CRASH_RECONCILED immediately (mutation receipt).

Verification

bun scripts/prove-reference-pool.ts repeated under load on hosted heavy feedback, plus the mutation receipt.

Contract impact

None.

2026-11-16 triage at main 3b104890f8: Verified the named crash-reconciliation assertion and moved its pointer to :590. The observed exact changing refusal and scoped #3236 precedent settle what may be awaited; choose and record one finite bound without changing production accounting or hiding any other refusal. Keep the loaded ten-run proof and immediate non-changing-refusal mutation. Wanted unscheduled proof repair is p2, with no release commitment. Leave standalone: #736 is at 100 direct children, and the browser/assertion-quality epics do not own this native status-settling outcome.

Dominant language
TypeScript
Stars
4
Forks
0
Avg merge
6h 5m
Merged PRs (30d)
730

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from schlessera/brain-kit

All issues in schlessera/brain-kit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.