chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
@@ -1,19 +1,19 @@
|
||||
# 2025-05-18-user-config-management
|
||||
dir: 2025-05-18-user-config-management
|
||||
# openspec/changes/archive/2025-05-18-user-config-management
|
||||
dir: openspec/changes/archive/2025-05-18-user-config-management
|
||||
|
||||
index: 2025-05-18-user-config-management/.pi-map.index.md
|
||||
index: openspec/changes/archive/2025-05-18-user-config-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and planning package for a JSONB-backed user configuration management feature with API and UI components.
|
||||
Design and specification package for a persistent user configuration management feature using PostgreSQL JSONB storage.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
||||
- design.md | Design document for a simple key-value user configuration system using PostgreSQL JSONB | dep: PostgreSQL, JSONB
|
||||
- proposal.md | Proposes a feature to add persistent user preference storage and management through a JSONB-backed config system with API endpoints and frontend settings UI. | dep: database, API, frontend, UserConfig model, AppShell
|
||||
- tasks.md | Project task tracking document for implementing a user settings/config feature with backend API, frontend UI, and verification steps | dep: SQLAlchemy, Alembic, FastAPI/HTTP endpoints, React/frontend router, Docker Compose, ruff, mypy, pytest, TypeScript tooling
|
||||
- .openspec.yaml | Defines an OpenAPI specification metadata file with schema type and creation date
|
||||
- design.md | Design document specifying a simple key-value user configuration system using PostgreSQL JSONB with merge semantics and lazy creation | dep: PostgreSQL, JSONB
|
||||
- proposal.md | Design proposal for implementing persistent user preferences and settings storage across sessions
|
||||
- tasks.md | Project task tracking document for implementing a user settings/config feature with backend API, frontend UI, and verification steps | dep: SQLAlchemy, Alembic, FastAPI/HTTP endpoints, React/frontend framework, Docker Compose, ruff, mypy, pytest, TypeScript
|
||||
## arch
|
||||
Specification-driven development using OpenSpec schema definitions, paired with markdown-based design documents (design.md, proposal.md, tasks.md) following a proposal → design → task breakdown workflow pattern.
|
||||
Specification-driven development with phased implementation (backend API → frontend UI → verification), using lazy-creation merge semantics for JSONB key-value preferences, tracked through OpenAPI metadata, design docs, proposals, and task breakdown.
|
||||
## tags
|
||||
design, user, jsonb, api, frontend, configuration, .openspec, document
|
||||
design, user, proposal, creation, .openspec, document, postgresql, jsonb
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
|
||||
Reference in New Issue
Block a user