fix(spec): Flow.errorHandling's maxAttempts refusal says a bare rename runs one attempt more, not fewer

maxAttempts counts the first attempt and maxRetries does not, so
maxAttempts: 3 is 3 runs and a bare rename to maxRetries: 3 is 4. The
prescription (maxRetries one lower) was right; the consequence clause was
inverted. Pinned on both surfaces: the message says "one attempt more"
and never "fewer".

Claude-Session: https://claude.ai/code/session_01DhTqaEHqPVSVnAkjG3jywn
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/22343-retry-policy-try-catch-undeclared-keys-refused.md

@@ -25,6 +25,8 @@ Clause-②: yes (narrowing: an undeclared key on the shared retry policy is refu
 - A pre-17 `retryDelayMs` alone: still renamed to `backoffMs` before the judge at every door that converts first (`defineStack`, `os validate`, `os compile`, `registerFlow`, the save door). Met by a direct `FlowSchema.parse` or `defineFlow()`, it meets its tombstone, like every other retired spelling.
 - `Flow.errorHandling`, which carries the same policy keys, was already closed; a `script` node's retired keys keep the scope they had.
 
+**Also corrected:** `Flow.errorHandling`'s refusal of a `maxAttempts` key said a bare rename to `maxRetries` would run one attempt fewer than asked for; it runs one more (`maxAttempts: 3` is 3 runs, `maxRetries: 3` is 4), and the message now says so — the prescription, `maxRetries` one lower, is unchanged.
+
 ## FROM → TO
 
 | you wrote | write instead |

packages/spec/src/automation/flow.test.ts

@@ -1988,10 +1988,15 @@ describe('unknown keys are rejected, not stripped', () => {
         ...minimalFlow,
         errorHandling: { strategy: 'retry', maxAttempts: 3 },
       });
-      // Renaming alone would silently run one attempt FEWER than asked for:
-      // RetryConfig's `maxAttempts` counts the first try, `maxRetries` does not.
+      // Renaming alone would silently run one attempt MORE than asked for:
+      // RetryConfig's `maxAttempts` counts the first try, `maxRetries` does not,
+      // so `maxAttempts: 3` is 3 runs and a bare `maxRetries: 3` is 1 + 3 = 4.
+      // The consequence clause shipped inverted ("fewer") until the shared
+      // retry policy closed beside it with the right direction; pin both halves.
       expect(issue!.message).not.toContain('`maxAttempts` → `maxRetries`');
-      expect(issue!.message).toContain('maxAttempts - 1');
+      expect(issue!.message).toContain('`maxRetries: <maxAttempts - 1>`');
+      expect(issue!.message).toContain('one attempt more than you asked for');
+      expect(issue!.message).not.toMatch(/fewer/i);
     });
 
     it('errorHandling: the `strategy: retry` refinement still runs after the block is strict', () => {

packages/spec/src/automation/flow.zod.ts

@@ -1191,7 +1191,7 @@ export const FlowSchema = lazySchema(() => strictObject(
       maxAttempts:
         '`maxAttempts` is the connector/RetryConfig spelling and INCLUDES the first attempt; ' +
         'flow `errorHandling` counts retries AFTER it. Write `maxRetries: <maxAttempts - 1>` ' +
-        '— renaming the key alone would quietly run one attempt fewer than you asked for.',
+        '— renaming the key alone would quietly run one attempt more than you asked for.',
       fallback:
         'There is no fallback node on `errorHandling` (`fallbackNodeId` was removed in 17 — ' +
         'the engine never read it). Draw a per-node FAULT EDGE from the failing node ' +

packages/spec/src/shared/retry-policy.test.ts

@@ -180,6 +180,8 @@ describe('RetryPolicySchema refuses a key it does not declare', () => {
     const attempts = RetryPolicySchema.safeParse({ maxAttempts: 3 });
     const message = attempts.success ? '' : attempts.error.issues[0]!.message;
     expect(message).toContain('`maxRetries: <maxAttempts - 1>`');
+    expect(message).toContain('one attempt more than you asked for');
+    expect(message).not.toMatch(/fewer/i);
     expect(message).not.toContain('`maxAttempts` → ');
   });