chore(project-map): regenerate .pi-map artifacts across the repo

This commit is contained in:
Developer
2026-06-17 11:31:24 +00:00
parent 0dd5f2317b
commit 93da9b42a2
683 changed files with 5075 additions and 4965 deletions
@@ -1,20 +1,20 @@
# 2026-05-17-project-management
dir: 2026-05-17-project-management
# openspec/changes/archive/2026-05-17-project-management
dir: openspec/changes/archive/2026-05-17-project-management
index: 2026-05-17-project-management/.pi-map.index.md
index: openspec/changes/archive/2026-05-17-project-management/.pi-map.index.md
## role
Defines specifications, design, and implementation tracking for a full-stack project management feature with authenticated CRUD, ownership enforcement, and SSH key integration.
Archive of design documents for a full-stack project management feature implementing authenticated CRUD operations with ownership enforcement.
## files
- .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
- README.md | Defines a project management application that implements create, read, update, delete, listing, and ownership workflows across API and frontend layers
- design.md | Design document specifying authenticated project CRUD implementation with ownership rules, default SSH key support, and frontend integration. | dep: auth-oauth, frontend-foundation, backend API routes, JWT, project service layer, repository associations, SSH key system
- proposal.md | Proposes a project management feature implementation covering authenticated CRUD APIs, frontend flows, SSH key integration, and cascading deletion behavior. | dep: authentication, data models, frontend foundation, apps/api/src, apps/web/src
- tasks.md | Tracks completed tasks for implementing full-stack project management features with ownership enforcement and verification checks.
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
- README.md | Describes a project management system implementing CRUD operations, listing, and ownership workflows across API and frontend layers.
- design.md | Design document specifying authenticated project CRUD implementation connecting backend and frontend with ownership/security rules | dep: auth-oauth, frontend-foundation, JWT, project service layer, repository associations, SSH keys
- proposal.md | Proposes implementation of end-to-end project management functionality with authentication, ownership enforcement, and SSH key integration across backend and frontend. | dep: apps/api/src, apps/web/src, authentication, data models, SSH keys, repositories
- tasks.md | A task tracking document for implementing full-stack project management functionality with ownership enforcement, covering backend API, frontend flows, and verification steps.
## arch
Documentation-driven specification pattern using OpenAPI metadata, layered design docs (proposal → design → tasks), and separation of concerns across API/backend and frontend concerns with explicit ownership-based access control.
Specification-driven development using OpenSpec schema with phased implementation tracking across backend API, frontend UI, and security layers (SSH key integration, ownership rules).
## tags
project, frontend, management, ownership, design, tasks, defines, .openspec
frontend, project, ownership, management, api, design, backend, .openspec
## symbols
-
## workflows