Parent: #498 Related: #1048, #1050, #1051, #493
Measured problem
An executed VM counter witness confirms that three semantically ordinary Array stores—appending index 0, filling a hole, and growing a nearby dense gap—produce correct results while the dense-store quick-path counter remains unchanged in both isolated and shared dispatch modes. They fall through to generic [[Set]] even though the interpreter already owns a guarded, prototype-aware dense creation primitive.
Scope
- Reuse the existing guarded Array dense-index mutation primitive from VM
set_index. - Cover append, hole fill, and bounded nearby dense growth for primitive Number and canonical String array-index keys.
- Preserve Array length, holes, extensibility, non-writable length/index descriptors, inherited setters/non-writable indexed data, Proxies, accessors, restriction ownership, and shared synchronization.
- Leave distant sparse-property creation and observable/generic key coercion on ordinary
[[Set]]. - Add a dedicated hit counter and update the source-derived quickening inventory and generated architecture page.
Acceptance
- The pre-change zero-hit witness records positive dense-creation hits with identical Node results.
- Append, hole fill, bounded gap growth, and canonical String keys are pinned in isolated and shared modes.
- Prototype interceptors, descriptors, non-extensible Arrays, Proxies, sparse creation, and object/non-canonical keys stay generic.
- Restriction ownership and unsuppressed TSan coverage pass.
- Quickening inventory, benchmark-validator, docs-manifest, and offline-link gates pass.