chore: patch project maps for multi-session-terminal-ux metadata updates

openspec/changes/.pi-map.md

@@ -1,27 +1,13 @@
-# .
-dir: .
+# openspec/changes
+dir: openspec/changes
 
-index: ./.pi-map.index.md
-
-## Project Map Protocol
-
-1. Read this protocol and the root `.pi-map.index.md` first.
-2. Use `index:` / `map:` references to open relevant directory indexes and maps.
-3. Load indexes before rich maps during task-start navigation.
-4. Read the local rich map and actual source before editing.
-5. Treat non-empty `## dirty` sections in either artifact as stale.
-6. If source and generated artifacts disagree, trust source.
-7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
-8. After editing source, run `project_map_patch` for each changed file.
-9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
-
-Trust boundary: index routes, map orients, source decides.
+index: openspec/changes/.pi-map.index.md
 
 ## role
-Empty root directory awaiting package initialization or content.
+Tracks and manages specification changes/versions for OpenAPI documents
 ## files
 ## arch
-N/A - no files or architectural patterns present to analyze.
+Simple data structure package with record types for change metadata, likely used by diff/merge tooling
 ## tags
 -
 ## symbols