language/runtime: computed property names and member definition semantics

[andrewtdiz]

Summary

Track computed class/object member definition failures: numeric/symbol keys, accessors, static members, super, and key-conversion side effects.

Child issues

• language/runtime: define computed class methods and static members with correct keys/order #3557
• language/runtime: install computed accessors and duplicate accessor definitions #3558
• language/runtime: preserve computed property-key conversion side effects #3559
• language/runtime: support super and prototype lookup inside computed members #3560
• language/runtime: normalize numeric and symbol keys in computed object literals #3561

Scope notes

• Treat these as Perry ECMAScript/runtime-language semantics gaps, not Node stdlib parity.
• Likely subsystems are parser, HIR lowering, codegen, runtime object model, async scheduling, or error/throw semantics.
• Eval/runtime-dynamic-code rows are excluded separately under Perry's AOT policy.

Validation

scripts/test262_subset.py --root vendor/test262 --dir language/computed-property-names --sample-cap 99999 --report /tmp/perry-test262-computed.json

Acceptance for this epic: every linked child issue has a focused regression or Test262 validation path, and the affected rows are removed from the gap report without introducing duplicate issue coverage.