chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
@@ -1,16 +1,16 @@
|
||||
# 2026-06-14-completed-specs-archive/user-config
|
||||
dir: 2026-06-14-completed-specs-archive/user-config
|
||||
# openspec/changes/archive/2026-06-14-completed-specs-archive/user-config
|
||||
dir: openspec/changes/archive/2026-06-14-completed-specs-archive/user-config
|
||||
|
||||
index: 2026-06-14-completed-specs-archive/user-config/.pi-map.index.md
|
||||
index: openspec/changes/archive/2026-06-14-completed-specs-archive/user-config/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines data specifications for a JSONB-based user preference configuration system with frontend theme integration.
|
||||
Defines a user configuration system specification for storing user preferences as JSONB key-value pairs with frontend integration
|
||||
## files
|
||||
- spec.md | Defines specifications for a user configuration system that stores JSONB key-value preferences, supports specific config keys, and integrates with frontend theme application. | dep: UserConfig, User, auth-oauth, pytest, mypy, ruff, npm
|
||||
- spec.md | Defines specification for a user configuration system that stores preferences as JSONB key-value pairs with frontend integration | dep: Database models (UserConfig, User), auth-oauth, pytest, mypy, ruff, npm typecheck, npm lint
|
||||
## arch
|
||||
Specification-driven schema design using JSONB key-value store with enumerated config keys and frontend theme mapping pattern.
|
||||
Specification-driven architecture using JSONB flexible schema pattern for key-value storage with frontend-backend contract definition
|
||||
## tags
|
||||
user, spec, defines, specifications, configuration, system, stores, jsonb
|
||||
spec, defines, specification, user, configuration, system, stores, preferences
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
|
||||
Reference in New Issue
Block a user