Agent objective
- Interact with the supplied stateful environment.
- Produce verifier-checkable actions or artifacts.
- Maximise scalar reward under the package contract.
A TypeScript software-engineering benchmark for credential epochs under hostile JavaScript re-entry. The visible suite starts green while private cases expose interacting authority, liveness, retry, boundary, validation, and resource failures. Agents must repair stale-token rotation, refresh ownership, cross-context races, logout, and exact public declarations under isolated, mutation-audited verification.
A TypeScript software-engineering benchmark for credential epochs under hostile JavaScript re-entry. The visible suite starts green while private cases expose interacting authority, liveness, retry, boundary, validation, and resource failures. Agents must repair stale-token rotation, refresh ownership, cross-context races, logout, and exact public declarations under isolated, mutation-audited verification.
Enough detail to understand the intellectual terrain; generated instances, hidden mechanisms, and solution paths remain inside the private package.
| Environment | Mathematical or technical frontier | Adaptive research problem |
|---|---|---|
| Credential authority | Epochs, rotation, stale-token rejection | Ensure only the newest credential epoch can authorize work across re-entrant JavaScript and cross-context state. |
| Refresh ownership | Single-flight and retry semantics | Coordinate refresh callers, retries, cancellation, and terminal failures without duplicate authority or lost wakeups. |
| Lifecycle boundaries | Logout, disposal, validation | Prevent late completions from resurrecting sessions and preserve exact errors and public declarations. |
| Hostile scheduling | Microtasks, timers, callbacks | Remain live and deterministic under generated schedules that interleave callbacks at adversarial boundaries. |
| Resource safety | Listeners, promises, timers | Clean up waiters and resources across success, failure, cancellation, logout, and repeated lifecycle transitions. |
The seeded repository already passes all 14 visible tests but only 122/211 private cases and receives zero reward. The oracle passes every case, the production reproduction, strict build, and declaration checks; the verifier kills all 14 audited near-miss mutations. A perfect-score patch is supplied, although no separate normalized model-run artifact identifies its actor. The benchmark is valuable precisely because a green public suite is not evidence of correct concurrent authority semantics.
We publish aggregate behavior and task structure, while withholding generated instances, hidden labels, exact successful probes, private checks, and solution trajectories.
Shown with its provenance and limitations; it is not a performance guarantee.
A perfect-score patch is supplied, but no separate normalized score artifact is present.
As identified by the supplied artifact.
1 reported runs.
swe0147-perfect-score.patch
Machine-readable provenance and the exact displayed metric are available in results.json.
The paid ZIP will live in a private R2 bucket. Vercel authorizes the buyer and issues a 2–5 minute object URL; R2 serves the bytes directly.
Authenticated buyer + entitlement check
+ private R2 object + 2–5 minute signed URL
= direct, auditable download
Package SHA-256
7a18ec976a45742409da97b74212c688321a2fbbd17c5dd2f9455be59c9e8a1aOne purchase licenses this identified item to one legal organisation for worldwide, perpetual commercial model training, evaluation, research and development. Redistribution and resale of the package are not permitted.