docs: align git-warp upgrade guidance (#312)

Author: flyingrobots

AGENTS.md

@@ -108,8 +108,8 @@ Your space. Write about whatever you want:
 
 ## 5. TECH STACK REFERENCE
 
-- **Runtime**: Node.js >= 20, ES modules
-- **Core dependency**: `@git-stunts/git-warp` (local path, CRDT graph on Git)
+- **Runtime**: Node.js >= 22, ES modules
+- **Core dependency**: `@git-stunts/git-warp` (published package, CRDT graph on Git)
 - **Plumbing**: `@git-stunts/plumbing` (must be installed as direct dependency)
 - **Tests**: vitest
 - **Style**: Plain JS with JSDoc, no TypeScript

CLAUDE.md

@@ -108,8 +108,8 @@ Your space. Write about whatever you want:
 
 ## 5. TECH STACK REFERENCE
 
-- **Runtime**: Node.js >= 20, ES modules
-- **Core dependency**: `@git-stunts/git-warp` (local path, CRDT graph on Git)
+- **Runtime**: Node.js >= 22, ES modules
+- **Core dependency**: `@git-stunts/git-warp` (published package, CRDT graph on Git)
 - **Plumbing**: `@git-stunts/plumbing` (must be installed as direct dependency)
 - **Tests**: vitest
 - **Style**: Plain JS with JSDoc, no TypeScript

CONTRIBUTING.md

@@ -55,9 +55,9 @@ GitHub milestones are not the primary planning surface for this repository.
 
 ## Prerequisites
 
-- Node.js >= 20.0.0
+- Node.js >= 22.0.0
 - Git
-- A local clone of [`@git-stunts/git-warp`](https://github.com/nicktomlin/git-warp) (git-mind depends on it via local path)
+- npm access to install published dependencies, including [`@git-stunts/git-warp`](https://github.com/nicktomlin/git-warp)
 
 ## Setup
 

GUIDE.md

@@ -64,7 +64,7 @@ cd git-mind
 npm install
 ```
 
-git-mind depends on `@git-stunts/git-warp`, which is currently installed from a local path. See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup details.
+git-mind depends on the published `@git-stunts/git-warp` package. See [CONTRIBUTING.md](CONTRIBUTING.md) for current development setup details.
 
 ### Verify the installation
 

TECH-PLAN.md

@@ -20,7 +20,7 @@ The key insight: **Git is already a graph database.** It has an immutable object
 
 ## 2. Storage Layer: git-warp
 
-git-mind delegates persistence to **@git-stunts/git-warp** (v10.3.2), a CRDT graph database that uses Git's object store as its backend.
+git-mind delegates persistence to **@git-stunts/git-warp**. The specific version in use is defined in [package.json](package.json); this historical document originally described the `v10.3.2` era of the substrate.
 
 ### How data gets stored
 

docs/design/git-warp-upgrade-audit.md

@@ -1,6 +1,6 @@
 # git-warp Upgrade Audit
 
-Status: draft for execution
+Status: active execution on `feat/git-warp-upgrade-audit`
 
 Related:
 
@@ -29,7 +29,7 @@ It is a boundary audit plus upgrade cycle.
 
 ## Context
 
-Current local dependency state:
+Cycle starting state:
 
 - declared in `package.json` as `^11.5.0`
 - locked and installed at `11.5.0`
@@ -38,7 +38,11 @@ Live npm registry state checked on 2026-03-25:
 
 - latest published `@git-stunts/git-warp` version: `14.16.2`
 
-That means Git Mind is currently three major versions behind the latest published package.
+Chosen upgrade target for this cycle:
+
+- `14.16.2`
+
+That means this cycle upgrades Git Mind across three major versions of the substrate.
 
 This does not automatically mean "upgrade immediately no matter what."
 It does mean Git Mind should not keep expanding Hill 1 behavior without auditing the real upgrade surface first.
@@ -106,9 +110,13 @@ The upgrade should pay special attention to:
 
 ## Known Mismatches Already Exposed
 
-At least one contributor-facing document still says Git Mind depends on git-warp via a local path.
+This cycle exposed one concrete runtime compatibility change:
+
+- `graph.getNodeProps()` now returns plain objects rather than `Map` instances
+
+Git Mind must treat node property bags as a compatibility boundary rather than assuming a single container shape.
 
-That no longer matches the actual package metadata and should be corrected as part of this cycle.
+This cycle also started with contributor-facing docs that still claimed git-warp was installed via local path. Those docs should be corrected as part of the upgrade.
 
 ## Acceptance Criteria