# Handoff — 2026-09-02 — code navigation and better editing, documentation side

## State

Done, on `feature/code-navigation`. Nothing is committed.

Two tickets, both turbo-core's code: the Code menu, and ticket 19 (double-click selects a word, `Ctrl-N` inserts a line, `Ctrl-Y` deletes one, **redo moves to `Ctrl-R`**).

All the code is turbo-core's. Turbo Go gained a new how-to (`ask-about-code.md`, EN+FR), the **Code** section in the menus reference, two keys in the keyboard reference, and an explanation section on the nine requests. Suite green, gate PASS 0/0/0.

**This branch builds as it stands**, against the published `turbo-core v0.3.0`.

## In flight

Nothing.

## Next steps

1. Review, commit, merge.
2. After **turbo-core v0.4.0** is published: `go get codeberg.org/turbo-editors/turbo-core@v0.4.0 && go mod tidy && make check`. That is when the Code menu appears here.

## Watch out for

- **Redo changed key.** `Ctrl-R`, not `Ctrl-Y`. It is in the menus reference with the reason, because a key moving under someone who had learnt it is the kind of change that is only forgivable if it is said out loud.
- **The documentation describes a menu this editor cannot show yet.** That is the same order as the last two cycles and is deliberate — but it means the docs are ahead of the binary until v0.4.0 lands.
- **A menu item moved has to be deleted from four files, not two.** The French menus reference is separate text, not a translation applied at build time.
- `navigate-code.md` and `ask-about-code.md` are different guides for different needs. Do not merge them: one is about moving around a file, the other about asking what a name means.