raaymax
diff --git a/‎.planning/PROJECT.md‎
Lines changed: 64 additions & 0 deletions b/‎.planning/PROJECT.md‎
Lines changed: 64 additions & 0 deletions
diff --git a/‎.planning/REQUIREMENTS.md‎
Lines changed: 88 additions & 0 deletions b/‎.planning/REQUIREMENTS.md‎
Lines changed: 88 additions & 0 deletions
diff --git a/‎.planning/ROADMAP.md‎
Lines changed: 110 additions & 0 deletions b/‎.planning/ROADMAP.md‎
Lines changed: 110 additions & 0 deletions
diff --git a/‎.planning/STATE.md‎
Lines changed: 94 additions & 0 deletions b/‎.planning/STATE.md‎
Lines changed: 94 additions & 0 deletions
@@ -0,0 +1,64 @@
+# LazyTail
+
+## What This Is
+
+LazyTail is a terminal-based log viewer for developers who work with multiple log streams. It provides multi-tab viewing, vim-style navigation, real-time filtering, and an MCP server for AI-assisted log analysis.
+
+## Core Value
+
+Fast, keyboard-driven log exploration across multiple sources with live updates.
+
+## Requirements
+
+### Validated
+
+- ✓ Multi-tab log viewing with independent state per tab — existing
+- ✓ Vim-style navigation (hjkl, gg/G, Ctrl+d/u, search) — existing
+- ✓ Real-time filtering with string, regex, and query syntax — existing
+- ✓ Background filtering with progress indication — existing
+- ✓ File watching for live log updates — existing
+- ✓ Stdin/pipe streaming support — existing
+- ✓ Line expansion for long lines — existing
+- ✓ Global stream capture (`cmd | lazytail -n "name"`) stored in ~/.config/lazytail/data/ — existing
+- ✓ MCP server for AI tool integration — existing
+- ✓ Source discovery mode to browse captured streams — existing
+
+### Active
+
+- [ ] Stream cleanup on exit/SIGTERM — stream files should be cleaned up so names can be reused
+- [ ] Project-scoped log configuration — `lazytail.yaml` config file defines project sources
+- [ ] Project-local stream storage — `.lazytail/` folder for project-specific streams
+- [ ] Dual storage support — both global (~/.config/lazytail/) and project-local (.lazytail/) coexist
+
+### Out of Scope
+
+- GUI interface — terminal-first tool
+- Log aggregation/shipping — this is a viewer, not a collector
+- Remote log access — local files and streams only
+
+## Context
+
+LazyTail is a brownfield project with an established architecture:
+- Event-driven main loop (render-collect-process)
+- Trait-based reader abstraction (`LogReader`) for files and streams
+- Channel-based communication for background filtering
+- Existing stream capture stores data in `~/.config/lazytail/data/`
+
+Current stream handling in `src/main.rs` creates files but doesn't clean them up on exit. Signal handling exists via `signal-hook` crate but isn't connected to stream cleanup.
+
+## Constraints
+
+- **Tech stack**: Rust with ratatui/crossterm — established, no changes
+- **Config format**: YAML for lazytail.yaml — human-readable, familiar to developers
+- **Backwards compatibility**: Global streams in ~/.config/lazytail/ must continue working
+
+## Key Decisions
+
+| Decision | Rationale | Outcome |
+|----------|-----------|---------|
+| YAML for project config | Human-readable, familiar format | — Pending |
+| .lazytail/ for project streams | Mirrors .git/ pattern, keeps project state local | — Pending |
+| Both global and project storage | Flexibility for different use cases | — Pending |
+
+---
+*Last updated: 2026-02-03 after initialization*
@@ -0,0 +1,88 @@
+# Requirements
+
+**Project:** LazyTail — Project Configuration & Stream Cleanup
+**Version:** v1
+**Created:** 2026-02-03
+
+## v1 Requirements
+
+### Signal Handling
+
+- [x] **SIG-01**: Graceful shutdown on SIGINT/SIGTERM cleans up stream markers before exit
+- [x] **SIG-02**: Fix capture.rs signal handler — remove process::exit(), let main thread handle cleanup
+- [x] **SIG-03**: Stale marker detection on startup — recover from SIGKILL by checking if PID still running
+- [x] **SIG-04**: Double Ctrl+C support — first triggers graceful shutdown, second forces immediate exit
+
+### Config Discovery
+
+- [x] **DISC-01**: Project root discovery — walk up directories looking for lazytail.yaml or .lazytail/
+- [x] **DISC-02**: Graceful missing config — tool works without config file using defaults
+- [x] **DISC-03**: Filesystem boundary checks — stop at root and $HOME to prevent slow traversal
+
+### Config Loading
+
+- [x] **LOAD-01**: YAML format support — parse lazytail.yaml using serde-saphyr
+- [x] **LOAD-02**: Hierarchical precedence — CLI args override project config override global config
+- [x] **LOAD-03**: Clear error messages — show file path and line number on parse errors
+
+### Config Options
+
+- [x] **OPT-01**: `name` option — project display name shown in UI
+- [x] **OPT-02**: `sources` option — file-based source definitions with paths/globs
+- [ ] **OPT-03**: `follow` option — default auto-follow mode for new tabs (deferred)
+- [ ] **OPT-04**: `filter` option — default filter pattern applied on startup (deferred)
+- [ ] **OPT-05**: `streams_dir` option — custom location for project streams (deferred)
+
+### Project-Local Streams
+
+- [x] **PROJ-01**: .lazytail/ directory — create project-local directory for stream storage
+- [x] **PROJ-02**: Context-aware capture — `lazytail -n` writes to project .lazytail/ when in project, global otherwise
+
+### Config Commands
+
+- [x] **CMD-01**: `lazytail init` — generate starter lazytail.yaml with comments
+- [x] **CMD-02**: `lazytail config validate` — parse config and report errors without running
+- [x] **CMD-03**: `lazytail config show` — display effective merged config
+
+## v2 Requirements (Deferred)
+
+- Local override file (lazytail.local.yaml) for personal settings not committed to git
+- Environment variable overrides (LAZYTAIL_* prefix)
+- Command-based sources in config (capture output of commands)
+- Source groups (open multiple related sources with one command)
+- JSON Schema for editor autocomplete support
+
+## Out of Scope
+
+- GUI interface — terminal-first tool
+- Remote log access — local files and streams only
+- TOML config format — YAML chosen for nested structures and multi-line strings
+- Wrap option in config — line expansion handles long lines
+
+## Traceability
+
+| Requirement | Phase | Status |
+|-------------|-------|--------|
+| SIG-01 | Phase 1 | complete |
+| SIG-02 | Phase 1 | complete |
+| SIG-03 | Phase 1 | complete |
+| SIG-04 | Phase 1 | complete |
+| DISC-01 | Phase 2 | complete |
+| DISC-02 | Phase 2 | complete |
+| DISC-03 | Phase 2 | complete |
+| LOAD-01 | Phase 3 | complete |
+| LOAD-02 | Phase 3 | complete |
+| LOAD-03 | Phase 3 | complete |
+| OPT-01 | Phase 3 | complete |
+| OPT-02 | Phase 3 | complete |
+| OPT-03 | - | deferred |
+| OPT-04 | - | deferred |
+| OPT-05 | - | deferred |
+| PROJ-01 | Phase 4 | complete |
+| PROJ-02 | Phase 4 | complete |
+| CMD-01 | Phase 5 | complete |
+| CMD-02 | Phase 5 | complete |
+| CMD-03 | Phase 5 | complete |
+
+---
+*Last updated: 2026-02-05*
@@ -0,0 +1,110 @@
+# Roadmap: LazyTail Project Configuration & Stream Cleanup
+
+## Overview
+
+This roadmap delivers project-scoped configuration and robust signal handling to LazyTail. The journey starts with signal infrastructure (foundational for all cleanup), builds configuration discovery and loading, integrates config into the application, extends to project-local streams, and finishes with developer experience commands. Each phase builds on the previous, following the dependency chain identified in research.
+
+## Phases
+
+**Phase Numbering:**
+- Integer phases (1, 2, 3): Planned milestone work
+- Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)
+
+Decimal phases appear between their surrounding integers in numeric order.
+
+- [x] **Phase 1: Signal Infrastructure** - Robust signal handling with cleanup coordination
+- [x] **Phase 2: Config Discovery** - Find project root and config files
+- [x] **Phase 3: Config Loading** - Parse YAML and merge configuration layers
+- [x] **Phase 4: Project-Local Streams** - .lazytail/ directory with context-aware capture
+- [x] **Phase 5: Config Commands** - Init, validate, and show commands for developer experience
+
+## Phase Details
+
+### Phase 1: Signal Infrastructure
+**Goal**: Application handles termination signals gracefully with proper cleanup
+**Depends on**: Nothing (first phase)
+**Requirements**: SIG-01, SIG-02, SIG-03, SIG-04
+**Success Criteria** (what must be TRUE):
+  1. Running `lazytail -n test` then pressing Ctrl+C cleans up stream markers before exit
+  2. Running `lazytail -n test` then sending SIGTERM cleans up stream markers before exit
+  3. After SIGKILL (kill -9), restarting lazytail detects and cleans stale markers
+  4. Double Ctrl+C forces immediate exit without hanging
+  5. capture.rs signal handler does not call process::exit() directly
+**Plans:** 1 plan
+
+Plans:
+- [x] 01-01-PLAN.md — Signal module, capture.rs refactor, stale marker cleanup
+
+### Phase 2: Config Discovery
+**Goal**: Application finds project root and config files by walking directory tree
+**Depends on**: Phase 1
+**Requirements**: DISC-01, DISC-02, DISC-03
+**Success Criteria** (what must be TRUE):
+  1. Running lazytail in a subdirectory finds lazytail.yaml in parent directories
+  2. Running lazytail in a directory with lazytail.yaml recognizes it as project root
+  3. Running lazytail without any config file works normally using defaults
+  4. Discovery stops at filesystem root (/)
+**Plans:** 1 plan
+
+Plans:
+- [x] 02-01-PLAN.md — Config discovery module with verbose output integration
+
+### Phase 3: Config Loading
+**Goal**: Application parses YAML config and merges multiple configuration sources with clear precedence
+**Depends on**: Phase 2
+**Requirements**: LOAD-01, LOAD-02, LOAD-03, OPT-01, OPT-02
+**Note**: OPT-03, OPT-04, OPT-05 (follow, filter, streams_dir) deferred per CONTEXT.md - only `name` and `sources` for now
+**Success Criteria** (what must be TRUE):
+  1. lazytail.yaml with `name` and `sources` options parses correctly
+  2. Project config overrides global config for name; sources kept in separate groups
+  3. Parse errors show file path, line number, and "did you mean" suggestions
+  4. Named sources from config appear in side panel
+  5. Sources with missing files shown grayed out/disabled
+**Plans:** 2 plans
+
+Plans:
+- [x] 03-01-PLAN.md — Config loading infrastructure (types, parser, errors)
+- [x] 03-02-PLAN.md — Integration with main.rs and UI (source categories)
+
+### Phase 4: Project-Local Streams
+**Goal**: Streams captured within a project are stored locally in .lazytail/ directory
+**Depends on**: Phase 3
+**Requirements**: PROJ-01, PROJ-02
+**Success Criteria** (what must be TRUE):
+  1. Running `lazytail -n test` inside a project creates stream in .lazytail/data/
+  2. Running `lazytail -n test` outside any project creates stream in ~/.config/lazytail/data/
+  3. Discovery mode shows both project-local and global streams appropriately
+  4. .lazytail/ directory created with secure permissions (mode 0700)
+**Plans:** 2 plans
+
+Plans:
+- [x] 04-01-PLAN.md — Context-aware directory functions and capture mode integration
+- [x] 04-02-PLAN.md — Discovery mode with dual-location source scanning
+
+### Phase 5: Config Commands
+**Goal**: Developer experience commands for config initialization, validation, and introspection
+**Depends on**: Phase 3
+**Requirements**: CMD-01, CMD-02, CMD-03
+**Success Criteria** (what must be TRUE):
+  1. `lazytail init` creates starter lazytail.yaml with helpful comments
+  2. `lazytail config validate` reports config errors without starting the viewer
+  3. `lazytail config show` displays effective merged configuration
+  4. Init refuses to overwrite existing config without confirmation
+**Plans**: 2 plans
+
+Plans:
+- [x] 05-01-PLAN.md — CLI subcommand infrastructure and init command
+- [x] 05-02-PLAN.md — Config validate and show commands
+
+## Progress
+
+**Execution Order:**
+Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
+
+| Phase | Plans Complete | Status | Completed |
+|-------|----------------|--------|-----------|
+| 1. Signal Infrastructure | 1/1 | Complete | 2026-02-03 |
+| 2. Config Discovery | 1/1 | Complete | 2026-02-03 |
+| 3. Config Loading | 2/2 | Complete | 2026-02-04 |
+| 4. Project-Local Streams | 2/2 | Complete | 2026-02-04 |
+| 5. Config Commands | 2/2 | Complete | 2026-02-05 |
@@ -0,0 +1,94 @@
+# Project State
+
+## Project Reference
+
+See: .planning/PROJECT.md (updated 2026-02-03)
+
+**Core value:** Fast, keyboard-driven log exploration across multiple sources with live updates
+**Current focus:** Phase 5 complete - Config Commands
+
+## Current Position
+
+Phase: 5 of 5 (Config Commands)
+Plan: 2 of 2 in current phase
+Status: Complete
+Last activity: 2026-02-05 - Completed 05-02-PLAN.md
+
+Progress: [██████████] 100%
+
+## Performance Metrics
+
+**Velocity:**
+- Total plans completed: 8
+- Average duration: 8 min
+- Total execution time: 1.05 hours
+
+**By Phase:**
+
+| Phase | Plans | Total | Avg/Plan |
+|-------|-------|-------|----------|
+| 01-signal-infrastructure | 1 | 8 min | 8 min |
+| 02-config-discovery | 1 | 12 min | 12 min |
+| 03-config-loading | 2 | 18 min | 9 min |
+| 04-project-local-streams | 2 | 15 min | 8 min |
+| 05-config-commands | 2 | 14 min | 7 min |
+
+**Recent Trend:**
+- Last 5 plans: 10 min, 8 min, 7 min, 8 min, 6 min
+- Trend: Consistent ~8 min average
+
+*Updated after each plan completion*
+
+## Accumulated Context
+
+### Decisions
+
+Decisions are logged in PROJECT.md Key Decisions table.
+Recent decisions affecting current work:
+
+- [Roadmap]: YAML chosen for config format (human-readable, nested structures)
+- [Roadmap]: .lazytail/ for project streams (mirrors .git/ pattern)
+- [Roadmap]: Both global and project storage coexist
+- [01-01]: Use signal-hook::flag for flag-based signal handling (non-blocking)
+- [01-01]: Register conditional_shutdown before flag setter (order for double Ctrl+C)
+- [01-01]: Stale marker cleanup logs errors but doesn't fail startup
+- [02-01]: Only lazytail.yaml signals project root (not .lazytail/ directory)
+- [02-01]: Global config checked before parent walk, but doesn't stop project search
+- [02-01]: Verbose mode shows full search path, not just results
+- [02-01]: Discovery runs early, before mode dispatch
+- [03-01]: Use serde-saphyr instead of unmaintained serde-yaml
+- [03-01]: 0.8 Jaro-Winkler threshold for typo suggestions
+- [03-01]: Project name takes precedence when merging configs
+- [03-01]: Sources kept in separate groups (project vs global)
+- [03-01]: Graceful degradation: empty Config when no configs exist
+- [03-02]: ProjectSource and GlobalSource added to beginning of SourceType enum
+- [03-02]: Disabled tabs created for missing config sources (shown grayed)
+- [03-02]: Config tabs prepended before CLI and discovery tabs
+- [03-02]: Captured renamed from Global in UI for clarity
+- [04-01]: Context-aware functions use _for_context variants for backward compatibility
+- [04-01]: Secure permissions (0700) on Unix only via cfg(unix)
+- [04-01]: Location indicator (project/global) shown in capture header
+- [04-02]: SourceLocation enum for tracking source origin (Project, Global)
+- [04-02]: Project sources shadow global sources with same name
+- [04-02]: scan_data_directory helper extracted for code reuse
+- [04-02]: watched_location parameter passed through for correct location assignment
+- [05-01]: colored 3.1 used instead of 2.7 (version not available)
+- [05-01]: Cli struct renamed from Args for clarity with subcommand field
+- [05-01]: Subcommand dispatch happens before stale marker cleanup
+- [05-02]: Closest config wins for config commands (load_single_file)
+- [05-02]: validate checks source file existence beyond YAML validity
+- [05-02]: show uses single sources: section (closest-wins semantics)
+
+### Pending Todos
+
+None.
+
+### Blockers/Concerns
+
+None - all planned phases complete.
+
+## Session Continuity
+
+Last session: 2026-02-05
+Stopped at: Completed 05-02-PLAN.md (all phases complete)
+Resume file: None