You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
hello_world.t27 counts the backends, so it goes stale every time one lands #4505
specs/demos/hello_world.t27 line 5, on fix/reject-vibee-specs — the branch
the website vendors as an overlay:
; watch it become tokens, an AST, and five different target languages.
There are seven (#4502). It was wrong at six too. This is the first spec a
reader opens — the website's Explorer links to it by name — so it is the worst
possible place for a number that nobody updates.
Границы
One line, one file. Not "fix it to seven": a literal count in prose is a thing
that goes stale on a schedule nobody controls, and the same reasoning already
deleted two test counts from bindings/wasm-explorer/src/lib.rs in #4502 and a
"five backends" sentence from the website's tech tree. The sentence names the
category instead of counting it.
Готово когда
hello_world.t27 carries no backend count, and an eighth backend costs it
nothing.
An attempt claimed this issue on 2026-09-21 and left an empty branch. A dispatch row that has spent its retry ceiling is released once and then keeps its issue for good, which is the right rule for a third identical failure and the wrong outcome for an issue nobody ever attempted twice. The new issue carries the same work, the same boundary, and today's brief.
Closing this one so the swarm can take the work again.
Activity
feat(website): TypeScript joins the spec tab, and the backend lists s…
Deploy dd6841d
gHashTag commentedon Sep 24, 2026
Re-filed as #4703.
An attempt claimed this issue on 2026-09-21 and left an empty branch. A dispatch row that has spent its retry ceiling is released once and then keeps its issue for good, which is the right rule for a third identical failure and the wrong outcome for an issue nobody ever attempted twice. The new issue carries the same work, the same boundary, and today's brief.
Closing this one so the swarm can take the work again.