| 📦 Turbo Rust f69efbe k33g 12h ago | 1 | # Handoff — 2026-09-20 — `-load-config` (needs turbo-core v1.0.3) |
| 2 | |
| 3 | ## State |
| 4 | |
| 5 | - `-load-config <url>` wired in `main.go`, three tests in `main_test.go`, docs EN+FR updated. Green under the umbrella `go.work` (`turbo-editors/`), which resolves turbo-core to the local checkout. |
| 6 | - **`go.mod` still says turbo-core v1.0.2** — `GOWORK=off make check` fails until turbo-core v1.0.3 is tagged and this is re-pinned. Even under the workspace, the two release-script tests (`TestTheTagScript…`) fail for the same reason: they build a copy of the module outside it. Everything else is green. |
| 7 | |
| 8 | ## Next steps |
| 9 | |
| 10 | 1. When turbo-core v1.0.3 is tagged: `go get rickub.com/turbo-editors/turbo-core@v1.0.3 && go mod tidy && GOWORK=off make check`. |
| 11 | 2. Try it for real: in an empty directory, `turbo-rust -load-config https://rickub.com/turbo-editors/configs/tree/main/golang-init` (the sample repository holds `.turbo-go` only — for this editor a directory with a `.turbo-rust` is needed), then start `turbo-rust` and check the settings took. |
| 12 | 3. Then `./01-release.tag.sh` as usual. |
| 13 | |
| 14 | ## Traps |
| 15 | |
| 16 | - The sample configs repository is `rickub.com/turbo-editors/configs`; its git address is `git.rickub.com`, which `configrepo` tries second. A wrong first candidate costs one `ls-remote`, not the load. |
| 17 | - The editor refuses when `.turbo-rust` already exists (`configrepo.ErrExists`); there is deliberately no `--force`. |