docs(spec): propose PR153 platform maintenance backlog

docs/specs/CBG-PLAT-01/approvals/ci-only-s06-s08.md

@@ -0,0 +1,15 @@
+# CBG-PLAT-01 — CI-only S06–S08 implementation approval
+
+- Approved canonical specification: [spec.md at revision0.10](https://github.com/rabii-chaarani/codebaseGraph/blob/1a9db7b558b60248888408daa6268a3b45f2f0df/docs/specs/CBG-PLAT-01/spec.md), full Git commit `1a9db7b558b60248888408daa6268a3b45f2f0df`.
+- Canonical path: `docs/specs/CBG-PLAT-01/spec.md`; SHA-256 `13aa21bb99084865557b8f9db2d39d51298e27e28ce9f60c2c6de4b7ae540030`.
+- **Exact approved scope:** S06/COD-57/R06/A10 (watch help states existing parallel default), S07/COD-58/R07/A11 (COPY metadata fixture uses production-rendered Windows paths with unchanged four-byte oracle), S08/COD-59/R08/A12 (reference-epoch test observer recognizes fs2 Windows contention, retaining the five-second deadline and epoch/birth assertions). Verification and normal Git/PR delivery for these fixes are included.
+- User decision: **“I approve CI-only implementation scope”**, immediately answering the assistant's proposal to implement COD-57/COD-58/COD-59 first under the linked revision0.10 and rerun affected checks.
+- Source baseline rechecked before implementation: PR153 remains `862a8f88d485d5bd257ebd9456c194156fd4ee94` (3.0.4). Docs decisions live in PR155; do not substitute old review code or unrelated pending Scryer/resource-ceiling work.
+- **Excluded:** S01–S05, S09/S10 implementation, runtime packaging/dependencies, discovery/shim behavior, lock-mode changes, directory-cursor repair, broad qualification closure, unrelated specs, merge, deployment and live-service restarts. Existing D01–D05 policy decisions remain selected, not newly implemented by this approval.
+- Scryer ledger: `chg-pzt87f`, signed off for this exact fixes/docs/tests scope. No new responsibilities/topology are needed: these restore existing help/test contracts. The configured Scryer project is repository-bound rather than this PR worktree; no current-PR model implementation/reconciliation result is claimed.
+
+## Verification and closure limits
+
+Keep the source/library mutation behavior unchanged. Do not change production COPY SQL/parser/lock policy to accommodate invalid fixture inputs, delete meaningful assertions, increase the five-second observer deadline, bypass required CI, or mark Windows/platform qualification passed without execution. If real contention still exceeds the existing deadline, investigate and report it separately.
+
+Record actual source/binary hashes, environment, commands and results; distinguish local macOS checks from hosted Windows/native cohorts and from previously failed CI. Move only these implementation records to active/review states as evidence warrants. COD-51 remains the gate for all unapproved implementation slices; it is not globally completed by this subset approval. No aggregate milestone closure, merge/deployment or service restart is authorized.

docs/specs/CBG-PLAT-01/approvals/d05a-current-macos-only.md

@@ -0,0 +1,16 @@
+# D05a current-macOS-only amendment approval
+
+- Canonical path: `docs/specs/CBG-PLAT-01/spec.md`, revision **0.11**.
+- Approved full Git SHA: **`8a410c7a22f5291f06a1cece5cd9e7c0be255e72`**.
+- Immutable revision: https://github.com/rabii-chaarani/codebaseGraph/blob/8a410c7a22f5291f06a1cece5cd9e7c0be255e72/docs/specs/CBG-PLAT-01/spec.md
+- Exact scope: **D05a current stable macOS-only Apple Silicon qualification**, S03/COD-54 R03/A05 and corresponding S10/COD-61 R10/A15 macOS references; preserve A06 runtime integrity/failure checks and all unrelated requirements.
+- User decision reference:2026-10-27, this Prime Agent conversation. After the assistant explained that current hosted CI does not execute13.3 and proposed a separate minimum-version runner, the user said **“well then just drop it and keep only current”**. This explicit user-directed edit is recorded against its committed revision here.
+- Scryer amendment ledger: `chg-p0s0ar`; existing responsibilities unchanged, no new topology/claims.
+
+## Approved effect and limits
+
+Drop macOS13.3 execution and older-version support qualification. Keep only current stable macOS on Apple Silicon, with actual tested OS/build/source/final-installed-archive identities and existing runtime/isolation/failure evidence. Current-release hosted CI may supply that evidence when its actual OS and no-external-Homebrew/OpenSSL runtime conditions are demonstrated. The moving runner label or configured tests alone are not passing execution.
+
+Retain the existing13.3 deployment target and Mach-O metadata checks as implementation details; no product constants, library versions, Rust/workflow code or artifact bytes are changed by this amendment. Prior spec revisions, the original D05a decision and S03 implementation approval remain historical immutable records. The reviewed/tested product source remains `855c7e282a27de4afbad2d4252d7692de4b42ecb`; this approval changes qualification scope, not that execution identity.
+
+No new Windows/shell/source-install policy, other slice authorization, S09 disposition, signing/notarization decision, passing qualification assertion, issue/milestone closure, merge, publication, deployment or restart. Maintainer closure ownership is unchanged.

docs/specs/CBG-PLAT-01/decisions/d01-windows-runtime-bundling.md

@@ -0,0 +1,26 @@
+# D01 — Windows prebuilt runtime bundling decision
+
+## Approved scope and source proposal
+
+- Work: `CBG-PLAT-01/D01`; applies to S02/COD-53 and qualification S10/COD-61.
+- Canonical proposal: `docs/specs/CBG-PLAT-01/spec.md`, proposed revision0.1 at full Git commit `33360340379f878e93324e0829a1bb6f33eafc9d`, **D01 only**, not the full specification or its implementation.
+- Immutable proposal: https://github.com/rabii-chaarani/codebaseGraph/blob/33360340379f878e93324e0829a1bb6f33eafc9d/docs/specs/CBG-PLAT-01/spec.md#d01--windows-native-dependency-delivery
+- Decision reference: this conversation, immediately after the user asked to resolve the pending decisions together. The assistant asked whether the Windows archive should work without manual dependency installation and presented A (bundle required runtimes) versus B (external prerequisites). The user answered **“A”**.
+- Decision status: **policy approved**. Revision0.2 records that selection; it does not pretend the user approved the entire revised document.
+
+## Selected option A
+
+Windows **prebuilt releases** must bundle the compatible redistributable non-system runtime libraries required by the shipped programs and JSON/FTS extensions. Users should install/extract the archive and run it without separately installing OpenSSL or the required Visual C++ runtime.
+
+The selected option includes maintaining compatible redistributable libraries, license notices, checksums/integrity verification and application-controlled DLL loading. Larger downloads and additional release-maintenance responsibility were stated tradeoffs. Do not widen global PATH or add arbitrary caller-writable library fallback. Determine exact compatible versions/layout and safe loading mechanisms during authorized implementation; no specific DLL placement or API design was selected by the user.
+
+If licensing, ABI compatibility or redistribution prevents this option, report the blocker. Do not silently substitute the rejected manual-prerequisite experience.
+
+## What this does not approve
+
+- Implementation start or completion of COD-53/R02/A03–A04, source changes, a model implementation claim or passing platform qualification.
+- D02 macOS distribution, D03 discovery, D04 lock mode or D05 OS/PowerShell floors and **Cargo source-install policy**.
+- A general Windows self-contained/system-library guarantee beyond an explicit approved consumer baseline.
+- Dependency/extension ABI upgrades, global environment changes, automatic downloads, merge, deployment or live service restart.
+
+COD-51 stays Backlog as the broader exact-scope approval gate; COD-53/COD-61 remain unimplemented/unqualified. Existing issue blockers are not removed merely because one policy is now selected. Subsequent exact-slice implementation approval can reuse D01 without reopening it.

docs/specs/CBG-PLAT-01/decisions/d02-macos-openssl-bundling.md

@@ -0,0 +1,23 @@
+# D02 — macOS prebuilt OpenSSL dylib bundling decision
+
+## Approved scope and source proposal
+
+- Work: `CBG-PLAT-01/D02`; applies to S03/COD-54 and qualification S10/COD-61.
+- Canonical proposal: `docs/specs/CBG-PLAT-01/spec.md`, revision0.2 at full Git commit `18d4f1e2e1e59f8c8ac05f90e9c8982b0af6c00c`, **D02 policy only**, not the whole specification or implementation.
+- Immutable proposal: https://github.com/rabii-chaarani/codebaseGraph/blob/18d4f1e2e1e59f8c8ac05f90e9c8982b0af6c00c/docs/specs/CBG-PLAT-01/spec.md#d02--macos-openssl-delivery
+- Decision reference: this conversation, immediately after the D02 question offered A (bundle OpenSSL dylibs), B (static OpenSSL), or C (require Homebrew OpenSSL). The user answered **“A”**.
+- Decision status: **policy approved**. Revision0.3 records this selected option; the user did not approve the entire revised document.
+
+## Selected option A
+
+macOS **ARM64 prebuilt releases** bundle compatible redistributable OpenSSL dylibs. Users do not need Homebrew or a separately installed OpenSSL. Package the libraries with relative install names/runtime paths, license notices and checksums/integrity verification. The stated tradeoff is maintaining those libraries and their packaging while retaining the existing dynamic-linking design rather than a static-linking redesign.
+
+The exact supported library versions, archive layout, relative install-name/rpath strategy and tooling must be validated during authorized implementation. The final release archive, not only a debug executable, must be inspected and tested on a clean approved consumer baseline. Missing/corrupt/incompatible bundled libraries must fail clearly. If licensing, compatibility or redistribution prevents the selected policy, report a blocker rather than silently require Homebrew or switch to static linkage.
+
+## What this does not approve
+
+- Implementation start/completion for COD-54/R03/A05–A06, source changes, a model implementation claim or passing qualification.
+- D03 Windows discovery, D04 lock mode, or D05 OS/PowerShell floors and Cargo source-install policy.
+- Intel macOS/Linux support expansion, a dependency/extension ABI upgrade, global environment mutation, automatic downloads, merge, deployment or service restart.
+
+D01 remains approved independently. COD-51, COD-54 and COD-61 stay Backlog; no blocker or implementation gate is removed by this policy record alone. Reuse D02 in later exact-slice implementation approval without reopening the settled choice.

docs/specs/CBG-PLAT-01/decisions/d03a-windows-user-directory.md

@@ -0,0 +1,27 @@
+# D03a — Windows user-directory selection decision
+
+## Approved scope and proposal
+
+- Work: `CBG-PLAT-01/D03a`; S04/COD-55 and qualification S10/COD-61.
+- Proposal: `docs/specs/CBG-PLAT-01/spec.md`, revision0.3 at full Git commit `f0b0cdefbfd4d655a776a6c4d0ca8d326d56a2cd`, **Windows user-directory policy only**.
+- Immutable proposal: https://github.com/rabii-chaarani/codebaseGraph/blob/f0b0cdefbfd4d655a776a6c4d0ca8d326d56a2cd/docs/specs/CBG-PLAT-01/spec.md#d03--windows-discovery-precedence-and-command-kinds
+- Decision reference: this conversation, immediately after the D03a question offered A (native Windows profile default) versus B (HOME before Windows profile). The user answered **“A”**. The question explicitly deferred executable/.cmd handling.
+- Status: **directory policy approved**. Revision0.4 records the selection; the user did not approve the entire revised document or implementation start.
+
+## Selected option A
+
+Windows user-scoped MCP/client configuration follows this precedence:
+
+1. Explicit configuration-path option.
+2. Client-specific override, such as CODEX_HOME.
+3. Native Windows user-profile directory.
+
+Ignore Unix-style HOME for the default Windows location. If no valid directory can be found, fail clearly; never fall back to the current working directory or repository. Preserve deliberate client-specific overrides, explicit paths and project-scoped behavior. The selected tradeoff favors ordinary Windows profile behavior over Git Bash/HOME-first defaults; users retain explicit/client-specific overrides.
+
+The exact native profile-resolution API/library and validation are implementation details to verify later. This does not approve a new dependency, a policy for invalid relative overrides, a change to macOS discovery, or an incidental change to Ladybug's native extension-cache home.
+
+## Remaining limits
+
+D03b executable suffix discovery, supported .cmd/.bat client shims, safe invocation/quoting and verification remain **unresolved**. They are not approved by the directory choice. D04 lock mode and D05 consumer/OS/PowerShell/Cargo recipe remain open. D01 and D02 remain approved independently.
+
+COD-51, COD-55 and COD-61 remain Backlog; no implementation blocker is removed, and no implementation, merge, deployment, service restart or passing native qualification is claimed. Later exact-slice approval can reuse D03a without reopening the directory choice.

docs/specs/CBG-PLAT-01/decisions/d03b-windows-client-command-invocation.md

@@ -0,0 +1,23 @@
+# D03b — Windows client-command invocation decision
+
+## Approved scope and proposal
+
+- Work: `CBG-PLAT-01/D03b`; S04/COD-55 and qualification S10/COD-61.
+- Canonical proposal: `docs/specs/CBG-PLAT-01/spec.md`, revision0.4 at full Git commit `950b09618b33b103ef766b308bb9413010dd4133`, **Windows executable/client-shim policy only**.
+- Immutable proposal: https://github.com/rabii-chaarani/codebaseGraph/blob/950b09618b33b103ef766b308bb9413010dd4133/docs/specs/CBG-PLAT-01/spec.md#d03b--executable-suffix-and-batch-command-handling-open
+- Decision reference: this conversation, immediately after the D03b question offered A (native executables only) or B (native executables plus .cmd/.bat shims). The user first answered “A”, then immediately corrected it with **“no i meant B”**. The effective decision is **B**; it supersedes A. No native-only policy was committed.
+- Status: **command policy approved**. Revision0.5 records the corrected choice; this is not approval of the entire revised document or implementation start.
+
+## Selected option B
+
+Support native `.exe` clients and `.cmd`/`.bat` client shims used by ordinary Windows client installations. Use a dedicated Windows invocation adapter with separate, tested argument handling for native executables and batch scripts. Discovery, actual invocation and verification must agree on supported command kinds.
+
+Preserve spaced paths, arguments and explicit overrides. Do not introduce generic shell-command evaluation or blind shell fallback. Unsupported or unsafe inputs must fail clearly rather than execute ambiguously. This permits safe invocation of the supported client shim, not evaluation of arbitrary caller-provided command strings. Additional implementation/testing work was an explicit tradeoff.
+
+The exact adapter APIs, command-line encoding and compatibility behavior must be verified during authorized implementation. Native Windows tests must capture exact arguments through controlled `.exe`, `.cmd` and `.bat` fixtures and cover quoting/metacharacter boundaries and rejection paths. This choice does not approve a particular dependency or implementation.
+
+## Remaining limits
+
+D03a user-directory precedence remains approved independently; it is not changed by this correction. D01/D02 distribution choices also remain approved. D04 Direct lock-mode policy and D05 supported consumer/OS/PowerShell/Cargo-install recipe remain open.
+
+COD-51, COD-55 and COD-61 remain Backlog. This record does not remove implementation gates, authorize code changes, claim tests passed, approve merge/deployment/service restart, or select a generic shell framework. Later exact-slice implementation approval can reuse D03b without reopening the settled native-plus-shim choice.

docs/specs/CBG-PLAT-01/decisions/d04-windows-direct-exclusive-mode.md

@@ -0,0 +1,23 @@
+# D04 — Windows Direct-read exclusive-mode decision
+
+## Approved scope and proposal
+
+- Work: `CBG-PLAT-01/D04`; S09/COD-60 and its qualification/disposition in S10/COD-61.
+- Canonical proposal: `docs/specs/CBG-PLAT-01/spec.md`, revision0.5 at full Git commit `b62dd75fc490d81484e8d235a01a4bc55833f517`, **Windows Direct-read lock-mode policy only**.
+- Immutable proposal: https://github.com/rabii-chaarani/codebaseGraph/blob/b62dd75fc490d81484e8d235a01a4bc55833f517/docs/specs/CBG-PLAT-01/spec.md#d04--direct-read-lock-mode-contract
+- Decision reference: this conversation, immediately after D04 offered A (keep Exclusive and report it accurately) versus B (release/reacquire/revalidate to Shared). The user answered **“A”**.
+- Status: **policy approved**. Revision0.6 records the choice; the user has not approved the entire revised document or implementation start.
+
+## Selected option A
+
+For Windows Direct reads, retain the existing Exclusive lock and report/verify its actual Exclusive mode. Do not add a redundant Shared lock layer, an unlock/relock transition or a new concurrent-reader guarantee. The stated benefit is preserving current exclusion without introducing a transition race; the stated tradeoff is no concurrent-read improvement.
+
+Preserve publication/recovery safety, release behavior, and current macOS lock behavior. This choice does not approve applying Exclusive everywhere or changing the separate fresh-creation transition protocol. Exact code/API/name changes are implementation details, not preselected changes.
+
+Native Windows verification must show that an admitted read reports/holds Exclusive, both Shared and Exclusive second-handle attempts contend until release, and release permits intended later acquisition. Rerun affected Direct read/replay/writer-exclusion cases on Windows and macOS. No passing implementation test is claimed here.
+
+## Remaining limits
+
+COD-60 remains preexisting Low/P3 debt, not a cause of the currently failing CI. Selecting its policy does not silently include its implementation in a release or remove its approval gate. D01/D02/D03a/D03b remain approved independently; D05 consumer/OS/PowerShell/Cargo-install policy remains open.
+
+COD-51, COD-60 and COD-61 remain Backlog. No implementation start, source change, full-spec sign-off, qualification, merge, deployment or service restart is authorized. Later exact-slice approval may reuse this settled policy without reopening it.