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,19 +1,19 @@
# 2026-05-19-git-history-visualization
dir: 2026-05-19-git-history-visualization
# openspec/changes/archive/2026-05-19-git-history-visualization
dir: openspec/changes/archive/2026-05-19-git-history-visualization
index: 2026-05-19-git-history-visualization/.pi-map.index.md
index: openspec/changes/archive/2026-05-19-git-history-visualization/.pi-map.index.md
## role
Design and planning package for an interactive Git history visualization web application feature
Product specification and design documents for a planned Git history visualization feature, archived as historical project planning artifacts.
## 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
- design.md | Design document for a Git history visualization web application with backend API and frontend components | dep: Git CLI, SVG rendering engine, HTTP API framework, syntax highlighting library
- proposal.md | Product proposal document for building an interactive git history visualization tool
- tasks.md | Project task tracking document for building a Git history visualization feature with backend API, frontend components, page integration, and testing phases.
## arch
Specification-driven development with markdown-based design documents, OpenSpec schema configuration, and phased task-based project management
Document-driven specification pattern using OpenSpec metadata with phased task breakdown (backend API → frontend components → integration → testing) and dual design/proposal documentation structure.
## tags
git, history, design, visualization, .openspec, api, git cli, building
design, document, git, history, visualization, proposal, .openspec, backend
## symbols
-
## workflows