From 8c7f6ce775eb1501bba37bcef94e97899365414c Mon Sep 17 00:00:00 2001
From: fullsend-code
 <278716306+fullsend-ai-coder[bot]@users.noreply.github.com>
Date: Wed, 9 Sep 2026 09:51:11 +0000
Subject: [PATCH] docs(#4652): clarify changeset bump guidance for type changes

Refine the major/minor bump criteria in .fullsend/AGENTS.md to
distinguish between runtime-breaking and TypeScript-only-breaking
API changes. The previous guidance listed changed interfaces as
major, which caused the review agent to repeatedly flag minor bumps
on additive type changes that are TypeScript compile-time breaking
but runtime/JSON-compatible.

The updated guidance specifies major for changes that affect
runtime behavior or remove capabilities (removed exports, narrowed
types, removed fields), and minor as acceptable for additive or
widening type changes on public interfaces that maintain
runtime/JSON compatibility. This aligns with established repo
practice (e.g., PR #4582) and eliminates the ambiguity that
caused repeated false-positive missing-version-bump findings.

Closes #4652
---
 .fullsend/AGENTS.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/.fullsend/AGENTS.md b/.fullsend/AGENTS.md
index 5f3c203d1ad..b47787e6a3a 100644
--- a/.fullsend/AGENTS.md
+++ b/.fullsend/AGENTS.md
@@ -28,8 +28,14 @@ type:
 - `patch` for bug fixes, refactors, chores, and internal improvements
   with no user-facing behavior change.
 - `minor` for new features or capabilities visible to plugin consumers.
-- `major` for breaking API changes (removed exports, changed interfaces,
-  dropped support).
+- `major` for breaking API changes that affect runtime behavior or
+  remove existing capabilities (removed exports, narrowed types,
+  removed required fields, dropped support).
+- `minor` is also acceptable for additive or widening type changes
+  on `@public` interfaces that maintain runtime/JSON compatibility
+  (new optional or required fields on response types, type widening
+  from `string` to `string | null`). These changes are TypeScript
+  compile-time breaking but runtime-compatible.
 
 Match the bump level to the issue's stated intent (title prefix,
 constraints), not the size of the diff.