Handoff — 2026-09-01 — tickets 9 to 14

State

Done, on the branch feature/menu-theme-and-settings. Nothing is committed.

Only ticket 9 is this repository's: the settings template now writes autosave = true. The other five are turbo-core's and reach Turbo Go through the library.

Suite green, quality gate PASS 0/0/0, complexity unchanged. Documentation updated in EN and FR: the settings, menus, tools and snippets references, configure-a-project.md, and a new section in run-the-tests.md on testing against an unreleased turbo-core.

This branch builds as it stands, against the published turbo-core v0.2.0. That is deliberate and unlike the last two releases, which left the editors unbuildable until the library was published.

In flight

Nothing half-done.

Next steps

Review and commit, merge to main.
After turbo-core v0.3.0 is published — see turbo-core's handoff of the same date:
```
go get codeberg.org/turbo-editors/turbo-core@v0.3.0
go mod tidy && make check
```
That is when the five library-side tickets become visible here.

Open questions / blockers

None.

Watch out for

settings.Default() must stay autosave: false. Only the template turns it on. The library default is what applies to a project with no settings file, and the editor writing to disk in a directory somebody merely started it in is a much larger claim than the ticket asked for. TestAProjectWithNoSettingsFileStillDoesNotAutosave holds that line.
To work against a turbo-core checkout beside this one, use go work init . ../turbo-core, not a replace. It changes no tracked file, so there is nothing to forget before committing, and go.work is gitignored. Verify with go list -f '{{.Dir}}' codeberg.org/turbo-editors/turbo-core/app — if it answers a pkg/mod path you are testing the published library and everything will still pass.

 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


# Handoff — 2026-09-01 — tickets 9 to 14

## State

Done, on the branch `feature/menu-theme-and-settings`. Nothing is committed.

Only **ticket 9** is this repository's: the settings template now writes `autosave = true`. The other five are turbo-core's and reach Turbo Go through the library.

Suite green, quality gate **PASS 0/0/0**, complexity unchanged. Documentation updated in EN and FR: the settings, menus, tools and snippets references, `configure-a-project.md`, and a new section in `run-the-tests.md` on testing against an unreleased turbo-core.

**This branch builds as it stands**, against the published `turbo-core v0.2.0`. That is deliberate and unlike the last two releases, which left the editors unbuildable until the library was published.

## In flight

Nothing half-done.

## Next steps

1. Review and commit, merge to `main`.
2. After **turbo-core v0.3.0** is published — see turbo-core's handoff of the same date:
   ```sh
   go get codeberg.org/turbo-editors/turbo-core@v0.3.0
   go mod tidy && make check
   ```
   That is when the five library-side tickets become visible here.

## Open questions / blockers

- None.

## Watch out for

- **`settings.Default()` must stay `autosave: false`.** Only the template turns it on. The library default is what applies to a project with no settings file, and the editor writing to disk in a directory somebody merely started it in is a much larger claim than the ticket asked for. `TestAProjectWithNoSettingsFileStillDoesNotAutosave` holds that line.
- **To work against a turbo-core checkout beside this one, use `go work init . ../turbo-core`, not a `replace`.** It changes no tracked file, so there is nothing to forget before committing, and `go.work` is gitignored. Verify with `go list -f '{{.Dir}}' codeberg.org/turbo-editors/turbo-core/app` — if it answers a `pkg/mod` path you are testing the published library and everything will still pass.