language/runtime: support super and prototype lookup inside computed members

[andrewtdiz]

Summary

super inside computed object/class accessors and methods resolves through the current prototype chain, including after Object.setPrototypeOf.

Affected Test262 rows

• LLVM IR: redefinition of @perry_ic_0 in multi-module dylib compilation #69 language/computed-property-names/object/accessor/getter-super.js (runtime-fail: Uncaught exception: The value of object.a is 'a proto m'. Defined as get ['a']() { return 'a' + super.m(); } Expected SameValue(«"a0"», «"a proto m"») to be true)
• SIGSEGV on property access of globalThis (regression in 0.5.30+) #70 language/computed-property-names/object/accessor/setter-super.js (runtime-fail: Uncaught exception: The value of value is 'a 2', after executing object.a = 2; Expected SameValue(«0», «"a 2"») to be true)
• Date.now() does not advance during tight CPU-bound loops #74 language/computed-property-names/object/method/super.js (runtime-fail: Uncaught exception: object.a() returns 'a proto m', after executing Object.setPrototypeOf(object, proto); Expected SameValue(«"a0"», «"a proto m"») to be true)

Perry actual behavior from report

• 1 x runtime-fail: Uncaught exception: object.a() returns 'a proto m', after executing Object.setPrototypeOf(object, proto); Expected SameValue(«"a0"», «"a proto m"») to be true
• 1 x runtime-fail: Uncaught exception: The value of object.a is 'a proto m'. Defined as get ['a']() { return 'a' + super.m(); } Expected SameValue(«"a0"», «"a proto m"») to be true
• 1 x runtime-fail: Uncaught exception: The value of value is 'a 2', after executing object.a = 2; Expected SameValue(«0», «"a 2"») to be true

Node / ECMAScript expected behavior

super inside computed object/class accessors and methods resolves through the current prototype chain, including after Object.setPrototypeOf.

Likely subsystem

runtime prototype chain / HIR super-member lowering

Acceptance criteria

• Computed getter/setter/method super.m() rows return the same values as Node.
• Prototype mutations visible to ordinary object methods are visible to computed super paths.
• Existing direct non-computed super behavior does not regress.

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/computed-property-names/object/accessor language/computed-property-names/object/method --sample-cap 99999 --report /tmp/COMPUTED_SUPER.json

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