Handoff — 2026-09-03 (later) — released, and the state of the family after it
Where this stopped
v0.1.0 is out and everything is green here. Nothing in flight in this repository.
The family, as of this scan
| Repository | HEAD | Tag | Tree | Suite |
|---|---|---|---|---|
| turbo-core | 4f93fb0 |
v0.4.1 |
clean | green |
| turbo-go | ab30ec6 |
v0.4.2 |
clean | red |
| turbo-rust | 9b90655 |
v0.4.2 |
clean | red |
| turbo-python | bccbb0b |
v0.1.0 |
clean | green |
All three editors pin turbo-core v0.4.1, none has an active replace.
The thing to know before touching anything else
turbo-go v0.4.2 and turbo-rust v0.4.2 are tagged releases whose test suites fail. The
failures were there before this editor existed and are now inside a release:
- turbo-go, four in
internal/golang/templates_test.go— the starter tools file holds
eight tools where the test wants five (Echo,GrepandInit modulewere added
deliberately, to teach themenukey and the{{placeholder}}syntax);Grepgoes to
editorandEchototerminalwhere the test wantspopup; two starter commands take
a value where the test asserts none does; and the snippets file no longer has the
if err != nilsnippet the test looks for. - turbo-rust, two in
internal/rustlang/templates_test.go— six tools where the test
wants five, andEchoin a terminal. (A third failure, about the Rust menu being named
Go, went away when the user committed their in-flight template edit.)
The templates are right and the assertions are stale, which is why this is a small job
rather than a design question: turbo-python's equivalent tests count their own Echo tool,
and the turbo-new-editor skill prescribes showing a placeholder and the menu key in the
starter file. It was left alone here because it belongs to those repositories' own cycle —
but a release that does not pass its own make check is worth fixing before the next one,
and 01-release.tag.sh runs make check, so the next tag in either will refuse to be cut.
Also worth doing, unchanged from the previous handoff
docs/diagrams/packages.drawiois unheld in turbo-go and turbo-rust. This repository's
diagram_test.goholds it togo list; copying it across is perhaps twenty minutes each.- Try pyright or ruff-lsp against this profile — two lines, and it would say whether "pylsp
answers seven of nine questions" is about pylsp or about Python.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
|