chore(release): prepare v0.1.71

Author: kargarisaac

CHANGELOG.md

@@ -5,6 +5,33 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.71] - 2026-04-13
+
+### Added
+- `lerim status --live` now uses the same data and renderer as snapshot mode, with periodic refresh only as the difference.
+- New status payload fields for richer operations visibility:
+  - `projects[]` per-project memory/queue/blocker summary
+  - `recent_activity[]` timeline including `sync` and `maintain`
+  - `unscoped_sessions` totals by agent
+- New `lerim unscoped` command to inspect indexed sessions that do not map to a registered project.
+- Queue filters now support exact project matching (`--project`) and explicit substring matching (`--project-like`).
+
+### Changed
+- Status UI redesigned for clarity:
+  - project stream table (`blocked` / `running` / `queued` / `healthy`)
+  - explicit “What These Terms Mean” section
+  - actionable “What To Do Next” section with full `lerim ...` commands
+  - activity panel (sync + maintain)
+- Read/query defaults now use all registered projects unless explicitly narrowed:
+  - `lerim status --scope all|project --project ...`
+  - `lerim ask --scope all|project --project ...`
+  - `lerim memory list --scope all|project --project ...`
+- Canonical run telemetry is now written in `service_runs.details_json` with normalized keys (`metrics_version=1`, sync/maintain totals, per-project metrics, events) while preserving legacy compatibility fields.
+
+### Fixed
+- Live status activity no longer appears stale during long in-flight sync runs; running queue jobs are now surfaced in `recent_activity`.
+- Fixed maintain runtime error (`name 'index_path' is not defined`) that caused maintain runs to fail.
+
 ## [0.1.70] - 2026-03-28
 
 ### Quality Improvements

README.md

@@ -106,8 +106,11 @@ Most-used commands:
 
 ```bash
 lerim status
+lerim status --live
 lerim logs --follow
 lerim queue
+lerim queue --failed
+lerim unscoped --limit 20
 lerim memory list --limit 20
 ```
 

docs/changelog.md

@@ -8,17 +8,27 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+- No entries yet.
+
+## [0.1.71] - 2026-04-13
+
+### Added
+
+- Unified status dashboard output for `lerim status` and `lerim status --live` (same sections, live mode only refreshes).
+- Per-project stream visibility in status (`projects[]`) plus timeline activity (`recent_activity[]`) from sync + maintain runs.
+- New `lerim unscoped` command to inspect indexed sessions without project mapping.
+- Queue filtering split into exact project match (`--project`) and substring match (`--project-like`).
+
 ### Changed
 
-- Migrated `maintain` and `ask` to PydanticAI agents, aligned with the existing PydanticAI extraction flow.
-- Simplified runtime orchestration to a single PydanticAI execution path (sync, maintain, ask).
-- Updated tracing integration to `mlflow.pydantic_ai.autolog()`.
-- Updated docs to describe the current PydanticAI-only runtime and request-turn limits.
+- Default read scope for `ask`, `status`, and `memory list` is now all registered projects, with explicit `--scope project --project ...` for narrowing.
+- Status output now includes stronger action hints with full commands (`lerim retry ...`, `lerim skip ...`, `lerim queue --project ...`).
+- Canonical run telemetry now stored in `service_runs.details_json` with normalized metrics (`metrics_version=1`, sync/maintain totals, per-project metrics, events), while keeping compatibility fields for older consumers.
 
-### Removed
+### Fixed
 
-- Removed prior runtime branches and prior runtime-specific config surface from active runtime paths.
-- Removed prior runtime and proxy-bridge runtime dependencies from active package/lock state.
+- Live status activity now surfaces currently running sync work so the activity panel no longer appears frozen during long cycles.
+- Fixed maintain runtime failure caused by undefined `index_path`.
 
 ## [0.2.0] - 2026-03-25
 

docs/cli/ask.md

@@ -1,126 +1,72 @@
 # lerim ask
 
-Ask a question using accumulated memory as context.
+Ask a question using Lerim memory as context.
 
 ## Overview
 
-One-shot query: ask Lerim a question and get an answer informed by memories extracted from your agent sessions.
+`lerim ask` sends a question to the running Lerim service. The ask flow reads project memories and returns a grounded answer.
+
+Default scope is all registered projects. Use `--scope project --project ...` to narrow.
 
 !!! note
-    This command requires a running Lerim server. Start it with `lerim up` (Docker) or `lerim serve` (direct).
+    This command requires a running Lerim server (`lerim up` or `lerim serve`).
 
 ## Syntax
 
 ```bash
-lerim ask <question> [--project NAME] [--json]
+lerim ask <question> [--scope all|project] [--project NAME] [--json]
 ```
 
 ## Parameters
 
-<div class="param-field">
-  <div class="param-header">
-    <span class="param-name">question</span>
-    <span class="param-type">string</span>
-    <span class="param-badge required">required</span>
-  </div>
-  <p class="param-desc">Your question (use quotes if it contains spaces).</p>
-</div>
-
-<div class="param-field">
-  <div class="param-header">
-    <span class="param-name">--project</span>
-    <span class="param-type">string</span>
-  </div>
-  <p class="param-desc">Scope to a specific project. <strong>Note:</strong> Not yet implemented.</p>
-</div>
-
-<div class="param-field">
-  <div class="param-header">
-    <span class="param-name">--json</span>
-    <span class="param-type">boolean</span>
-    <span class="param-badge default">default: false</span>
-  </div>
-  <p class="param-desc">Output structured JSON instead of human-readable text.</p>
-</div>
+| Parameter | Default | Description |
+|---|---|---|
+| `question` | required | The question to ask |
+| `--scope` | `all` | Read from all projects or one project |
+| `--project` | -- | Project name/path when `--scope=project` |
+| `--json` | off | Output structured JSON payload |
 
 ## Examples
 
-### Basic question
-
-Ask about authentication patterns:
-
 ```bash
-lerim ask 'What auth pattern do we use?'
-```
-
-**Output:**
-
-```
-Based on your project memories, you use bearer token authentication
-for API requests. This pattern was chosen for its simplicity and
-compatibility with standard HTTP clients.
-```
-
-### JSON output
-
-Get structured output for parsing:
-
-```bash
-lerim ask "What testing framework do we use?" --json
-```
-
-**Output:**
-
-```json
-{
-  "answer": "Your project uses pytest...",
-  "agent_session_id": "4f5e0c0a-...",
-  "memories_used": [],
-  "error": false,
-  "cost_usd": 0.0012
-}
+lerim ask "Why did we choose this architecture?"
+lerim ask "What changed in auth recently?" --scope project --project lerim-cli
+lerim ask "What should I watch out for?" --json
 ```
 
 ## How it works
 
-1. Your question is sent to the running Lerim server via HTTP POST to `/api/ask`
-2. Lerim asks the PydanticAI ask agent to scan/read relevant memory files
-3. The model generates an answer grounded in the memory files it read
-4. The answer is returned as plain text (or JSON with metadata using `--json`)
-
-!!! tip
-    For best results, ask specific questions about decisions, patterns, or procedures in your project.
+1. CLI posts your question to `/api/ask`
+2. Ask flow retrieves relevant memory files from selected scope
+3. Model answers using retrieved memory context
+4. CLI prints text (or full JSON when `--json`)
 
 ## Exit codes
 
-- **0**: Success — answer generated
-- **1**: Error — server not running or authentication failed
-- **2**: Usage error — invalid arguments
+| Code | Meaning |
+|---|---|
+| `0` | Success |
+| `1` | Server or provider/auth error |
+| `2` | Usage error |
 
 ## Related commands
 
 <div class="grid cards" markdown>
 
--   :material-format-list-bulleted: **lerim memory list**
+-   :material-chart-box: **lerim status**
 
     ---
 
-    Browse stored memory files
+    Check project streams and queue health
 
-    [:octicons-arrow-right-24: lerim memory](memory.md)
+    [:octicons-arrow-right-24: lerim status](status.md)
 
--   :material-chart-box: **lerim status**
+-   :material-format-list-bulleted: **lerim memory list**
 
     ---
 
-    Check server status
+    List memory files in scope
 
-    [:octicons-arrow-right-24: lerim status](status.md)
+    [:octicons-arrow-right-24: lerim memory](memory.md)
 
 </div>
-
-## Notes
-
-- Ask uses memory scan/read tools to ground its answers in local memory files
-- If provider auth fails (missing API key), the CLI returns exit code 1
-- The `--project` flag is reserved for future project-scoped queries

docs/cli/memory.md

@@ -1,107 +1,107 @@
 # lerim memory
 
-Manage the memory store directly — list and reset memories.
+Manage memory files directly.
 
 ## Overview
 
-The `memory` command group provides direct access to the memory store. Memories are stored as markdown files in `.lerim/memory/` within each registered project. Use these subcommands to browse or wipe memories.
+The `memory` command group provides local memory operations:
 
-!!! tip "Direct file access"
-    You can also read `.lerim/memory/index.md` directly — it lists all memory files by category with one-line descriptions and links. No server or CLI needed.
+- `memory list` to browse memory markdown files
+- `memory reset` to wipe selected memory/index roots
+
+`memory list` is local and does not require the server.
 
 ---
 
 ## memory list
 
-List stored memories as a sorted file list. No server required.
+List memory files from all projects (default) or one project.
 
 ```bash
-lerim memory list [--project NAME] [--limit N] [--json]
+lerim memory list [--scope all|project] [--project NAME] [--limit N] [--json]
 ```
 
 | Parameter | Default | Description |
-|-----------|---------|-------------|
-| `--project` | -- | Reserved for project filter (not yet implemented) |
-| `--limit` | `50` | Maximum items to display |
-| `--json` | off | Output structured JSON |
+|---|---|---|
+| `--scope` | `all` | Read from all registered projects, or one project |
+| `--project` | -- | Project name/path when `--scope=project` |
+| `--limit` | `50` | Maximum number of files to print |
+| `--json` | off | Print JSON array instead of plain text |
+
+Examples:
 
 ```bash
 lerim memory list
-lerim memory list --limit 10 --json
+lerim memory list --scope project --project lerim-cli --limit 20
+lerim memory list --json
 ```
 
 ---
 
 ## memory reset
 
-Irreversibly delete `memory/`, `workspace/`, and `index/` under the selected scope.
+Irreversibly delete memory/workspace/index data in selected scope.
 
 ```bash
-lerim memory reset --yes [--scope SCOPE]
+lerim memory reset --yes [--scope project|global|both]
 ```
 
 | Parameter | Default | Description |
-|-----------|---------|-------------|
-| `--yes` | *(required)* | Safety flag -- command refuses to run without it |
-| `--scope` | `both` | What to reset: `project`, `global`, or `both` |
+|---|---|---|
+| `--yes` | required | Safety confirmation flag |
+| `--scope` | `both` | Reset `project`, `global`, or `both` |
 
 !!! danger
-    This operation is **irreversible**. All memories, workspace artifacts, and index data within the selected scope will be permanently deleted.
+    This is permanent. Deleted data cannot be recovered.
 
 !!! warning
-    `--scope project` alone does **not** reset the session queue. The sessions DB lives in `~/.lerim/index/sessions.sqlite3`. Use `--scope global` or `--scope both` to fully reset.
+    `--scope project` does **not** reset the session queue DB. Queue state lives in global `~/.lerim/index/sessions.sqlite3`. Use `--scope global` or `--scope both` for full queue/index reset.
+
+Examples:
 
 ```bash
-lerim memory reset --yes                          # wipe everything
-lerim memory reset --scope project --yes          # project data only
-lerim memory reset --yes && lerim sync --max-sessions 5  # fresh start
+lerim memory reset --yes
+lerim memory reset --scope project --yes
+lerim memory reset --scope global --yes
 ```
 
 ---
 
 ## Exit codes
 
 | Code | Meaning |
-|------|---------|
+|---|---|
 | `0` | Success |
-| `1` | Runtime failure (server not running, write error) |
-| `2` | Usage error (missing required flags) |
+| `1` | Runtime failure |
+| `2` | Usage error |
 
 ---
 
 ## Related commands
 
 <div class="grid cards" markdown>
 
--   :material-magnify: **lerim ask**
+-   :material-brain: **lerim ask**
 
     ---
 
-    Query memories with natural language
+    Query memories in natural language
 
     [:octicons-arrow-right-24: lerim ask](ask.md)
 
 -   :material-sync: **lerim sync**
 
     ---
 
-    Extract memories from agent sessions
+    Extract new memories from sessions
 
     [:octicons-arrow-right-24: lerim sync](sync.md)
 
--   :material-wrench: **lerim maintain**
-
-    ---
-
-    Offline memory refinement and deduplication
-
-    [:octicons-arrow-right-24: lerim maintain](maintain.md)
-
 -   :material-chart-box: **lerim status**
 
     ---
 
-    Check memory counts and server state
+    Check memory counts and queue state
 
     [:octicons-arrow-right-24: lerim status](status.md)