headquarter/openspec/changes/tool-config-mount-cleanup/.pi-map.md

.

dir: .

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.

role

Package containing completed specification, proposal, and task tracking for a tool configuration mount cleanup feature that separates built-in tool definitions from user-specific configuration.

files

• .openspec.yaml | Defines a completed OpenSpec configuration for a tool named "tool-config-mount-cleanup"
• proposal.md | Proposes removing configuration and state mounts from built-in tool definitions to separate tool setup from user-specific configuration handled by config profiles.
• tasks.md | This is a completed task checklist for modifying built-in tool configurations and database migrations in a codebase. | dep: alembic, pytest, opencode, pi-agent

arch

Documentation-driven change management with OpenSpec configuration, markdown-based proposal/justification, and structured task checklist for tracking implementation of a configuration separation pattern.

tags

tool, configuration, completed, config, .openspec, proposal, tasks, defines

symbols

workflows

dirty