fix: drop wrapper frames from schedule stacks when schedule is overridden

[sderrow]

Schedule-location stacks now start at the caller even when a limiter overrides schedule() with a subclass method (including async) or an arrow function on the instance. Previously, the override's wrapper frames appeared at the top of every section.

If the override isn't on the stack, for example when the base method is called directly, a fallback capture keeps the section intact. Overrides made with .bind() keep their wrapper frames, because V8 can't cut a stack at a bound function.

The schedule-stack code also moves out of async-context.ts into its own schedule-stack.ts module, with its tests in a matching file. That move doesn't change behaviour.

[sderrow]

• fix: flaky Group error and timing test #28
• chore: enable more lint rules #27
• chore: no non-null assertions #26
• fix: drop wrapper frames from schedule stacks when schedule is overridden #25 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[sderrow]

Merge activity

• Oct 5, 3:02 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 5, 3:03 AM UTC: @sderrow merged this pull request with Graphite.