runtime/object-model: support primitive receiver boxing and temporary property visibility

[andrewtdiz]

Summary

Primitive property access and writes follow ECMAScript wrapper semantics for number primitives, including visible temporary values only where the spec permits.

Affected Test262 rows

• FFI call c code #215 language/function-code/10.4.3-1-103.js (runtime-fail: Uncaught exception: (5).x == 5)
• GTK4: perry_ui_open_folder_dialog not wired — blocks docs/examples/ui/dialogs/snippets.ts on Linux CI #216 language/function-code/10.4.3-1-104.js (runtime-fail: Uncaught exception: (5).x === 5)
• GTK4: 4 widget overlay/reorder FFIs not wired — blocks docs/examples/ui/layout/snippets.ts on Linux CI #217 language/function-code/10.4.3-1-106.js (runtime-fail: Uncaught exception: typeof (5).x Expected SameValue(«"undefined"», «"number"») to be true)
• GTK4: SplitView FFIs (splitview_create, splitview_add_child) not wired — co-blocks docs/examples/ui/layout/snippets.ts on Linux CI #218 language/function-code/10.4.3-1-105.js (runtime-fail: Uncaught exception: typeof (5).x Expected SameValue(«"undefined"», «"object"») to be true)

Perry actual behavior from report

• 1 x runtime-fail: Uncaught exception: (5).x == 5
• 1 x runtime-fail: Uncaught exception: (5).x === 5
• 1 x runtime-fail: Uncaught exception: typeof (5).x Expected SameValue(«"undefined"», «"number"») to be true
• 1 x runtime-fail: Uncaught exception: typeof (5).x Expected SameValue(«"undefined"», «"object"») to be true

Node / ECMAScript expected behavior

Primitive property access and writes follow ECMAScript wrapper semantics for number primitives, including visible temporary values only where the spec permits.

Likely subsystem

ToObject/primitive wrapper object model

Acceptance criteria

• The (5).x and typeof (5).x rows match Node/Test262.
• Number primitive ToObject behavior remains consistent with Number.prototype access.
• No persistent property is incorrectly stored on primitive values.

Validation

Run the Test262 differential against the affected area and confirm these rows leave the gap report:

scripts/test262_subset.py --root vendor/test262 --dir language/function-code --sample-cap 99999 --report /tmp/FUNC_PRIMITIVE_BOXING.json

This is Perry language/runtime semantics triage, not a Node core API compatibility issue.

[andrewtdiz]

Claiming this as part of the same primitive wrapper/ToObject slice.

Scope: temporary primitive receiver boxing for number primitives and no persistent property storage on primitive values, coordinated with the Object/String wrapper fixes in #3986/#3987.

[andrewtdiz]

Opened draft PR for this cut: #4161

Scope covered here:

• primitive Object(value) / wrapper constructor identity for Number/String/Boolean-family wrappers
• boxed String virtual indices, length, descriptors, keys, and own property names
• temporary primitive receiver boxing for dynamic Number/String/Boolean prototype method calls

The broader Object.assign descriptor/proxy tail remains outside this PR.

[andrewtdiz]

PR #4161 merged on June 3, 2026 with the focused primitive wrapper/ToObject cut for this issue.

Merged scope:

• primitive Object(value) / wrapper constructor identity for Number/String/Boolean-family wrappers
• boxed String virtual indices, length, descriptors, keys, and own property names
• temporary primitive receiver boxing for dynamic Number/String/Boolean prototype method calls

The corresponding regression fixture is test-parity/node-suite/object/primitive-wrapper-toobject.ts. This issue looks stale-open and ready for maintainer closure.