From e5fd1e9218be422633b86aea41691f5297f69de9 Mon Sep 17 00:00:00 2001 From: test Date: Tue, 2 Jun 2026 14:17:06 +0000 Subject: [PATCH] docs: audit existing source stub coverage --- AI.md | 43 +++++++++++++++++++++++++++++++++---------- TODO.md | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 65 insertions(+), 10 deletions(-) diff --git a/AI.md b/AI.md index ac0cf8a..9e86e3f 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 0206 +## Current handoff status after patch 0207 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 `0206`; -- latest expected patch name: `0206-docs-retrofit-stub-scope-notes.patch`. +- endpoint-audit/documentation patches `0199` through `0207`; +- latest expected patch name: `0207-docs-audit-existing-source-stub-coverage.patch`. When continuing in a new chat, first ask the user which patch was actually last -applied. If they confirm `0206`, build the next patch as `0207-...` against a -tree that already contains `0206`. If any patch failed or was skipped, rebuild +applied. If they confirm `0207`, build the next patch as `0208-...` against a +tree that already contains `0207`. If any patch failed or was skipped, rebuild against the last confirmed applied patch instead of assuming the file in `/mnt/data` was accepted. @@ -436,13 +436,14 @@ user.org.mars-nwe.afp.prodos-info=0x010203040506 ## Latest endpoint audit checkpoint -As of patch `0206-docs-retrofit-stub-scope-notes.patch`, the latest +As of patch `0207-docs-audit-existing-source-stub-coverage.patch`, the latest audited endpoint block is still the old direct file-I/O group in `src/nwconn.c`. Patch 0204 is a style follow-up to 0203: it splits the request/reply/coverage notes so each endpoint documents its own audit directly at its `case` label. -Patches 0205 and 0206 only clarify the missing-endpoint stub scope: source -stubs are for 1.x/2.x/3.x compatibility gaps and planned 4.x gaps, not for -NetWare 5.x/OES/MOAB/newer endpoints during the current audit. +Patches 0205 and 0206 clarify the missing-endpoint stub scope: source stubs are +for 1.x/2.x/3.x compatibility gaps and planned 4.x gaps, not for NetWare +5.x/OES/MOAB/newer endpoints during the current audit. Patch 0207 then +retro-checks the already touched families against that source-stub rule. The last audited endpoint block contains: @@ -465,7 +466,29 @@ 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 `0207` if `0206` was applied. +The next patch number should be `0208` if `0207` was applied. + + +Retro source-stub checkpoint from patch 0207: + +- Already documented eligible gaps in Directory Services `22/12`, `22/35`, and + `22/36` have disabled source stubs at the correct `src/nwconn.c` dispatch + slots. Do not rewrite those stubs unless implementing the endpoint. +- Already documented File Server Environment `23` queue/server-management gaps + have disabled source stubs at the appropriate `src/nwbind.c` switch slots. + Some pre-existing disabled stubs still contain legacy placeholder control flow; + leave existing stubs alone unless implementing or explicitly cleaning that + exact block. +- Message `21/04`..`21/08` were not SDK/PDF server endpoints in the default + audit set, so no stubs are required. Message `21/12` is later-generation + only and remains prose-only/out-of-scope under the current rules. +- Physical-record `26`..`31` plus `110`, TTS `34/00`..`34/10`, and direct file + `59`, `61`..`77` do not have additional eligible missing slots in the audited + ranges; no new source stubs were needed. +- Future retro-audits must distinguish three cases: add a disabled source stub + for an eligible missing endpoint, leave an already-present stub unchanged and + only document that it exists, or keep non-endpoints / 5.x+ endpoints out of + source. 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 diff --git a/TODO.md b/TODO.md index 4571f55..8048899 100644 --- a/TODO.md +++ b/TODO.md @@ -999,6 +999,38 @@ Follow-up: handle should remain compatibility padding or participate in a future handle table expansion. + +### Retrospective source-stub coverage for already audited blocks + +Current status: + +- The endpoint-stub scope is source-level as well as documentation-level. When + an already audited family has a documented 1.x/2.x/3.x compatibility gap or a + planned 4.x gap, the dispatcher should contain a disabled `#if 0` slot marker + at the correct numeric case, unless that slot is already active. +- Retro-check of the already touched families found the known eligible stubs + already present in source: + - Directory Services `22/12` / wire `0x0c`, `22/35` / wire `0x23`, and + `22/36` / wire `0x24` are disabled source stubs in `src/nwconn.c`. + - File Server Environment `23` queue/server-management gaps that were + previously documented as disabled stubs are present in `src/nwbind.c`. +- No source stubs are needed for message `21/04`..`21/08` because they were not + default-compatibility server endpoints in the checked SDK/PDF/WebSDK material. + `21/12` remains later-generation only and should stay out of source under the + current through-4.x planning scope. +- Physical-record `26`..`31` plus `110`, TTS `34/00`..`34/10`, and direct file + commit/search/I/O `59`, `61`..`77` did not expose additional eligible missing + slots during the retro-check. + +Follow-up: + +- For each next endpoint-family patch, record the source outcome inline: active + case, already-present disabled stub, newly added disabled stub, no server + endpoint, or later-generation/out-of-scope. +- If a disabled stub already exists, do not churn its code merely to restyle it; + add or adjust prose only unless the user explicitly asks for cleanup or the + endpoint is being implemented. + ### AFP / Mac namespace backend Current status: