# Allocator capacity retry and native registration request

RE-606. Reproduce with `python3 scripts/analyze_qvm_entity_allocate.py`; check with `python3 scripts/test_qvm_entity_allocate.py`. The [machine report](qvm-entity-allocate.json) retains source identity and bounded fixtures.

The bounded driver interprets actual277166–277344, dispatches actual277125 and captures native−16 without engine effects. It allows enough instructions for two scans of960 slots and rejects unexpected calls. Exhaustion at index1024 increments retry and repeats once; pass1 ignores the recent-free delay. All-in-use count1024 increments count to1025 and stops before fatal2319. Exhaustion at1022 instead stops before the1024-entry2294 diagnostic loop. These asymmetric literal limits are evidence, not corrected assumptions. Count1023 can extend to1024, request−16(pool,count,880,clientBase,6336), initialize and return the final legal slot. No clearing occurs. The unusual1022 diagnostic path and whether2319 ever returns require native/reference confirmation. Reports omit enormous pool dumps but retain complete selected records and trace hashes.

No original executable/full QVM/native collision/physics/rendering executes. Native responses and legal input domains are supplied or unverified where stated; full runtime/macOS/Linux Rust/Bevy/Solari gameplay remains open.