v0.2.0-Foundation
V0.2.0 — Foundation & Integration
The core capture loop. Shipped in the v0.2.x line on main; this doc is a retrospective of what landed, not a forward plan.
Features:
- Ambient Dashboard: The homepage displays capture rhythm stats (last pour, today/week counts, streak), per-module activity counts, recent capture history, and gap indicators for neglected modules. Launch via
pouror bypass directly to a workflow viapour <module_key>. See pour-design-spec §2.1. - Resilient Transport: Seamlessly shifts between the Obsidian REST API and direct filesystem writes if the vault is closed. See ADR-001-Hybrid-Transport-Layer.
- Dynamic Form Rendering: Parses
~/.pour/config.tomlto dynamically construct UI forms — see field-types for the full schema. - Smart Data Fetching: `dynamic_select` fields automatically query vault directories for options, backed by an atomic local JSON cache (
~/.pour/cache/state.json). See The-3-Tier-Data-Fallback. - Capture History: Every successful write is logged to
~/.pour/cache/history.jsonl(append-only JSONL, O(1) writes), with a precomputedhistory-summary.jsonfor instant dashboard stats. Powers the dashboard's ambient stats and enables behavioral feedback loops. All history is preserved indefinitely for long-term analytics. - Obsidian-Native Output: Custom YAML generation ensures compatibility with Obsidian Properties. See ADR-002-Custom-YAML-Serialization.
- In-App Configuration: Module settings (
e) and vault settings (v) editable from the dashboard without leaving the TUI. Uses `toml_edit` for comment-preserving atomic writes.
Known Limitations:
- Network operations block the UI thread momentarily. See ADR-003-Synchronous-TUI-Async-Operations.
Release context: sprint-6-integration-report and System-Architecture-Overview.