From 6865a42555c5ed42176ad06e5caaa3baff0b39e6 Mon Sep 17 00:00:00 2001 From: OpenAI Date: Tue, 2 Jun 2026 15:14:18 +0000 Subject: [PATCH] docs: close high namespace selector scope --- AI.md | 29 +++++++++++++++-------------- TODO.md | 31 +++++++++++++++++++++++++------ 2 files changed, 40 insertions(+), 20 deletions(-) diff --git a/AI.md b/AI.md index 956903a..efa5bf3 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 0212 +## Current handoff status after patch 0213 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 `0212`; -- latest expected patch name: `0212-docs-audit-namespace-lock-salvage-stubs.patch`. +- endpoint-audit/documentation patches `0199` through `0213`; +- latest expected patch name: `0213-docs-audit-namespace-later-generation-scope.patch`. When continuing in a new chat, first ask the user which patch was actually last -applied. If they confirm `0212`, build the next patch as `0213-...` against a -tree that already contains `0212`. If any patch failed or was skipped, rebuild +applied. If they confirm `0213`, build the next patch as `0214-...` against a +tree that already contains `0213`. If any patch failed or was skipped, rebuild against the last confirmed applied patch instead of assuming the file in `/mnt/data` was accepted. @@ -198,14 +198,15 @@ Schema/import direction: Latest endpoint audit note: -- Patch `0212` audits the next `NCP 0x2222/87` / wire `0x57` Name Space - lock/quota/search/salvage-rights subset from `87/36` through `87/43`. The - active source has no handlers for these selectors, so they are represented as - disabled `#if 0` stubs at the correct switch locations. `87/44` Update File - Handle Rights is documented as NetWare 5.x and is intentionally not added as - a source stub under the current 1.x/2.x/3.x plus planned-4.x scope. Next - patch should be `0213`; a likely next block is `87/64`..`87/69`, the parallel - `89` long namespace family, or another user-selected endpoint family. +- Patch `0213` closes the high-number `NCP 0x2222/87` / wire `0x57` + namespace/file selectors for the current audit scope. `87/44` Update File + Handle Rights and `87/64`..`87/69` Read/Write/Size/Physical-Record variants + are documented as later-generation NDK additions, so no source stubs are added + under the current 1.x/2.x/3.x plus planned-4.x rule. The in-scope `87` work + now ends with the documented `87/43` stubs from patch `0212`. Next patch + should be `0214`; likely next blocks are the `89` Enhanced Name Space family + as out-of-current-scope documentation, AFP `35`, or another user-selected + endpoint family. ## Patch workflow @@ -501,7 +502,7 @@ long-name-space family, or another unaudited top-level family such as AFP bindery/property/admin subfunction coverage, unless the user requests a specific family first. -The next patch number should be `0213` if `0212` was applied. +The next patch number should be `0214` if `0213` was applied. Retro source-stub checkpoint from patch 0207: diff --git a/TODO.md b/TODO.md index d0bee7d..4cd2069 100644 --- a/TODO.md +++ b/TODO.md @@ -192,9 +192,10 @@ Present in the code but not yet fully endpoint-audited: a compatibility shim block in `src/nwconn.c` and `src/namspace.c`; see the Extended Attribute section below for the exact per-subfunction status. - SDK `0x2222/87` / wire `0x57` Name Space is endpoint-audited for the - core `87/01`..`87/12` block; later `87/16+` salvage/metadata/namespace - subfunctions still need their own per-endpoint pass. SDK `0x2222/97` / - wire `0x61` Packet Burst, SDK `0x2222/101` / wire `0x65` Packet Burst + current 1.x/2.x/3.x plus planned-4.x scope. Later-generation high selectors + `87/44` and `87/64`..`87/69` are documented as out of current source-stub + scope. SDK `0x2222/97` / wire `0x61` Packet Burst, SDK `0x2222/101` / wire + `0x65` Packet Burst Connection Request, and SDK `0x2222/104` / wire `0x68` NDS/NCP fragger paths all have top-level code entries and need their own generation-bucketed audits before any new TODO stubs are added. @@ -1135,11 +1136,29 @@ Current status: 1.x/2.x/3.x plus planned-4.x scope. - These stubs are documentation-only and leave runtime behavior unchanged. +### Name Space group 0x2222/87 later-generation high selectors + +Current status: + +- The remaining SDK-listed high selectors in the `0x2222/87` / wire `0x57` + family are explicitly reviewed for scope rather than implemented or stubbed: + `87/44` Update File Handle Rights, `87/64` Read File, `87/65` Write to a + File, `87/66` Get Current Size of File, `87/67` Log Physical Record, `87/68` + Release Physical Record, and `87/69` Clear Physical Record. +- These selectors are later-generation NDK additions and are outside the current + 1.x/2.x/3.x plus planned-4.x source-stub rule. Do not add `#if 0` cases for + them during the current endpoint audit unless the project scope is explicitly + extended beyond NetWare 4.x. +- The older direct file-I/O calls (`65`..`77`) and old/new physical-record calls + already audited in `nwconn.c` remain the compatibility paths for the current + scope. + Follow-up: -- Continue the namespace audit with `87/64`..`87/69`, the matching `89` - long-name-space family, or another unaudited endpoint family requested by the - user. +- The `87` family is now closed for the current endpoint-audit scope. Continue + with the matching `89` Enhanced Name Space family as out-of-current-scope + documentation, AFP `35`, or another unaudited endpoint family requested by + the user. ### Retrospective source-stub coverage for already audited blocks