diff --git a/AI.md b/AI.md
index 0a40771..ca44d84 100644
--- a/AI.md
+++ b/AI.md
@@ -11,18 +11,18 @@ When the user says this is a new chat or asks to continue mars-nwe work, first
 read this file before proposing patches or making assumptions.  Then ask for, or
 use, the current project status that the user pasted into the chat.
 
-## Current handoff status after patch 0203
+## Current handoff status after patch 0205
 
 The current accepted patch line in this chat is expected to include:
 
 - endpoint-audit/documentation patches through `0176-docs-audit-direct-lifecycle-buffer-endpoints.patch`;
 - redesign documentation patches `0177` through `0198`;
-- endpoint-audit/documentation patches `0199` through `0203`;
-- latest expected patch name: `0203-docs-audit-old-direct-file-io-endpoints.patch`.
+- endpoint-audit/documentation patches `0199` through `0205`;
+- latest expected patch name: `0205-docs-clarify-missing-endpoint-stub-scope.patch`.
 
 When continuing in a new chat, first ask the user which patch was actually last
-applied.  If they confirm `0203`, build the next patch as `0204-...` against a
-tree that already contains `0203`.  If any patch failed or was skipped, rebuild
+applied.  If they confirm `0205`, build the next patch as `0206-...` against a
+tree that already contains `0205`.  If any patch failed or was skipped, rebuild
 against the last confirmed applied patch instead of assuming the file in
 `/mnt/data` was accepted.
 
@@ -460,7 +460,7 @@ for example AFP `0x2222/35`, EA `0x2222/86`, namespace `0x2222/87`, packet
 burst `0x2222/97`/`101`, or resume deeper `0x2222/23` bindery/property/admin
 subfunction coverage, unless the user requests a specific family first.
 
-The next patch number should be `0205` if `0204` was applied.
+The next patch number should be `0206` if `0205` was applied.
 
 Remember: for every new endpoint-audit patch, also update this AI handoff file
 with the latest audited block and expected next patch number.  Put detailed
@@ -468,10 +468,15 @@ Coverage/Request/Reply/Known-difference notes inline at each endpoint case rathe
 than as one large audit block before the switch range.
 
 Missing-endpoint rule: when an audited SDK/PDF/WebSDK/Header endpoint is not
-implemented, document it at the appropriate dispatch location as a disabled
-`#if 0` stub instead of only mentioning it in prose.  This also applies to
-later NetWare 4.x/5.x/OES endpoints that are intentionally out of the default
-3.x-compatible runtime: add a clearly disabled stub with the selector path,
-name, request/reply sketch, provider/out-of-scope reason, and no active behavior
-change.  Disabled stubs must not use misleading control flow such as `return(-1)`
-where that return value has no local handoff meaning.
+implemented but belongs to the compatibility scope, document it at the
+appropriate dispatch location as a disabled `#if 0` stub instead of only
+mentioning it in prose.  The compatibility scope for stubs is NetWare 1.x/2.x
+legacy calls, NetWare 3.x/default compatibility calls, and explicitly planned
+NetWare 4.x/NDS work.  Do not add stubs merely for NetWare 5.x/OES/MOAB/newer
+endpoints: those are outside the current target unless the user explicitly asks
+for that later generation.  A 3.x-compatible server should remain compatible
+with documented 1.x/2.x calls, and the current forward plan is only through
+4.x.  Disabled stubs should include selector path, name, request/reply sketch,
+provider/out-of-scope reason, and no active behavior change.  Disabled stubs
+must not use misleading control flow such as `return(-1)` where that return
+value has no local handoff meaning.