Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Workbench: live measurements leave no versioned trace

Offen
  • Stimmt etwas nicht?
#459 6 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@auberginewly arbeitet bereits daran.

Seit 27.10.2026.

  • #1403 von @auberginewly — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
testing, tooling

Rechercherichtung

Start with workbench/README.md, especially “La prise réelle,” then inspect baseline.ts and workbench/lib/cassette.ts. The issue calls for manually verified --update-baseline runs for the real-take scenarios, followed by capturing the provider’s usage block in the recording proxy. Done should include tracked, verified measurements and a clear decision in the README about whether judged-PR cassettes should be committed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement

Split out of #428, which is being closed — its core ask is done, this is the adjacent point that was never in scope for it.

What's left

workbench/runs/ and workbench/reports/ are gitignored, and only three baselines are committed (consent.json, describe-project.json, wizard-enhance.json). Every live measurement made against this bench — including the ones behind #431, #432, #440, #452, #453, #454 and #456 — leaves no trace anyone else can replay without re-running it themselves, on their own key, against whatever the provider resolves that day.

Concretely, that means:

  • A cassette recorded during a PR review (e.g. workbench/cassettes/judge-migration-*.json) replays offline for whoever has the file, but nothing forces it to reach main — it's a byproduct of one session, not a tracked measurement.
  • The three real-take scenarios (real-wizard-enhance, real-zooms, real-zoom-grounding) have never been judged at all, because the take itself (workbench/fixtures/) is gitignored and absent from every clone. See #457's sibling problem and workbench/README.md § "La prise réelle" for what that costs on a fresh checkout (44 L0 tests fail on the missing fixture, silently, since CI never runs the bench).
  • A baseline's behaviour/dsl numbers, once written, are never re-verified against anything — nothing reads them back (baseline.ts only compares check ids), so they drift into being an unlabelled archive, which is exactly what happened to wizard-enhance.json before #453 said so explicitly.

First step, as noted when this was flagged

Freeze the real-take scenario baselines (--update-baseline, verified by hand rather than trusted), then capture the provider's usage block in the recording proxy (workbench/lib/cassette.ts) — the token count every context-size argument in this codebase wants is already in the response the recorder sees pass through, uncaptured.

Also worth deciding here, not in #428

Whether cassettes from a judged PR review should be committed as a matter of course (the way judge-migration-*.json were, by convention rather than by rule) or whether that's noise the repo doesn't want. workbench/README.md doesn't currently say either way.

Vorherrschende Sprache
TypeScript
Sterne
3.7k
Forks
231
Ø Merge
16 Std. 25 Min.
Gemergte PRs (30 T.)
331

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getopenscreen/openscreen

Alle Issues in getopenscreen/openscreen

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.