Before submitting
Problem or opportunity
Since PR #1384, every global profile apply asks for confirmation, including the case where the profile's agent routes already match the current global routing. That apply would change nothing, so the dialog is pure friction for an operator re-selecting the active profile or verifying state, and it trains users to approve the dialog without reading it, which weakens the guard on the destructive cases.
Proposed outcome
When the effective routing diff is empty (no replaced, cleared, or added agent routes, and no orchestrator change), applying should proceed without the confirmation dialog, or with a non-modal informational notice ("profile already active"), depending on what the maintainers prefer. The destructive confirmations introduced by #1349 and PR #1384 stay exactly as they are.
Alternatives considered
Keeping the confirm on no-op applies (current behavior) with the "its agent routes already match the current global routing" wording; it is safe but adds friction in the only non-destructive case.
Additional context
Identified during review of PR #1384 as a friction refinement. The dialog already computes the empty-diff case (extensions/gentle-ai.ts, populated-apply branch). Related: #1349, #1384.
Before submitting
Problem or opportunity
Since PR #1384, every global profile apply asks for confirmation, including the case where the profile's agent routes already match the current global routing. That apply would change nothing, so the dialog is pure friction for an operator re-selecting the active profile or verifying state, and it trains users to approve the dialog without reading it, which weakens the guard on the destructive cases.
Proposed outcome
When the effective routing diff is empty (no replaced, cleared, or added agent routes, and no orchestrator change), applying should proceed without the confirmation dialog, or with a non-modal informational notice ("profile already active"), depending on what the maintainers prefer. The destructive confirmations introduced by #1349 and PR #1384 stay exactly as they are.
Alternatives considered
Keeping the confirm on no-op applies (current behavior) with the "its agent routes already match the current global routing" wording; it is safe but adds friction in the only non-destructive case.
Additional context
Identified during review of PR #1384 as a friction refinement. The dialog already computes the empty-diff case (extensions/gentle-ai.ts, populated-apply branch). Related: #1349, #1384.