chore: track all project map and index files

Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).

openspec/changes/archive/2026-05-24-terminal-startup-and-container-tools/.pi-map.md

@@ -0,0 +1,22 @@
+# openspec/changes/archive/2026-05-24-terminal-startup-and-container-tools
+dir: openspec/changes/archive/2026-05-24-terminal-startup-and-container-tools
+
+index: openspec/changes/archive/2026-05-24-terminal-startup-and-container-tools/.pi-map.index.md
+
+## role
+Design and planning package for implementing customizable terminal startup commands and productivity tools in a WebSocket-based container terminal system
+## files
+- .openspec.yaml | Defines an OpenSpec configuration file with schema version and creation date metadata
+- design.md | Design specification for adding per-tool-type terminal startup commands and productivity utilities to a WebSocket-based container terminal system | dep: tool-types-definition, tool-terminal, opencode-web-server, tool-config-management, Docker, WebSocket, bash, Docker Compose
+- proposal.md | Proposes adding customizable startup commands to terminal tool types and productivity tools to the OpenCode container
+- tasks.md | Task tracking checklist for implementing a `startup_command` feature across database, backend API, terminal execution, frontend, and container tooling | dep: Alembic, SQLAlchemy, Pydantic, FastAPI, WebSocket, bash/tmux/ranger, npm, pytest, mypy, ruff
+## arch
+Specification-driven development using OpenSpec schema with phased task tracking across full-stack implementation (database → API → execution → frontend → container tooling)
+## tags
+tool, terminal, design, startup, websocket, container, .openspec, adding
+## symbols
+-
+## workflows
+-
+## dirty
+-