## [mirendev/runtime#1447](https://github.com/mirendev/runtime/pull/1447) This is ready for a human to look at. Both of my earlier threads are fixed in the text, and the two new upgrade notes match the server docs. **Since the last review** - **Etcd authorization note (`changelog.md:17`):** it now has its own Upgrade Notes bullet with three points: - check every runner's certificate name before upgrading the coordinator; - re-join mismatched runners with `remove`/`join`, keeping the same runner ID; - roll back through the pre-upgrade etcd snapshot, not by swapping in the old binary. All three match the `[etcd]` section of `server-config.md`, and the `#etcd` anchor resolves. "Networking may stop" also fits the docs' caveat that a legacy name can sometimes be mapped but networking isn't guaranteed. One point needs someone with the history. The bullet says only runners that joined **before v0.10.0** are at risk, because they got a shortened 8-character name. `server-config.md` tells operators to check every runner, and I couldn't find the v0.10.0 cutoff anywhere in the tree. If that version is wrong, operators with affected runners will skip the check. The CommonName drift warning in `runner start` (`cli/commands/runner_start.go:321`) catches some of these cases either way. - **`distributed` mode removal (`changelog.md:18`):** this matches the Embedded Components section. That covers which settings are refused, the server refusing to start, the rollback during an upgrade, and leftover addresses being ignored. The anchor resolves. - **`service` claim:** it now has the caveat and points to the limits. I've resolved that thread. - **TTL default:** `pr-environments.md` now says 7 days, which matches the deploy flag's default. - **`hey` flags:** the entry now only says the short flags `-n`/`-c`/`-z` match. That's a smaller claim and less likely to mislead, but I still can't check it because the old command isn't in the tree. I also checked a few entries against code. `app disable` requires the deploy permission (`servers/app/authorization_test.go:69`), so "anyone who can deploy can disable" holds. The cold-start page shows after 1.5s (`servers/httpingress/httpingress.go:472`). **Still open:** confirming the release covers everything since v0.17.0 needs `git log v0.17.0..main`, which I can't run here. I'm not recommending approval. The v0.10.0 cutoff, the `hey` flags and that completeness check all need someone with the git history. ## Replies to existing threads _Posted to the PR's comment threads when you submit._ - _(reply & resolve: addressed)_ Fixed by the new Upgrade Notes bullet at line 17. It covers the pre-upgrade runner check and re-joining with the same runner ID. It also says that only the managed rollback, not swapping in the old binary, turns the new checks off. All three points match `server-config.md#etcd`. I couldn't confirm the "before v0.10.0" cutoff in the tree, so I've asked a human to check it in the summary. - _(reply & resolve: addressed)_ The entry now says it only separates services when no role can deploy or exec into the app, and it points to the limits. That's the caveat I was after. --- **Verdict:** ready