Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(windows): add the Experimental→Supported tier exit-criterion checklist (#758)
AkitaOnRailsed0a28da3947
diff --git a/docs/windows.md b/docs/windows.mdindex 4c853085..2d7fa837 100644--- a/docs/windows.md+++ b/docs/windows.md@@ -578,6 +578,62 @@ ai-memory treats both as normal lock-busy states, so concurrent drains wait,skip, or expire according to the same spool timing rules instead of failing thehook.+<!-- BEGIN: windows-tier-exit-criteria -->+## Support Tier: Experimental → Supported Exit Criteria++Native Windows is currently an **Experimental** tier. This is the checklist a+maintainer uses to decide whether it can be promoted to **Supported** — it is a+status inventory, not a promotion. Nothing here claims the tier has changed.+Each item is marked **done**, **in-progress**, or **deferred-pending-policy**,+from what the repository actually ships today.++- **CI trigger coverage — done.** `.github/workflows/windows.yml` runs on a+ nightly `schedule`, on `workflow_dispatch`, and on pull requests. A pull+ request that touches platform-sensitive code (path handling, file locking,+ git plumbing, the hook bundle — `crates/ai-memory-{wiki,store,hooks}/**`,+ `crates/ai-memory-cli/src/commands/install_hooks.rs`, `hooks/**`,+ `tests/hooks/**`, and the workflow itself) now opts in automatically via the+ workflow's leading `changes` job (`dorny/paths-filter`, SHA-pinned); the+ `windows` label remains a manual override for PRs outside those paths. The+ tier promise no longer depends on a human remembering the label.++- **Hook-bundle Windows job — done.** The `hooks` job in `windows.yml` runs+ `tests/hooks/test_lib.sh` on `windows-latest`. That suite drives+ `hooks/lib/ai-memory-hook.ps1`, whose PowerShell branch only ever executes+ natively on Windows — so the one platform its PowerShell code is written for+ is now exercised in CI rather than only on a contributor's box.++- **`#[cfg(windows)]` regression coverage — in-progress.** The Windows-only+ regression tests that no Linux/macOS leg can compile run here: the drain-lock+ `ERROR_LOCK_VIOLATION` busy-state handling, the libgit2 path-resolution+ fallback to the Git CLI when opening a freshly initialized wiki repository,+ and verbatim (`\\?\`) path handling (see the header of `windows.yml` and+ Scenario D above). This coverage exists for the platform code that has hit a+ documented bug; it stays **in-progress** because each new Windows path-,+ lock-, or git-touching change is expected to add its own `#[cfg(windows)]`+ regression before promotion, not because the current tests are absent.++- **`.exe` code-signing — deferred-pending-policy.** Release binaries and the+ `build.rs` helper executables Cargo emits are unsigned. On machines enforcing+ **App Control for Business** or **Smart App Control**, unsigned binaries run+ from user-writable directories are blocked — this is the `os error 4551`+ build failure documented in Scenario D, and it can equally block an unsigned+ released `ai-memory.exe`. Signing needs a code-signing certificate and a+ decision on how its private material is held as a CI secret (and rotated).+ Both are maintainer/policy calls, so this item is deferred until that+ decision is made; it is a blocker for a frictionless Supported experience on+ Application-Control-enforced fleets.++- **Native `ai-memory upgrade` path — in-progress.** A first-class in-place+ upgrade for native Windows installs (release-binary and wrapper flows) is+ tracked in #801/#802. Until it lands, upgrading is the manual+ download/extract/re-`install-hooks` sequence in Scenarios B and C.++Promotion to Supported is the maintainer's decision once the in-progress items+are closed and the deferred code-signing policy is resolved (or explicitly+accepted as out of scope for the tier).+<!-- END: windows-tier-exit-criteria -->+## Current Harness CaveatsWindows hook support is new and needs real-world testing against native