# Handoff — 2026-09-19 — Rickub migration and the Release workflow

## State

- Module `rickub.com/turbo-editors/turbo-rust`, pinned to `rickub.com/turbo-editors/turbo-core v1.0.0`; `GOWORK=off make check` green.
- Releases: `./01-release.tag.sh` tags; the tag push runs `.github/workflows/release.yml`, which builds with `./02-build-releases.sh` and publishes the page with the binaries. `02-release.publish.sh` and `04-release.upload-binaries.sh` are deleted. No token needed.
- **Nothing is committed.** Fresh `git init`, `origin` at `ssh://git@rickub.com/turbo-editors/turbo-rust.git`, no commit; the sandbox cannot reach the remote.

## Next steps

1. Check `release.env` (`TAG="v1.0.0"`, `ABOUT="Turbo Rust"`) and run `./01-release.tag.sh` from a machine that reaches Rickub. It makes the root commit, pushes `main`, tags, pushes the tag.
2. Watch the Release workflow on the Actions tab. turbo-go's identical workflow has run and published; this one has not yet.
3. If the publish step answers 403, the binaries are on the run page as the `turbo-rust-<tag>` artifact (14 days).
4. `turbo-rust.token.env` was deleted on 2026-09-19; nothing read it any more.

## Traps

- `go.work` beside this checkout (where there is one) points at `../turbo-core`. Check the *published* shape with `GOWORK=off`; the release tests already do for their children.
- Do not `go get …/turbo-core@v0.9.0` under the new path: the proxy has it, but its `go.mod` declares the Codeberg path. v1.0.0 is the first usable version.
- `release/` holds the Codeberg-era binaries (hundreds of MB). Gitignored; the tests skip it when copying the module.
- `sed -i` on this filesystem drops the execute bit; `chmod 755` the scripts after any such edit.