Parent: #498 Related: #1049, #1050, #1051, #1052, #493
Measured problem
The executed sparse-store VM witness confirms that creating the first distant Array index (for example values[1000000] = 7) produces the correct sparse own property and length but leaves the sparse-store quick counter unchanged. Only a later replacement of that property is quickened.
Scope
- Add an exact create-only path for distant primitive Number and canonical String Array indices.
- Publish the named own data property and sparse Array length under the indexed/property/element synchronization contract.
- Recheck exact own accessors/data, attributes, extensibility, dense representation, restriction ownership, and the prototype chain at mutation time.
- Preserve inherited setters/non-writable data, frozen length, own accessors/descriptors, Proxies, object/Symbol/non-canonical keys, strict failure, OOM behavior, and no-GIL safety.
- Add a dedicated hit counter and update the source-derived quickening inventory and generated architecture page.
Acceptance
- The pre-change generic-creation witness records positive sparse-creation hits with identical Node results.
- Multiple distant Number and canonical String creations update Array length and read back exactly.
- Existing sparse data uses the replacement path; exact accessors/descriptors and dense indices are never consumed by creation.
- Prototype interceptors, frozen length, non-extensibility, Proxies, and observable/generic keys stay generic.
- Receiver/prototype restriction ownership and unsuppressed TSan coverage pass.
- Quickening inventory, benchmark-validator, docs-manifest, and offline-link gates pass.