runledger-cli 0.1.2__tar.gz → 0.1.3__tar.gz

runledger_cli-0.1.3/PKG-INFO

@@ -0,0 +1,90 @@
+Metadata-Version: 2.4
+Name: runledger-cli
+Version: 0.1.3
+Summary: Zero‑instrumentation experiment registry CLI
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: requests
+Requires-Dist: rich
+
+Here’s the updated README with the troubleshooting note added right after the installation instructions. The primary command remains `runledger`, but users who hit the Windows PATH issue now have a clear fallback.
+
+---
+
+# RunLedger
+
+**A zero-instrumentation experiment registry.** Point RunLedger at a folder of JSON experiment files and search, filter, aggregate, diff, and export the results; no SDK, no code changes, no cloud.
+
+Most experiment trackers make you instrument your training code before they can help you. RunLedger reads the JSON you're already writing, no `wandb.init()`, no `mlflow.log_metric()`, and indexes it in real Postgres, giving you full relational search: structured comparisons, full-text, fuzzy matching, and exact array-element lookups, from one CLI command.
+
+Backed by Postgres, served by a Spring Boot API, and fronted by a Python CLI.
+
+## Install
+
+```bash
+pip install runledger-cli
+```
+
+Requires Docker. If it's not installed, `runledger` detects that on first run and links you straight to the installer; everything else (Postgres, the backend) is managed for you.
+
+### Troubleshooting: `runledger` command not found (Windows)
+
+On some Windows systems, the Python Scripts folder is not automatically added to your PATH. If `runledger` is not recognized after installation, you have two options:
+
+1. **Add the Scripts folder to your PATH permanently** (recommended):
+    - Find where `runledger` was installed: `pip show runledger-cli | findstr Location`
+    - Navigate to that folder, then up one level to the `Scripts` directory.
+    - Add that `Scripts` path to your system PATH via **System Properties > Environment Variables**.
+    - Restart your terminal.
+
+2. **Use the Python module fallback** (works immediately, no PATH changes):
+   ```bash
+   python -m cli.ledger
+   ```
+   All subcommands and the guided wizard work exactly the same way; just prefix every command with `python -m cli.ledger`.
+
+Once the PATH is configured, `runledger` will work as shown in the examples below.
+
+<details>
+<summary>Installing from source</summary>
+
+```bash
+git clone https://github.com/yourusername/run-ledger.git
+cd run-ledger
+docker compose up -d
+pip install -e .
+```
+</details>
+
+## Quick start
+
+```bash
+runledger scan ~/experiments --batch my-sweep
+runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
+runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
+```
+
+New here? Run `runledger` with no arguments — the guided wizard walks you through your first scan and search.
+
+## What you get
+
+- **Search any field, no schema required** — structured comparisons (`gt`, `lt`, `eq`...), full-text with stemming, and fuzzy matching for typos, all on arbitrary dot-paths, including fields nested inside arrays (`results[].sst2_cacc`).
+- **Compound AND/OR** across multiple conditions in one query.
+- **Exact match pointers** — array searches tell you exactly which element(s) matched (`results[3].sst2_cacc = 0.933`), not just that the run did.
+- **Aggregates & group-by** — `AVG` / `MAX` / `MIN` / `SUM` / `COUNT`, straight from the CLI.
+- **Safe re-scanning** — ingestion is idempotent; a changed file gets a new version, and `diff --history` shows you what changed and when.
+- **Run diff, saved searches, JSONL ingestion, block-depth control** — see [docs/examples.md](docs/examples.md) for each in action.
+- **Self-hosted, local-first** — your data never leaves your machine.
+
+## Metric paths
+
+Address any value with a dot-path — `accuracy`, `metrics.loss`, `results[].sst2_cacc`. Shorthand (`cacc`) resolves automatically when it's unambiguous. Run `runledger metrics --batch <batch>` to see everything discovered in a scan, or add `--verbose` for full paths.
+
+## Docs
+
+- [API reference](docs/api.md)
+- [Usage examples](docs/examples.md)
+
+## License
+
+MIT

runledger_cli-0.1.3/README.md

@@ -0,0 +1,81 @@
+Here’s the updated README with the troubleshooting note added right after the installation instructions. The primary command remains `runledger`, but users who hit the Windows PATH issue now have a clear fallback.
+
+---
+
+# RunLedger
+
+**A zero-instrumentation experiment registry.** Point RunLedger at a folder of JSON experiment files and search, filter, aggregate, diff, and export the results; no SDK, no code changes, no cloud.
+
+Most experiment trackers make you instrument your training code before they can help you. RunLedger reads the JSON you're already writing, no `wandb.init()`, no `mlflow.log_metric()`, and indexes it in real Postgres, giving you full relational search: structured comparisons, full-text, fuzzy matching, and exact array-element lookups, from one CLI command.
+
+Backed by Postgres, served by a Spring Boot API, and fronted by a Python CLI.
+
+## Install
+
+```bash
+pip install runledger-cli
+```
+
+Requires Docker. If it's not installed, `runledger` detects that on first run and links you straight to the installer; everything else (Postgres, the backend) is managed for you.
+
+### Troubleshooting: `runledger` command not found (Windows)
+
+On some Windows systems, the Python Scripts folder is not automatically added to your PATH. If `runledger` is not recognized after installation, you have two options:
+
+1. **Add the Scripts folder to your PATH permanently** (recommended):
+    - Find where `runledger` was installed: `pip show runledger-cli | findstr Location`
+    - Navigate to that folder, then up one level to the `Scripts` directory.
+    - Add that `Scripts` path to your system PATH via **System Properties > Environment Variables**.
+    - Restart your terminal.
+
+2. **Use the Python module fallback** (works immediately, no PATH changes):
+   ```bash
+   python -m cli.ledger
+   ```
+   All subcommands and the guided wizard work exactly the same way; just prefix every command with `python -m cli.ledger`.
+
+Once the PATH is configured, `runledger` will work as shown in the examples below.
+
+<details>
+<summary>Installing from source</summary>
+
+```bash
+git clone https://github.com/yourusername/run-ledger.git
+cd run-ledger
+docker compose up -d
+pip install -e .
+```
+</details>
+
+## Quick start
+
+```bash
+runledger scan ~/experiments --batch my-sweep
+runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
+runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
+```
+
+New here? Run `runledger` with no arguments — the guided wizard walks you through your first scan and search.
+
+## What you get
+
+- **Search any field, no schema required** — structured comparisons (`gt`, `lt`, `eq`...), full-text with stemming, and fuzzy matching for typos, all on arbitrary dot-paths, including fields nested inside arrays (`results[].sst2_cacc`).
+- **Compound AND/OR** across multiple conditions in one query.
+- **Exact match pointers** — array searches tell you exactly which element(s) matched (`results[3].sst2_cacc = 0.933`), not just that the run did.
+- **Aggregates & group-by** — `AVG` / `MAX` / `MIN` / `SUM` / `COUNT`, straight from the CLI.
+- **Safe re-scanning** — ingestion is idempotent; a changed file gets a new version, and `diff --history` shows you what changed and when.
+- **Run diff, saved searches, JSONL ingestion, block-depth control** — see [docs/examples.md](docs/examples.md) for each in action.
+- **Self-hosted, local-first** — your data never leaves your machine.
+
+## Metric paths
+
+Address any value with a dot-path — `accuracy`, `metrics.loss`, `results[].sst2_cacc`. Shorthand (`cacc`) resolves automatically when it's unambiguous. Run `runledger metrics --batch <batch>` to see everything discovered in a scan, or add `--verbose` for full paths.
+
+## Docs
+
+- [API reference](docs/api.md)
+- [Usage examples](docs/examples.md)
+
+## License
+
+MIT

{runledger_cli-0.1.2 → runledger_cli-0.1.3}/cli/ledger.py

@@ -333,11 +333,13 @@ def navigate_json_pointer(doc, pointer: str):
 
 def show_blocks(run: dict, dot_path: str = None, block_levels: list = None):
     payload = run.get("payload", {})
+    # Use experiment name, then source file, then run id
     if isinstance(payload, dict):
         source_file = payload.get("_source", {}).get("file") or payload.get("experiment") or f"run-{run['id']}"
     else:
         source_file = f"run-{run['id']}"
 
+    # Show matched pointers if available
     matched = run.get("matched")
     if matched:
         console.print("  Matches:")
@@ -359,6 +361,7 @@ def show_blocks(run: dict, dot_path: str = None, block_levels: list = None):
         console.print(Panel(pretty, title=f"Run {run['id']} · {source_file}"))
         return
 
+    # Strip "[]" so JSON Pointer navigation works
     parts = [seg.replace("[]", "") for seg in dot_path.split(".")]
     max_block = len(parts) - 1
 
@@ -372,6 +375,7 @@ def show_blocks(run: dict, dot_path: str = None, block_levels: list = None):
 
     for block in sorted(levels, reverse=True):
         if block == 0 and matched:
+            # For block=0, show each matched snippet individually
             for i, m in enumerate(matched):
                 snippet = m.get("snippet")
                 try:
@@ -381,9 +385,19 @@ def show_blocks(run: dict, dot_path: str = None, block_levels: list = None):
                 title = f"Run {run['id']} · {source_file}  |  metric: {dot_path}  |  depth: 0 (match {i+1}/{len(matched)})"
                 console.print(Panel(pretty, title=title))
         else:
-            ancestor_parts = parts[:len(parts) - (block + 1)]
-            pointer = "/" + "/".join(ancestor_parts) if ancestor_parts else ""
-            node = navigate_json_pointer(payload, pointer) if pointer else payload
+            if block > 0 and matched:
+                # Use the first match's concrete pointer for precise navigation
+                # Example: "clients[1].sweep[0].fin_asr" → "/clients/1/sweep"
+                concrete = matched[0]['pointer']
+                segments = concrete.replace('[', '.').replace(']', '').split('.')
+                ancestor_segments = segments[:len(segments) - (block + 1)]
+                pointer = "/" + "/".join(ancestor_segments) if ancestor_segments else ""
+                node = navigate_json_pointer(payload, pointer) if pointer else payload
+            else:
+                ancestor_parts = parts[:len(parts) - (block + 1)]
+                pointer = "/" + "/".join(ancestor_parts) if ancestor_parts else ""
+                node = navigate_json_pointer(payload, pointer) if pointer else payload
+
             depth_label = ""
             if block == max_block:
                 depth_label = " (full run)"
@@ -394,7 +408,6 @@ def show_blocks(run: dict, dot_path: str = None, block_levels: list = None):
             except Exception:
                 pretty = str(node)
             console.print(Panel(pretty, title=f"Run {run['id']} · {source_file}  |  metric: {dot_path}  |  depth: {block}{depth_label}"))
-
 # ------------------------------------------------------------
 # Export helpers
 # ------------------------------------------------------------
@@ -444,9 +457,16 @@ def build_export_blocks(content, dot_path, block_levels, include_pointers=True):
                         "value": m.get("value")
                     })
             else:
-                ancestor_parts = parts[:len(parts) - (block + 1)]
-                pointer = "/" + "/".join(ancestor_parts) if ancestor_parts else ""
-                node = navigate_json_pointer(payload, pointer) if pointer else payload
+                if block > 0 and matched:
+                    concrete = matched[0]['pointer']
+                    segments = concrete.replace('[', '.').replace(']', '').split('.')
+                    ancestor_segments = segments[:len(segments) - (block + 1)]
+                    pointer = "/" + "/".join(ancestor_segments) if ancestor_segments else ""
+                    node = navigate_json_pointer(payload, pointer) if pointer else payload
+                else:
+                    ancestor_parts = parts[:len(parts) - (block + 1)]
+                    pointer = "/" + "/".join(ancestor_parts) if ancestor_parts else ""
+                    node = navigate_json_pointer(payload, pointer) if pointer else payload
                 blocks.append({
                     "id": run["id"],
                     "sourceFile": source_file,

{runledger_cli-0.1.2 → runledger_cli-0.1.3}/cli/tests/test_data_features.py

@@ -57,7 +57,7 @@ def setup_data():
     # Ingest sample runs into the fresh batch
     result = run_cli("scan", str(SAMPLE_FOLDER), "--batch", BATCH_NAME)
     assert result.returncode == 0, result.stderr
-    assert "Successfully ingested 9 run(s)" in result.stdout
+    assert "Successfully ingested 10 run(s)" in result.stdout
 
 # ------------------------------------------------------------
 # v1 – Basic metric block search
@@ -251,4 +251,73 @@ def test_jsonl_ingestion(setup_data):
                 assert payload.get(k) == v, f"Mismatch at line {idx}: {k} {v} != {payload.get(k)}"
 
         # Clean up the temporary batch
-        requests.delete(f"{API_BASE}/batch/{batch}")  # if this endpoint exists, otherwise manual cleanup
+        requests.delete(f"{API_BASE}/batch/{batch}")  # if this endpoint exists, otherwise manual cleanup
+
+def test_nested_array_block_depth():
+    """Verify block‑depth on nested arrays using direct API calls."""
+    import uuid
+    import requests
+
+    batch = f"nest-{uuid.uuid4().hex[:6]}"
+
+    # 1. Ingest the nested file directly via the API
+    payload = {
+        "experiment": "nested_arrays_block_test",
+        "clients": [
+            {
+                "client_name": "clean_client",
+                "sweep": [
+                    {"w_base": 0.5, "fin_asr": 0.12, "sst2_asr": 0.07},
+                    {"w_base": 0.75, "fin_asr": 0.09, "sst2_asr": 0.06}
+                ]
+            },
+            {
+                "client_name": "poisoned_client",
+                "sweep": [
+                    {"w_base": 0.5, "fin_asr": 0.45, "sst2_asr": 0.88},
+                    {"w_base": 1.0, "fin_asr": 0.28, "sst2_asr": 0.72}
+                ]
+            }
+        ]
+    }
+    resp = requests.post(API_BASE, json={"payload": payload, "batch": batch})
+    assert resp.status_code == 201, f"ingest failed: {resp.text}"
+
+    # 2. Search for fin_asr < 0.3 with block=0
+    params = {"metric": "clients[].sweep[].fin_asr", "op": "lt", "value": "0.3",
+              "batch": batch, "block": "0", "size": "1", "pointers": "true"}
+    resp = requests.get(API_BASE, params=params)
+    assert resp.status_code == 200, resp.text
+    data = resp.json()
+    assert data["totalElements"] == 1
+    run = data["content"][0]
+
+    # 3. Verify matched pointers exist
+    matched = run.get("matched")
+    assert matched is not None, "matched pointers missing"
+    assert len(matched) == 3, f"expected 3 matches, got {len(matched)}"
+
+    # 4. block=1 should return the sweep array (a list)
+    params["block"] = "1"
+    resp = requests.get(API_BASE, params=params)
+    assert resp.status_code == 200, resp.text
+    data1 = resp.json()
+    block1_payload = data1["content"][0]["payload"]
+    assert isinstance(block1_payload, list), f"block=1 payload should be a list, got {type(block1_payload)}"
+    assert any("fin_asr" in json.dumps(elem) for elem in block1_payload)
+
+    # 5. block=2 should return the client object
+    params["block"] = "2"
+    resp = requests.get(API_BASE, params=params)
+    assert resp.status_code == 200, resp.text
+    data2 = resp.json()
+    block2_payload = data2["content"][0]["payload"]
+    assert isinstance(block2_payload, dict) and block2_payload.get("client_name") == "clean_client"
+
+    # 6. block=3 should return the clients array
+    params["block"] = "3"
+    resp = requests.get(API_BASE, params=params)
+    assert resp.status_code == 200, resp.text
+    data3 = resp.json()
+    block3_payload = data3["content"][0]["payload"]
+    assert isinstance(block3_payload, list) and len(block3_payload) > 0

{runledger_cli-0.1.2 → runledger_cli-0.1.3}/cli/tests/test_integration.py

@@ -10,8 +10,8 @@ import pytest
 import requests
 
 PROJECT_ROOT = Path(__file__).parent.parent.parent
-COMPOSE_FILE = PROJECT_ROOT / "docker-compose.yml"
-HEALTH_URL = "http://localhost:8080/actuator/health"
+COMPOSE_FILE = PROJECT_ROOT / "docker-compose.test.yml"
+HEALTH_URL = "http://localhost:8081/actuator/health"
 API_BASE = "http://localhost:8080/api/runs"
 
 def wait_for_health(timeout=120):

{runledger_cli-0.1.2 → runledger_cli-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name           = "runledger-cli"
-version        = "0.1.2"
+version        = "0.1.3"
 description    = "Zero‑instrumentation experiment registry CLI"
 readme         = "README.md"
 requires-python = ">=3.10"

runledger_cli-0.1.3/runledger_cli.egg-info/PKG-INFO

@@ -0,0 +1,90 @@
+Metadata-Version: 2.4
+Name: runledger-cli
+Version: 0.1.3
+Summary: Zero‑instrumentation experiment registry CLI
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: requests
+Requires-Dist: rich
+
+Here’s the updated README with the troubleshooting note added right after the installation instructions. The primary command remains `runledger`, but users who hit the Windows PATH issue now have a clear fallback.
+
+---
+
+# RunLedger
+
+**A zero-instrumentation experiment registry.** Point RunLedger at a folder of JSON experiment files and search, filter, aggregate, diff, and export the results; no SDK, no code changes, no cloud.
+
+Most experiment trackers make you instrument your training code before they can help you. RunLedger reads the JSON you're already writing, no `wandb.init()`, no `mlflow.log_metric()`, and indexes it in real Postgres, giving you full relational search: structured comparisons, full-text, fuzzy matching, and exact array-element lookups, from one CLI command.
+
+Backed by Postgres, served by a Spring Boot API, and fronted by a Python CLI.
+
+## Install
+
+```bash
+pip install runledger-cli
+```
+
+Requires Docker. If it's not installed, `runledger` detects that on first run and links you straight to the installer; everything else (Postgres, the backend) is managed for you.
+
+### Troubleshooting: `runledger` command not found (Windows)
+
+On some Windows systems, the Python Scripts folder is not automatically added to your PATH. If `runledger` is not recognized after installation, you have two options:
+
+1. **Add the Scripts folder to your PATH permanently** (recommended):
+    - Find where `runledger` was installed: `pip show runledger-cli | findstr Location`
+    - Navigate to that folder, then up one level to the `Scripts` directory.
+    - Add that `Scripts` path to your system PATH via **System Properties > Environment Variables**.
+    - Restart your terminal.
+
+2. **Use the Python module fallback** (works immediately, no PATH changes):
+   ```bash
+   python -m cli.ledger
+   ```
+   All subcommands and the guided wizard work exactly the same way; just prefix every command with `python -m cli.ledger`.
+
+Once the PATH is configured, `runledger` will work as shown in the examples below.
+
+<details>
+<summary>Installing from source</summary>
+
+```bash
+git clone https://github.com/yourusername/run-ledger.git
+cd run-ledger
+docker compose up -d
+pip install -e .
+```
+</details>
+
+## Quick start
+
+```bash
+runledger scan ~/experiments --batch my-sweep
+runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
+runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
+```
+
+New here? Run `runledger` with no arguments — the guided wizard walks you through your first scan and search.
+
+## What you get
+
+- **Search any field, no schema required** — structured comparisons (`gt`, `lt`, `eq`...), full-text with stemming, and fuzzy matching for typos, all on arbitrary dot-paths, including fields nested inside arrays (`results[].sst2_cacc`).
+- **Compound AND/OR** across multiple conditions in one query.
+- **Exact match pointers** — array searches tell you exactly which element(s) matched (`results[3].sst2_cacc = 0.933`), not just that the run did.
+- **Aggregates & group-by** — `AVG` / `MAX` / `MIN` / `SUM` / `COUNT`, straight from the CLI.
+- **Safe re-scanning** — ingestion is idempotent; a changed file gets a new version, and `diff --history` shows you what changed and when.
+- **Run diff, saved searches, JSONL ingestion, block-depth control** — see [docs/examples.md](docs/examples.md) for each in action.
+- **Self-hosted, local-first** — your data never leaves your machine.
+
+## Metric paths
+
+Address any value with a dot-path — `accuracy`, `metrics.loss`, `results[].sst2_cacc`. Shorthand (`cacc`) resolves automatically when it's unambiguous. Run `runledger metrics --batch <batch>` to see everything discovered in a scan, or add `--verbose` for full paths.
+
+## Docs
+
+- [API reference](docs/api.md)
+- [Usage examples](docs/examples.md)
+
+## License
+
+MIT

runledger_cli-0.1.2/PKG-INFO

@@ -1,198 +0,0 @@
-Metadata-Version: 2.4
-Name: runledger-cli
-Version: 0.1.2
-Summary: Zero‑instrumentation experiment registry CLI
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-Requires-Dist: requests
-Requires-Dist: rich
-
-# RunLedger
-
-**Zero-instrumentation experiment registry and search engine.**  
-Point to a folder of JSON experiment files and instantly search, filter, aggregate, diff, and export your results—no SDK, no code changes.
-
-## Quick Start
-
-```bash
-# 1. Start the backend
-docker compose up -d
-
-# 2. Ingest your experiment files
-runledger scan ~/experiments --batch my-sweep
-
-# 3. Search
-runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
-
-# 4. Aggregate
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
-```
-
-New to the tool? Try the guided wizard:
-
-```bash
-runledger guided
-```
-
-## Key Features
-
-### 🔍 Search any JSON field, no schema required
-- Structured numeric/text comparisons on arbitrary dot-paths (`metrics.accuracy`, `config.optimizer.learning_rate`).
-- Full-text phrase search with stemming.
-- Fuzzy trigram search for typos.
-- Compound AND/OR queries: combine multiple conditions.
-- Batch isolation: group runs by folder and filter within a batch.
-
-### 📊 Aggregates & group-by
-Answer research questions directly:
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch sweep
-```
-
-Supported functions: `AVG`, `MAX`, `MIN`, `SUM`, `COUNT`. Group by any scalar field.
-
-### 🎯 Exact match pointers (“JSON line numbers”)
-For array searches (`results[].sst2_cacc < 0.8`), the CLI shows exactly which array elements matched:
-
-```text
-Matches:
-  • results[0].sst2_cacc = 0.924312
-  • results[3].sst2_cacc = 0.933486
-```
-
-Works for scalar, array, and compound conditions.
-
-### 🔬 Block-depth control
-Limit output to the relevant part of a large JSON payload with `--block 0` (tightest match), `--block 1` (parent), etc.
-
-### 📁 JSONL ingestion
-Ingest one-JSON-object-per-line logs (common in training scripts) with `--jsonl`.
-
-### 🔎 Run diff
-Compare any two runs side-by-side:
-
-```bash
-runledger diff 12 15
-```
-
-Or see every version of a re-scanned run with `--history`.
-
-### 💾 Saved searches
-Save frequent queries and re-run them with a single command:
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-```
-
-### 🧭 Interactive & guided modes
-- Filter-as-you-type interactive search (`runledger interactive`).
-- Step-by-step wizard for first-time users (`runledger guided`).
-
-### 🔒 Self-hosted, local-first
-Runs in Docker with a single `docker compose up -d`.  
-All data stays on your machine. No internet, no accounts, no vendor lock-in.
-
-## Installation
-
-### From PyPI (CLI only)
-
-```bash
-pip install runledger-cli
-```
-
-### From source
-
-```bash
-git clone https://github.com/yourusername/run-ledger.git
-cd run-ledger
-docker compose up -d          # starts PostgreSQL + Spring Boot
-pip install -e .              # installs the CLI
-```
-
-## Quick Tour
-
-### Scan & Discover
-
-```bash
-runledger scan experiments/ --batch my-sweep
-```
-
-The CLI prints a schema summary showing every metric found, its full dot-path, and depth. Array keys are shown with `[]` notation (e.g., `results[].cacc`).
-
-### Search
-
-```bash
-# Single condition
-runledger search --metric loss --op lt --value 0.2 --batch my-sweep --summary
-
-# Compound AND
-runledger search --metric accuracy --op gt --value 0.9 --metric loss --op lt --value 0.2 --combine and
-
-# Full-text
-runledger search --q "weighted averaging"
-
-# Fuzzy
-runledger search --q "weighted avaraging" --fuzzy
-```
-
-### Aggregate
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by config.learning_rate --batch my-sweep
-```
-
-### Diff
-
-```bash
-runledger diff 12 15
-runledger diff --history 12 --batch my-sweep
-```
-
-### Export
-
-```bash
-runledger export --metric accuracy --op gt --value 0.9 --batch my-sweep --block 0 --output results.txt
-```
-
-### Saved searches
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-runledger saved list
-runledger saved delete best-accuracy
-```
-
-## Metrics-Path Convention
-
-RunLedger uses **dot-separated paths** to address any value in a JSON payload.
-
-| Example | Meaning |
-| -------- | ------- |
-| `accuracy` | Top-level field |
-| `metrics.loss` | Nested field |
-| `results[].sst2_cacc` | Field inside each element of an array |
-| `phases[].metrics.loss` | Nested field inside array elements |
-
-**Shorthand keys:** After scanning a batch, the CLI shows a shorthand key for every leaf field. Typing `cacc` will automatically resolve to `client.results[].cacc` if that’s the only (or shallowest) occurrence. Use the full path when there’s ambiguity.
-
-Discover available metrics with:
-
-```bash
-runledger metrics --batch my-sweep
-runledger metrics --batch my-sweep --verbose   # shows full paths
-```
-
-## API
-
-See [`docs/api.md`](docs/api.md) for the complete REST API reference.
-
-## Usage Examples
-
-See [`docs/examples.md`](docs/examples.md) for real-world workflows.
-
-## License
-
-MIT

runledger_cli-0.1.2/README.md

@@ -1,189 +0,0 @@
-# RunLedger
-
-**Zero-instrumentation experiment registry and search engine.**  
-Point to a folder of JSON experiment files and instantly search, filter, aggregate, diff, and export your results—no SDK, no code changes.
-
-## Quick Start
-
-```bash
-# 1. Start the backend
-docker compose up -d
-
-# 2. Ingest your experiment files
-runledger scan ~/experiments --batch my-sweep
-
-# 3. Search
-runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
-
-# 4. Aggregate
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
-```
-
-New to the tool? Try the guided wizard:
-
-```bash
-runledger guided
-```
-
-## Key Features
-
-### 🔍 Search any JSON field, no schema required
-- Structured numeric/text comparisons on arbitrary dot-paths (`metrics.accuracy`, `config.optimizer.learning_rate`).
-- Full-text phrase search with stemming.
-- Fuzzy trigram search for typos.
-- Compound AND/OR queries: combine multiple conditions.
-- Batch isolation: group runs by folder and filter within a batch.
-
-### 📊 Aggregates & group-by
-Answer research questions directly:
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch sweep
-```
-
-Supported functions: `AVG`, `MAX`, `MIN`, `SUM`, `COUNT`. Group by any scalar field.
-
-### 🎯 Exact match pointers (“JSON line numbers”)
-For array searches (`results[].sst2_cacc < 0.8`), the CLI shows exactly which array elements matched:
-
-```text
-Matches:
-  • results[0].sst2_cacc = 0.924312
-  • results[3].sst2_cacc = 0.933486
-```
-
-Works for scalar, array, and compound conditions.
-
-### 🔬 Block-depth control
-Limit output to the relevant part of a large JSON payload with `--block 0` (tightest match), `--block 1` (parent), etc.
-
-### 📁 JSONL ingestion
-Ingest one-JSON-object-per-line logs (common in training scripts) with `--jsonl`.
-
-### 🔎 Run diff
-Compare any two runs side-by-side:
-
-```bash
-runledger diff 12 15
-```
-
-Or see every version of a re-scanned run with `--history`.
-
-### 💾 Saved searches
-Save frequent queries and re-run them with a single command:
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-```
-
-### 🧭 Interactive & guided modes
-- Filter-as-you-type interactive search (`runledger interactive`).
-- Step-by-step wizard for first-time users (`runledger guided`).
-
-### 🔒 Self-hosted, local-first
-Runs in Docker with a single `docker compose up -d`.  
-All data stays on your machine. No internet, no accounts, no vendor lock-in.
-
-## Installation
-
-### From PyPI (CLI only)
-
-```bash
-pip install runledger-cli
-```
-
-### From source
-
-```bash
-git clone https://github.com/yourusername/run-ledger.git
-cd run-ledger
-docker compose up -d          # starts PostgreSQL + Spring Boot
-pip install -e .              # installs the CLI
-```
-
-## Quick Tour
-
-### Scan & Discover
-
-```bash
-runledger scan experiments/ --batch my-sweep
-```
-
-The CLI prints a schema summary showing every metric found, its full dot-path, and depth. Array keys are shown with `[]` notation (e.g., `results[].cacc`).
-
-### Search
-
-```bash
-# Single condition
-runledger search --metric loss --op lt --value 0.2 --batch my-sweep --summary
-
-# Compound AND
-runledger search --metric accuracy --op gt --value 0.9 --metric loss --op lt --value 0.2 --combine and
-
-# Full-text
-runledger search --q "weighted averaging"
-
-# Fuzzy
-runledger search --q "weighted avaraging" --fuzzy
-```
-
-### Aggregate
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by config.learning_rate --batch my-sweep
-```
-
-### Diff
-
-```bash
-runledger diff 12 15
-runledger diff --history 12 --batch my-sweep
-```
-
-### Export
-
-```bash
-runledger export --metric accuracy --op gt --value 0.9 --batch my-sweep --block 0 --output results.txt
-```
-
-### Saved searches
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-runledger saved list
-runledger saved delete best-accuracy
-```
-
-## Metrics-Path Convention
-
-RunLedger uses **dot-separated paths** to address any value in a JSON payload.
-
-| Example | Meaning |
-| -------- | ------- |
-| `accuracy` | Top-level field |
-| `metrics.loss` | Nested field |
-| `results[].sst2_cacc` | Field inside each element of an array |
-| `phases[].metrics.loss` | Nested field inside array elements |
-
-**Shorthand keys:** After scanning a batch, the CLI shows a shorthand key for every leaf field. Typing `cacc` will automatically resolve to `client.results[].cacc` if that’s the only (or shallowest) occurrence. Use the full path when there’s ambiguity.
-
-Discover available metrics with:
-
-```bash
-runledger metrics --batch my-sweep
-runledger metrics --batch my-sweep --verbose   # shows full paths
-```
-
-## API
-
-See [`docs/api.md`](docs/api.md) for the complete REST API reference.
-
-## Usage Examples
-
-See [`docs/examples.md`](docs/examples.md) for real-world workflows.
-
-## License
-
-MIT

runledger_cli-0.1.2/runledger_cli.egg-info/PKG-INFO

@@ -1,198 +0,0 @@
-Metadata-Version: 2.4
-Name: runledger-cli
-Version: 0.1.2
-Summary: Zero‑instrumentation experiment registry CLI
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-Requires-Dist: requests
-Requires-Dist: rich
-
-# RunLedger
-
-**Zero-instrumentation experiment registry and search engine.**  
-Point to a folder of JSON experiment files and instantly search, filter, aggregate, diff, and export your results—no SDK, no code changes.
-
-## Quick Start
-
-```bash
-# 1. Start the backend
-docker compose up -d
-
-# 2. Ingest your experiment files
-runledger scan ~/experiments --batch my-sweep
-
-# 3. Search
-runledger search --metric accuracy --op gt --value 0.9 --batch my-sweep
-
-# 4. Aggregate
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch my-sweep
-```
-
-New to the tool? Try the guided wizard:
-
-```bash
-runledger guided
-```
-
-## Key Features
-
-### 🔍 Search any JSON field, no schema required
-- Structured numeric/text comparisons on arbitrary dot-paths (`metrics.accuracy`, `config.optimizer.learning_rate`).
-- Full-text phrase search with stemming.
-- Fuzzy trigram search for typos.
-- Compound AND/OR queries: combine multiple conditions.
-- Batch isolation: group runs by folder and filter within a batch.
-
-### 📊 Aggregates & group-by
-Answer research questions directly:
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by experiment --batch sweep
-```
-
-Supported functions: `AVG`, `MAX`, `MIN`, `SUM`, `COUNT`. Group by any scalar field.
-
-### 🎯 Exact match pointers (“JSON line numbers”)
-For array searches (`results[].sst2_cacc < 0.8`), the CLI shows exactly which array elements matched:
-
-```text
-Matches:
-  • results[0].sst2_cacc = 0.924312
-  • results[3].sst2_cacc = 0.933486
-```
-
-Works for scalar, array, and compound conditions.
-
-### 🔬 Block-depth control
-Limit output to the relevant part of a large JSON payload with `--block 0` (tightest match), `--block 1` (parent), etc.
-
-### 📁 JSONL ingestion
-Ingest one-JSON-object-per-line logs (common in training scripts) with `--jsonl`.
-
-### 🔎 Run diff
-Compare any two runs side-by-side:
-
-```bash
-runledger diff 12 15
-```
-
-Or see every version of a re-scanned run with `--history`.
-
-### 💾 Saved searches
-Save frequent queries and re-run them with a single command:
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-```
-
-### 🧭 Interactive & guided modes
-- Filter-as-you-type interactive search (`runledger interactive`).
-- Step-by-step wizard for first-time users (`runledger guided`).
-
-### 🔒 Self-hosted, local-first
-Runs in Docker with a single `docker compose up -d`.  
-All data stays on your machine. No internet, no accounts, no vendor lock-in.
-
-## Installation
-
-### From PyPI (CLI only)
-
-```bash
-pip install runledger-cli
-```
-
-### From source
-
-```bash
-git clone https://github.com/yourusername/run-ledger.git
-cd run-ledger
-docker compose up -d          # starts PostgreSQL + Spring Boot
-pip install -e .              # installs the CLI
-```
-
-## Quick Tour
-
-### Scan & Discover
-
-```bash
-runledger scan experiments/ --batch my-sweep
-```
-
-The CLI prints a schema summary showing every metric found, its full dot-path, and depth. Array keys are shown with `[]` notation (e.g., `results[].cacc`).
-
-### Search
-
-```bash
-# Single condition
-runledger search --metric loss --op lt --value 0.2 --batch my-sweep --summary
-
-# Compound AND
-runledger search --metric accuracy --op gt --value 0.9 --metric loss --op lt --value 0.2 --combine and
-
-# Full-text
-runledger search --q "weighted averaging"
-
-# Fuzzy
-runledger search --q "weighted avaraging" --fuzzy
-```
-
-### Aggregate
-
-```bash
-runledger aggregate --metric accuracy --agg AVG --group-by config.learning_rate --batch my-sweep
-```
-
-### Diff
-
-```bash
-runledger diff 12 15
-runledger diff --history 12 --batch my-sweep
-```
-
-### Export
-
-```bash
-runledger export --metric accuracy --op gt --value 0.9 --batch my-sweep --block 0 --output results.txt
-```
-
-### Saved searches
-
-```bash
-runledger search --metric accuracy --op gt --value 0.9 --batch sweep --save best-accuracy
-runledger search --saved best-accuracy
-runledger saved list
-runledger saved delete best-accuracy
-```
-
-## Metrics-Path Convention
-
-RunLedger uses **dot-separated paths** to address any value in a JSON payload.
-
-| Example | Meaning |
-| -------- | ------- |
-| `accuracy` | Top-level field |
-| `metrics.loss` | Nested field |
-| `results[].sst2_cacc` | Field inside each element of an array |
-| `phases[].metrics.loss` | Nested field inside array elements |
-
-**Shorthand keys:** After scanning a batch, the CLI shows a shorthand key for every leaf field. Typing `cacc` will automatically resolve to `client.results[].cacc` if that’s the only (or shallowest) occurrence. Use the full path when there’s ambiguity.
-
-Discover available metrics with:
-
-```bash
-runledger metrics --batch my-sweep
-runledger metrics --batch my-sweep --verbose   # shows full paths
-```
-
-## API
-
-See [`docs/api.md`](docs/api.md) for the complete REST API reference.
-
-## Usage Examples
-
-See [`docs/examples.md`](docs/examples.md) for real-world workflows.
-
-## License
-
-MIT