## [mirendev/runtime#1426](https://github.com/mirendev/runtime/pull/1426)

Nothing of substance has changed since my last review, and I still recommend approval. The branch is now a single commit, `f381862`, with the same content I reviewed at `bd6087f`. In `servers/sandbox/pools.go`:

- `filterInventoryApp` still runs against each pool's real owner before the `app` label is read.
- The label is used only to display ownerless pools and to match them against the app filter.
- `poolVersion` reads concurrency through `coreutil.ResolveConfig`. That's safe for MODE because `ResolveAddonConfig` only touches `Variables` and service `Disks`.
- `TestPoolInventoryAddonPoolApp` still pins the deny case for app-bound callers, and `TestSandboxPoolListFilters` still runs an addon pool through the real CLI flags.

There are no new comments or threads, and evanphx has approved this head.

**Who sees addon pools under `--app shop`.** Only cluster admins see shop's database pool there. A caller who owns `shop` but isn't a cluster admin still won't see it, because ownerless pools need admin rights. That matches what this code did before, so it isn't a regression. I'm mentioning it in case someone reads the description as "app owners now see their addon pools."

**Older servers.** On servers without the RPC, the legacy fallback filters `--app` client-side against `pool.App()`. That path never reads the label, so addon pools there still show `-` and drop out of a filtered listing. This only affects servers that predate the RPC, so I don't think it needs to block.

Why I'd skip another human pass: the only security-relevant change is moving authorization from a single upfront check to a per-pool check, and that check still runs before any label is read. A test covers the case where an app-bound caller must be denied. Everything else is a contained CLI and inventory change, and each new behavior has its own test.

---

**Verdict:** ready