chore: seed BuildPulse v0.1 documentation package

docs/PARKING_LOT.md

@@ -0,0 +1,222 @@
+# BuildPulse Parking Lot
+
+This file contains useful ideas that are intentionally not part of v0.1.
+Parking ideas is a success behavior, not a failure.
+
+## AI Idea Triage
+
+Description:
+Use AI to classify new ideas into Now, Next, Later, Parking Lot, or Reject.
+
+Reason parked:
+Manual workflow should be proven first.
+
+Possible version:
+v0.2
+
+Risk:
+Medium
+
+## AI Scope Creep Detection
+
+Description:
+AI reviews a proposed feature and warns if it violates current scope.
+
+Reason parked:
+Requires AI integration and context handling.
+
+Possible version:
+v0.2
+
+Risk:
+Medium
+
+## Acceptance Criteria Generator
+
+Description:
+AI generates testable acceptance criteria for a feature card.
+
+Reason parked:
+Useful but not needed for manual v0.1.
+
+Possible version:
+v0.2
+
+Risk:
+Low
+
+## Phases and Releases
+
+Description:
+Add formal project phases and release planning.
+
+Reason parked:
+v0.1 only needs Now/Next/Later/Done.
+
+Possible version:
+v0.3
+
+Risk:
+Medium
+
+## Session View
+
+Description:
+Add a dedicated session timer and session dashboard.
+
+Reason parked:
+In v0.1, sessions are represented as Pulse events.
+
+Possible version:
+v0.4
+
+Risk:
+Medium
+
+## Claude/Codex Prompt Generator
+
+Description:
+Generate ready-to-paste prompts for Claude Code, Codex, OpenCode, or OpenClaw based on selected feature.
+
+Reason parked:
+Requires feature plan and export to work first.
+
+Possible version:
+v0.4
+
+Risk:
+Low
+
+## Local/Cloud AI Router
+
+Description:
+Track which AI tasks should use local LLMs vs cloud providers.
+
+Reason parked:
+Important later, but not required for planning cockpit v0.1.
+
+Possible version:
+v0.5
+
+Risk:
+High
+
+## Local Model Capability Lab
+
+Description:
+Track local models, hardware, use cases, speed, quality, and recommended tasks.
+
+Reason parked:
+Useful but could become a distraction before BuildPulse is useful.
+
+Possible version:
+v0.5
+
+Risk:
+High
+
+## File-Backed Storage
+
+Description:
+Store features as JSON files and pulses as JSONL on disk.
+
+Reason parked:
+More future-compatible with agents, but browser local storage is faster for v0.1.
+
+Possible version:
+v0.6 or earlier if explicitly chosen.
+
+Risk:
+Medium
+
+## Real Agent Pulse Ingestion
+
+Description:
+Allow external agents/tools to submit Pulse events via API.
+
+Reason parked:
+This is the beginning of the actual Agent Pulse framework and should not be built before manual pulse workflows are proven.
+
+Possible version:
+v1.0
+
+Risk:
+High
+
+## WebSocket Timeline
+
+Description:
+Show live agent activity in real time.
+
+Reason parked:
+Requires backend/event infrastructure.
+
+Possible version:
+v1.0+
+
+Risk:
+High
+
+## GitHub/Gitea Integration
+
+Description:
+Link pulses/features to commits, branches, issues, and PRs.
+
+Reason parked:
+Useful later but not needed for v0.1.
+
+Possible version:
+v1.0+
+
+Risk:
+Medium
+
+## OpenClaw/Hermes Integration
+
+Description:
+Read OpenClaw/Hermes heartbeats, agent status, and task outputs into BuildPulse.
+
+Reason parked:
+Important long-term, but too complex for v0.1.
+
+Possible version:
+v1.0+
+
+Risk:
+High
+
+## Multi-Project Support
+
+Description:
+Allow multiple projects in the same BuildPulse instance.
+
+Reason parked:
+Single-project workflow should be proven first.
+
+Possible version:
+v0.6+
+
+Risk:
+Medium
+
+## Full Agent Pulse Framework
+
+Description:
+Event-driven autonomous agent observability and coordination layer.
+Includes:
+- Append-only event log
+- Agent ownership
+- Handoff protocol
+- Progress engine
+- Safety gates
+- WebSockets
+- Plugin system
+
+Reason parked:
+This is the end-state architecture, not the first build.
+
+Possible version:
+v2.0
+
+Risk:
+Dangerous