chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
@@ -1,14 +1,14 @@
|
||||
# 2026-05-19-git-control/specs
|
||||
dir: 2026-05-19-git-control/specs
|
||||
# openspec/changes/archive/2026-05-19-git-control/specs
|
||||
dir: openspec/changes/archive/2026-05-19-git-control/specs
|
||||
|
||||
index: 2026-05-19-git-control/specs/.pi-map.index.md
|
||||
index: openspec/changes/archive/2026-05-19-git-control/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines the API contract and UI specification for a Git version control interface that enables branch management, commits, remote sync, and merge operations.
|
||||
Defines REST API and frontend specifications for a Git version control interface with branch management, commit operations, remote sync, and merge capabilities
|
||||
## files
|
||||
- spec.md | Defines a REST API and frontend specification for a Git version control interface enabling branch management, commits, remote sync, and merge operations
|
||||
- spec.md | Defines a REST API and frontend specification for a Git version control interface with branch management, commit operations, remote sync, and merge capabilities
|
||||
## arch
|
||||
Specification-driven design using REST API documentation paired with frontend requirements, establishing clear interfaces between backend services and client implementation.
|
||||
Specification-driven design using Markdown-based API documentation with clear endpoint definitions, request/response schemas, and frontend UI component requirements
|
||||
## tags
|
||||
spec, defines, rest, api, frontend, specification, git, version
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user