Git Explorer

# Interactive Git & Structure Visualizer

**Goal:** Create a highly interactive single-page HTML application that visualizes the Git branching topology (the DAG) by integrating external structural events directly into the commit history. The application must demonstrate how specific contextual markers relate precisely to specific points in the code development process.

## 1. Technology Stack
* **Frontend:** HTML5, CSS3, JavaScript (ES6+).
* **Visualization Library:** Use **D3.js** or a similar powerful library for rendering interconnected data structures and spatial relationships simultaneously.
* **Persistence:** Use `localStorage` to ensure all application state is saved across refreshes.

## 2. Data Model Requirements

The application must manage two fundamental, interconnected data sets: Git history (the structure) and external contextual events (the associations).

### A. Git History (The Structure)
1. **Commits:** The primary nodes of the graph. Each commit must store:
    * A unique ID.
    * A list of parent commit IDs (defining the DAG structure).
    * A specific anchor point for spatial placement.
2. **Branches:** Track current branch names and their pointers to the latest commit.

### B. External Contextual Events (The Associations)
1. **Events:** External structural markers that provide context. Each event must store:
    * A descriptive Title (e.g., "Code Freeze," "Feature Completion").
    * An identifying reference for spatial placement.
    * **Association ID:** A mandatory field linking the event to a specific Git commit ID where it occurred.

## 3. Functional Requirements

The application must provide tools to manage both data sets and render their synthesized view.

### A. Data Management (CRUD Operations)
* **Git History Management:** Provide full functionality to create, edit, delete commits, branches, and tags to build the branching structure.
* **Event Management:** Allow users to add new contextual events and explicitly associate them with existing Git commits or branches.

### B. Visualization Requirements (The Synthesis)
The visualization must fuse the structural history and the external context into a single view:

1. **Primary View (Git Graph):** Render the standard network graph showing all commits and their merging paths.
2. **Integrated Anchoring:** All External Contextual Events must be visually anchored directly onto their corresponding Git Commit nodes on the graph. This establishes a direct spatial link between the code structure and the contextual marker.
3. **Contextual Flow Display:** A secondary view should display all contextual events, allowing for overall structural context.
4. **Interactivity & Synchronization:**
    * Selecting a commit on the Git graph must highlight its associated anchored contextual marker.
    * Hovering over an anchor must reveal the full details of the external event and confirm the specific Git commit it is linked to.

## 4. Data Handling and Persistence
* **Import Feature:** Implement functionality to import initial Git commit data and associated Contextual Events.
* **Local Storage State:** The complete, unified state of both Git history and contextual events must be serialized and saved to `localStorage`, ensuring full persistence across sessions.