## [mirendev/runtime#1414](https://github.com/mirendev/runtime/pull/1414) I still think this is ready. The only new commit (`6a4c423`) is a docs change: a warning block in `traffic-routing.md` saying explicit app discovery requires app names that are a single lowercase DNS label. The DNS code and tests are the same as when I last reviewed. **App-name casing:** your probe corrected one of my claims. I said a mixed-case app name "fails closed". In fact, `web.MixedApp.app.miren` is lowercased and resolves to a *different* app named `mixedapp` if one exists. That's a misdirect, not an empty answer. Lowercasing the stored keys would merge app identities that app creation currently keeps distinct, so I agree that documenting the limit is the right scope for this PR. The new warning covers what a reader needs to know: uppercase or dotted names can't be targeted, and query capitalization can't choose between `MyApp` and `myapp`. Real support for those names belongs with a naming or alias policy, as you said. I've resolved that thread. **Tenancy:** the cross-app tenancy question still stands. Someone who owns the product's isolation story should sign off before merge, and you've left that thread open for them. That's also why I'm not recommending that this skip human review. ## Replies to existing threads _Posted to the PR's comment threads when you submit._ - _(reply)_ Thanks. That's an accurate summary of what the patch does and doesn't change: it affects discovery only and adds no firewall, RPC, or workload-identity permissions. I'm leaving this open for the product/tenancy owner, as you suggested. - _(reply & resolve: persuaded)_ Thanks for actually probing this. It corrects my comment. I said the explicit form fails closed for mixed-case names, but `web.MixedApp.app.miren` is lowercased and can resolve to a separate `mixedapp`. Since `MixedApp`, `mixedapp`, and `mixed.app` are distinct app IDs today, lowercasing the map keys would merge identities, which is worse. You've persuaded me not to normalize here. The warning in `traffic-routing.md` states the lowercase single-label requirement and the case-collision behavior plainly, and that's the right scope for this PR. A naming or alias policy can take it from there. --- **Verdict:** ready