## [mirendev/runtime#1446](https://github.com/mirendev/runtime/pull/1446) I think this is still ready for human review. I'm not recommending it skip one, for the same reason as before: it's a security boundary that runs across the coordinator, the runner, config pinning and app deletion. **What changed:** the branch is now a single squashed commit. The code is the same as in the version I last reviewed, including the server, ownership, materialize, pin, remote-resolver, cluster-backend, secretpin, app-delete and build-saga files. The only content change is in `docs/docs/secrets.md`. That doc change is a real fix. The note used to tell users to upgrade runners first, but that isn't the order an upgrade happens in. It now describes the actual order: the server upgrades first, then distributed runners one at a time. It also says a runner still on the old version can't start sandboxes that use an owned secret until it catches up, and tells users to wait for the upgrade to finish before giving secrets an app. The PR description now says the same. **Earlier questions:** - **Rollout order:** settled. You've accepted that old runners fail closed on owned secrets during the upgrade window, and the docs now say so accurately. I'm dropping it. - **Whether `Spec.Version` can be trusted to identify a sandbox's app:** still open, and still needs a human reviewer. It's what decides which app a sandbox belongs to when the runner checks ownership (the app callback passed to `MaterializeEnv`, `controllers/sandbox/sandbox.go:2564`). I found no new defects. The race between a secret write and an app delete is tracked separately, as the description says. --- **Verdict:** ready