docs(gsd): bootstrap planning and phase-1 discussion artifacts

.planning/PROJECT.md

@@ -0,0 +1,14 @@
+# ActivityWatch-Russian
+
+## Current Milestone: v1.0 Data Pipeline Stability
+
+**Goal:** Ensure stable collection and rendering of endpoint activity data in AW Web UI.
+
+**Target features:**
+- Reliable ingestion from Windows collectors (`endpoint-signals`, `browser-domains`).
+- Stable AW server query/render path for worktime/activity pages.
+- Deployment/runbook consistency (Ansible + install kit + rollback notes).
+
+## Evolution
+
+This document evolves at phase transitions and milestone boundaries.

.planning/ROADMAP.md

@@ -0,0 +1,14 @@
+# ROADMAP
+
+## 🚧 v1.0 Data Pipeline Stability
+
+- [ ] Phase 1: Collectors and API flow hardening
+- [ ] Phase 2: UI reports consistency and release proof
+
+### Phase 1: Collectors and API flow hardening
+**Goal:** Stabilize collectors-to-server pipeline and remove known transport/runtime failure modes.
+**Depends on:** none
+
+### Phase 2: UI reports consistency and release proof
+**Goal:** Validate report links/output, enforce rollout checks, and freeze reproducible release state.
+**Depends on:** Phase 1

.planning/STATE.md

@@ -0,0 +1,26 @@
+---
+milestone: v1.0
+milestone_name: Data Pipeline Stability
+phase: "0"
+phase_name: Not started
+current_plan: 0
+total_plans_in_phase: 0
+status: planning
+progress_percent: 0
+last_activity: 2026-05-07
+---
+
+## Current Position
+
+Phase: Not started (defining requirements)
+Plan: —
+Status: Defining requirements
+Last activity: 2026-05-07 — Milestone v1.0 started
+
+## Decisions
+
+- Prioritize reliable data presence in activity/worktime views over UI extensions.
+
+## Blockers
+
+- None.

.planning/phases/01-collectors-and-api-flow-hardening/CONTEXT.md

@@ -0,0 +1,17 @@
+# Phase 1 Context
+
+## Phase
+
+Phase 1: Collectors and API flow hardening
+
+## Focus
+
+- Endpoint collectors must continuously send data without silent hangs.
+- AW server must accept/query data for UI pages consistently.
+- Failure points around transport/CORS/runtime must be explicitly checked.
+
+## Initial Acceptance Targets
+
+- Endpoint collector heartbeats arrive regularly.
+- Browser domains and endpoint signals appear in corresponding buckets.
+- Activity page for target host shows non-zero timeline/events for active period.

.planning/phases/01-collectors-and-api-flow-hardening/PLAN.md

@@ -0,0 +1,22 @@
+# PLAN — Phase 01: collectors-and-api-flow-hardening
+
+## Goal
+
+Deliver stable collector-to-server data flow so activity/worktime pages have consistent data.
+
+## Work Items
+
+1. Validate collector runtime and log rotation behavior.
+2. Validate server ingest endpoints and bucket write/read checks.
+3. Validate CORS/origin and report link consistency.
+4. Add/adjust scripts or runbook checks to detect zero-data regressions early.
+
+## Verification
+
+- Manual and scripted checks show fresh events in target buckets.
+- Host activity page reflects real activity (not `0s`) for active sessions.
+- No repeating transport errors in collector logs during test window.
+
+## Status
+
+Planned.