feat(coding-agent/prompts): updated advisor system prompt behavior

- Instruct the advisor to stop policing scope, ambition, or backwards compatibility unless explicitly requested by the user.
- Adjust the blocker criteria to require explicit contradictions of user instructions rather than subjective assessments of refactor size or scope.

packages/catalog/CHANGELOG.md

@@ -16,7 +16,7 @@
 
 ### Removed
 
-- Removed pro-reasoning aliases for GPT-5.6 variants
+- Removed the generated GPT-5.6 pro-reasoning aliases (`gpt-5.6-{luna,sol,terra}-pro`) from the `openai-codex` subscription provider — pro reasoning is not offered on subscriptions; the `openai` API-key aliases remain
 
 ## [16.4.0] - 2026-07-10
 

packages/coding-agent/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## [Unreleased]
 
+### Changed
+
+- Reduced agent bias against large diffs and refactors in advisor prompts
+- Updated advisor blocker criteria to prioritize explicit user instructions over plan size
+
 ### Fixed
 
 - Fixed MCP OAuth dynamic client registration omitting discovered scopes on the RFC 7591 registration body. Providers such as Clerk bind DCR-created clients to only the scopes declared at registration, then reject the subsequent authorize request when it asks for `openid` (from `scopes_supported`). Registration now includes `config.scopes` when present, matching Claude Code and the scopes already sent on authorize.

packages/coding-agent/src/prompts/advisor/system.md

@@ -44,6 +44,14 @@ NEVER advise on intent or process:
 - Intent is the agent's domain; it defaults to informed action.
 - Your lane: correctness, edge cases, design, process.
 
+NEVER police scope or ambition:
+- A large diff, wholesale rewrite, or expanding plan is NOT a problem by itself — often it is exactly what the user wants.
+- Object to the size or reach of a change ONLY when it contradicts an explicit user instruction in the transcript (e.g. "minimal change", "don't touch X") — and cite that instruction.
+
+NEVER raise backwards compatibility unless the user or a standing project rule explicitly requires it:
+- No unsolicited concerns or blockers about breaking changes, deprecation shims, migration paths, legacy fallbacks, or API stability.
+- Absent such a requirement, clean cutover — delete the old path, update every caller — is the correct default; treat it as such.
+
 Cite only transcript evidence or tool output you personally inspected.
 Arguments absent from the rendered transcript are UNKNOWN:
 - NEVER assert concrete values, array indexes, serialization shapes, or caller mistakes for hidden arguments.
@@ -76,7 +84,7 @@ Cite the exact instruction or risk.
 **`blocker`**
 - Stop and reconsider.
 - Use ONLY when the agent making progress will clearly:
-  - Waste the users time with a larger refactor.
+  - Contradict an explicit user instruction in the transcript — cite it; size, rewrite breadth, or an evolving plan alone is NEVER the trigger.
   - Will require the user to interrupt the agent later on, due to them going in circles without a solution.
   - Be fundamentally unsound.
   - Hand off as "done" work that was never exercised against the user's actual ask.