Make the Model Tiers Bullets Agree on What a Dispatch Naming No Model Runs At #3529

Summary

AGENTS.md "Model Tiers", at hub main f60f57d, states two different results for a dispatch that names no model.

• The highest bullet states the conditional form: "A dispatch naming no model runs at its agent definition's model where one is set, and otherwise at the session's own."
• The "A tier resolves only through this table" bullet states the unconditional form: "A session that cannot see this table names no model rather than guessing one, so the subagent runs at the session's own model."
• The "An orchestrating seat runs at frontier" bullet does the same: "A dispatch that names no model inherits whatever the session runs on."

Failure

A session that cannot see the table follows the second bullet and omits the model, expecting the subagent to run at the session's own model. Where it dispatches a typed agent whose definition pins a model, the subagent runs at that pinned model instead, which can be a lower tier than the session. The rule's stated promise does not hold in that case.

Expected

The two later bullets carry the same condition as the first, or point at it, so the three agree. The same region is a generated include in backlog-burndown, local-strict-review, and unattended-handoff, so the fix lands in AGENTS.md and a regenerate carries it.

Found By

A local strict review pass over ptr727/Blog's resync to hub f60f57d, which carries this region verbatim.

🤖 Generated with Claude Code