Track pending Iterator take/drop RangeError semantics from tc39/ecma262#3776

Summary

Track the pending Iterator.prototype.take / Iterator.prototype.drop limit semantics from tc39/ecma262#3776 so GocciaScript follows the normative result rather than treating the current Test262 failures as a confirmed engine regression.

Why

The conformance dashboard should distinguish an implementation defect from an upstream suite/spec ordering gap. Implementing the currently failing assertions immediately would move GocciaScript ahead of the published ECMA-262 algorithm while the normative change remains unresolved.

Current behavior

At ECMA-262 main snapshot 994b48ed0c0940edaa0e4ce4d9e358fa3ba91edb, the take and drop algorithms reject NaN and negative limits but do not reject finite values above Number.MAX_SAFE_INTEGER:

• https://tc39.es/ecma262/multipage/control-abstraction-objects.html#sec-iterator.prototype.take
• https://tc39.es/ecma262/multipage/control-abstraction-objects.html#sec-iterator.prototype.drop

The approved but still-open normative PR tc39/ecma262#3776 adds a RangeError for finite limits above 2**53 - 1 and changes iterator-helper counters to Numbers:

• https://github.com/tc39/ecma262/pull/3776

Test262 merged those assertions first in tc39/test262#5065:

• https://github.com/tc39/test262/pull/5065

Against pinned Test262 SHA b363f29d3c43c626dc852744ad64a0b48a003693, current main fails six tests under take and drop:

• argument-effect-order.js
• argument-validation-failure-closes-underlying.js
• limit-rangeerror.js

The failures all reduce to the pending large-finite-limit behavior. The latest retained main artifact is CI run 30980196951. Local filtered bytecode runs reproduce 30/33 passing for take and 31/34 for drop with the same three failures per method.

Relevant implementation paths:

• source/units/Goccia.Values.IteratorValue.pas
• IteratorLimitArgOrClose
• TGocciaIteratorValue.IteratorTake
• TGocciaIteratorValue.IteratorDrop

Expected behavior

• Track the disposition of tc39/ecma262#3776.
• If the normative change lands, implement the finalized counter and range semantics and add focused local coverage in interpreted and bytecode modes.
• If the normative change is revised or rejected, update the Test262 baseline/pin only with corresponding upstream evidence.
• Keep release reporting explicit that these six failures are currently caused by Test262 advancing ahead of published ECMA-262.

Scope notes

This issue does not currently establish a GocciaScript regression. Do not change iterator semantics solely to make the six tests green before the upstream normative contract is settled.

Start by reading IteratorLimitArgOrClose, TGocciaIteratorValue.IteratorTake, and IteratorDrop in source/units/Goccia.Values.IteratorValue.pas, then reproduce the filtered Test262 runs for take and drop. Check tc39/ecma262#3776 and tc39/test262#5065 before changing behavior. Done means recording the upstream disposition and, if finalized, adding the required semantics and focused interpreted and bytecode coverage.