turbo-editors/turbo-core · 2026-09-03-third-editor.md

⑂ v1.0.1

2026-09-03-third-editor.md · 49 lines · 2.4 KBmarkdown    Blame HistoryRaw
   1# Handoff — 2026-09-03 — a third editor joined the family
3## Where this stopped
5Done, nothing in flight. **The library was not changed**: turbo-python was built against
6published `v0.4.0` and needed nothing new from here, so **no release is required**.
8## What changed, and why
10Only claims that count the editors, plus one comment:
12`README.md` (the list), `docs/{en,fr}/README.md` (the counting sentence),
13`profile/profile.go` (package comment), `docs/{en,fr}/how-to/release-the-library.md`,
14`docs/{en,fr}/how-to/write-the-starter-files.md`,
15`docs/{en,fr}/explanation/architecture.md`, `.memory/summary.md`.
17`docs/{en,fr}/how-to/test-without-publishing.md` got more than a count: the workspace now
18lists four modules, and a new paragraph says to list **nested** modules in the `use` block —
19a `go.mod` under a listed module stops being a module at all, and the error
20(*directory prefix . does not contain modules listed in go.work*) names the wrong problem.
22**History was left alone on purpose.** "`tools.DefaultMenu` was correct for a year and wrong
23the moment there were two editors" is a true sentence about the past.
25## The sweep, and its result
27`grep -rnE '"[^"]*\b(Go|Rust|golang|cargo|gopls|rust-analyzer)\b[^"]*"' --include='*.go'`,
28run because a third editor is what exposes a hardcoded language name. **Nothing to fix.**
29Every hit was one of: a false positive (`"Go to definition"`, `"Ctrl-G Go to line"`), a
30doc-comment example of the seam, or a true statement about the implementation
31(`"written in Go."` — every editor in this family *is* written in Go). The About box's
32language had already been moved into the profile after Turbo Rust exposed it; a pty run of
33turbo-python confirms it now reads "A Turbo C-style editor for Python".
35Re-run that sweep the next time an editor is added. It is only worth running if you read
36
38## Trap for the next session
40**A pty run of an editor is what finds this library's stale claims about its own menus.**
41Adding the Code menu made the tutorial and the menus reference wrong in *both* existing
42editors — the bar listing and the "press → four times" count — and no test in any of the
43four repositories could see it. Fixed in turbo-go and turbo-rust the same day; if you add a
44menu here, re-count the arrows in every editor's tutorial.
48Suite green, quality gate PASS (0/0/0, complexity 1810, unchanged). **Not committed** — the
49changes are in the working tree on `main` at `14aae7c`.

🛟 Updated. 28d5985 k33g 11h ago	1	# Handoff — 2026-09-03 — a third editor joined the family
	2
	3	## Where this stopped
	4
	5	Done, nothing in flight. The library was not changed: turbo-python was built against
	6	published `v0.4.0` and needed nothing new from here, so no release is required.
	7
	8	## What changed, and why
	9
	10	Only claims that count the editors, plus one comment:
	11
	12	`README.md` (the list), `docs/{en,fr}/README.md` (the counting sentence),
	13	`profile/profile.go` (package comment), `docs/{en,fr}/how-to/release-the-library.md`,
	14	`docs/{en,fr}/how-to/write-the-starter-files.md`,
	15	`docs/{en,fr}/explanation/architecture.md`, `.memory/summary.md`.
	16
	17	`docs/{en,fr}/how-to/test-without-publishing.md` got more than a count: the workspace now
	18	lists four modules, and a new paragraph says to list nested modules in the `use` block —
	19	a `go.mod` under a listed module stops being a module at all, and the error
	20	(directory prefix . does not contain modules listed in go.work) names the wrong problem.
	21
	22	History was left alone on purpose. "`tools.DefaultMenu` was correct for a year and wrong
	23	the moment there were two editors" is a true sentence about the past.
	24
	25	## The sweep, and its result
	26
	27	`grep -rnE '"[^"]\b(Go\|Rust\|golang\|cargo\|gopls\|rust-analyzer)\b[^"]"' --include='*.go'`,
	28	run because a third editor is what exposes a hardcoded language name. Nothing to fix.
	29	Every hit was one of: a false positive (`"Go to definition"`, `"Ctrl-G Go to line"`), a
	30	doc-comment example of the seam, or a true statement about the implementation
	31	(`"written in Go."` — every editor in this family is written in Go). The About box's
	32	language had already been moved into the profile after Turbo Rust exposed it; a pty run of
	33	turbo-python confirms it now reads "A Turbo C-style editor for Python".
	34
	35	Re-run that sweep the next time an editor is added. It is only worth running if you read
	36	every hit.
	37
	38	## Trap for the next session
	39
	40	A pty run of an editor is what finds this library's stale claims about its own menus.
	41	Adding the Code menu made the tutorial and the menus reference wrong in both existing
	42	editors — the bar listing and the "press → four times" count — and no test in any of the
	43	four repositories could see it. Fixed in turbo-go and turbo-rust the same day; if you add a
	44	menu here, re-count the arrows in every editor's tutorial.
	45
	46	## State
	47
	48	Suite green, quality gate PASS (0/0/0, complexity 1810, unchanged). Not committed — the
	49	changes are in the working tree on `main` at `14aae7c`.