diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 0616906c..47692f55 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -55,7 +55,7 @@ jobs:
           go mod tidy
           git diff --exit-code go.mod go.sum
           go build ./...
-          go test -race -count=1 -timeout=30m ./...
+          go test -race -count=1 -timeout=60m ./...
 
       - name: Verify sub-modules
         run: |
@@ -75,12 +75,12 @@ jobs:
                   *) packages+=("$package") ;;
                 esac
               done < "$RUNNER_TEMP/cortex-release-optimizer-packages.txt"
-              go test -race -count=1 -timeout=30m "${packages[@]}"
+              go test -race -count=1 -timeout=60m "${packages[@]}"
               for backend in sqlite postgres mongo; do
-                go test -race -count=1 -timeout=30m "./store/$backend"
+                go test -race -count=1 -timeout=60m "./store/$backend"
               done
             else
-              go test -race -count=1 -timeout=30m ./...
+              go test -race -count=1 -timeout=60m ./...
             fi
             popd > /dev/null
             echo "::endgroup::"
diff --git a/AGENTS.md b/AGENTS.md
index ed450a0d..24173bd8 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -26,7 +26,7 @@ All modules declare Go 1.26.0. Build with `GOWORK=off`, which is what CI sees.
 GOWORK=off go build ./...
 make test              # go test -v ./...  (root module only)
 make test-race         # go test -race -v ./...
-make test-coverage     # race + atomic coverage, 30-minute package timeout
+make test-coverage     # race + atomic coverage, 60-minute package timeout
 make vet               # go vet ./...      (root module only)
 make lint              # golangci-lint in every module, inttest with -tags integration
 make lint-fix
@@ -50,7 +50,7 @@ cd extension && GOWORK=off go test -race -count=1 ./...
 
 | Job | Scope | What it runs |
 |---|---|---|
-| `ci` (shared `xraph/workflows` `go-ci.yml@v1`, Go 1.26) | root | `make test`, `make test-coverage` (race + atomic coverage, 30-minute package timeout), golangci-lint at the version pinned there, `gofmt -l .`, `make vet`, a `go mod tidy` diff, gosec and govulncheck (both gating), and a check that nested modules require cortex at versions the proxy can serve |
+| `ci` (shared `xraph/workflows` `go-ci.yml@v1`, Go 1.26) | root | `make test`, `make test-coverage` (race + atomic coverage, 60-minute package timeout), golangci-lint at the version pinned there, `gofmt -l .`, `make vet`, a `go mod tidy` diff, gosec and govulncheck (both gating), and a check that nested modules require cortex at versions the proxy can serve |
 | `format` | whole tree | `goimports -l -local github.com/xraph/cortex .` must print nothing |
 | `submodules` | `api`, `sentinel`, `extension`, `integrations/fabriq`, `integrations/sandbox`, `optimization`, `mcpbridge`, `a2aremote`, `a2aremote/grpcbind` | `go mod tidy` diff, `go build ./...`, `go test -race -count=1 ./...` |
 | `docs` | `docs/` | `pnpm install --frozen-lockfile`, `pnpm types:check`, `pnpm lint`, `pnpm build` |
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f2d3964f..448a2a01 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,14 @@ All notable changes to this project are documented in this file.
 
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
+## [1.10.1] - 2026-10-30
+
+Use this one. It's the same code as v1.10.0, but the v1.10.0 release run tagged the root module and then timed out in its race tests before it could tag the sub-modules, so `api/v1.10.0`, `extension/v1.10.0`, `mcpbridge/v1.10.0` and the rest were never published. Everything listed under 1.10.0 below ships here.
+
+### Fixed
+
+- The release workflow gives each race test run 60 minutes, the same as CI coverage. The engine and SQLite packages need about 25 to 30 minutes on a hosted runner, which left no room under the old 30.
+
 ## [1.10.0] - 2026-10-29
 
 v1.9.0 went out on 2026-10-27 and carried the work that was on `main` before this, assured execution included. That part is experimental and stays off unless you turn it on. If you run v1.9.0 today, read "Upgrading from v1.9.0" in `MIGRATION.md` before you roll this out. Coming from v1.8.0, read "Upgrading from v1.8.0" too.