chore: patch project maps after stale backend test cleanup
Regenerate .pi-map*.md artifacts for source changes in: - apps/api/src/api/tool/tool_types_validation.py - apps/api/src/schemas/tool/tool_type.py - apps/api/tests/integration/test_tool_types_api_extended.py - and all affected test files from backend-frontend refactoring cleanup
This commit is contained in:
@@ -4,13 +4,13 @@ dir: .stoneforge
|
||||
index: .stoneforge/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Hidden system directory storing runtime state, configuration, and version-control metadata for the Stoneforge application.
|
||||
Internal configuration and state tracking directory for the Stoneforge application
|
||||
## files
|
||||
- .dashboard-opened | Stores timestamp and identifier data for tracking when a dashboard was opened
|
||||
- .gitignore | Specifies files and patterns for Git to ignore in version control
|
||||
- config.yaml | Configuration file for the Stoneforge application defining database, sync, playbook, identity, merge, workflow, and agent settings.
|
||||
## arch
|
||||
Simple flat-file storage with YAML-based configuration, dotfile-based state tracking, and standard Git ignore patterns.
|
||||
Simple dot-directory pattern storing metadata (.dashboard-opened), version control exclusions (.gitignore), and hierarchical YAML configuration (config.yaml) with domain-separated settings
|
||||
## tags
|
||||
config, stores, timestamp, identifier, data, tracking, dashboard, was
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user