Developer
070cd4d5a5
Add generated .pi-map.md and .pi-map.index.md files across the repository so the project navigation maps are shared and versioned. These artifacts are maintained by project_map_init/patch/validate and must be kept in sync with source edits. Note: .cache/ remains ignored (added in previous commit).
23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
# openspec/changes/archive/2026-05-19-git-history-visualization
|
|
dir: openspec/changes/archive/2026-05-19-git-history-visualization
|
|
|
|
index: openspec/changes/archive/2026-05-19-git-history-visualization/.pi-map.index.md
|
|
|
|
## role
|
|
Defines the specification and planning documents for a Git history visualization feature to be built in the project.
|
|
## files
|
|
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
|
- design.md | Design document specifying architecture, API endpoints, data models, and UI layout for a Git history visualization web application | dep: Git CLI, Backend API, Frontend (SVG rendering), JSON
|
|
- proposal.md | Proposes building an interactive git history visualization tool with graph and list views for exploring commit history, branches, and diffs | dep: git CLI, React, SVG
|
|
- tasks.md | Project task checklist for building a Git history visualization feature with backend API, frontend components, page integration, and testing phases | dep: Git, Python (backend), TypeScript/JavaScript (frontend), SVG, React/Vue (implied by component structure), HTTP API, Router
|
|
## arch
|
|
Document-driven specification pattern using OpenSpec schema with structured design docs (design.md, proposal.md, tasks.md) separating architecture definition, feature proposal, and implementation tracking.
|
|
## tags
|
|
git, history, design, visualization, .openspec, api, git cli, building
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|