# Handoff — 2026-09-03 — the defects a third editor exposed here

## Where this stopped

Done, nothing in flight. **Documentation only; no code changed and no dependency moved.**

## Why this repository was touched at all

turbo-python was built by adapting this project's documentation. Adapting it found three
things that were wrong **here**, not just in the copy.

## What changed

- `docs/en/reference/menus.md` — said project menus appear **"between Go and Help"**, twice,
  in an editor whose menu is called Rust. The French version had it right. This is the same
  mistake this project already recorded and fixed once, in the French tools reference: a
  mechanical substitution that only looked at identifiers.
- `docs/{en,fr}/reference/menus.md` and `docs/{en,fr}/tutorials/getting-started.md` — the
  menu bar listing omitted **Code**.
- `docs/{en,fr}/tutorials/getting-started.md` — "press `→` four times to reach Options" has
  been **five** since the Code menu shipped.
- `docs/{en,fr}/explanation/architecture.md` — "both editors" → "every editor built on it".

Checked by driving this editor's own binary in a pty, not by reasoning about it: the bar
reads `File  Edit  Search  Run  Code  Options  Window  Snippets  Rust  Help`, and five `→`
from `File` lands on `Options`.

## Left undone, and cheap

`docs/diagrams/packages.drawio` is a file nothing imports, so nothing notices when it stops
describing the code. turbo-python's copy of it shipped labelled `internal/rustlang`, with
`host="turbo-rust"`, because a diagram cannot be grepped for correctness. turbo-python now
has a `diagram_test.go` that parses the drawio and holds it to `go list` — the boxes are the
packages the module imports, every arrow out of our own packages is a real import, and no
label names another editor's language. Copying it here is perhaps twenty minutes.

## Already red when I arrived — not caused here, not fixed here

`go test ./...` **fails at `HEAD` on a clean tree**, verified by stashing this session's
changes and running it again. Three tests in `internal/rustlang/templates_test.go`:

- `TestTheCreatedToolsFileHoldsTheFiveCargoCommands` — the file now holds **six**: the five,
  plus the `Echo` tool the starter file gained deliberately to teach the `menu` key.
- `TestRunIsTheOneToolInATerminal` — `Echo` goes to `terminal`, on purpose.
- `TestTheCreatedToolsFileNamesTheRustMenuNotTheGoOne`.

**The template moved and the tests did not.** The template looks right — turbo-python's
equivalent test counts its own `Echo` tool, and the `turbo-new-editor` skill prescribes
showing the `menu` key in the starter file — so the fix is in the assertions. Left alone
because that is the tools-template cycle's business, not a documentation session's.

## State

**Not committed.**