fluxloop-cli 0.3.9__tar.gz → 0.3.11__tar.gz

{fluxloop_cli-0.3.9 → fluxloop_cli-0.3.11}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fluxloop-cli
-Version: 0.3.9
+Version: 0.3.11
 Summary: FluxLoop CLI for running agent simulations
 Author-email: FluxLoop Team <team@fluxloop.dev>
 License: Apache-2.0
@@ -68,10 +68,36 @@ The legacy `setting.yaml` is still supported, but new projects created with
 - `fluxloop parse experiment` – convert experiment outputs into readable artifacts and emit structured per-trace JSON at `per_trace_analysis/per_trace.jsonl`
 - `fluxloop evaluate experiment` – run the LLM-driven evaluation pipeline (LLM-PT → rule aggregation → LLM-OV → HTML render). Requires the parsed per-trace file (or `--per-trace`) and writes an interactive report to `evaluation_report/report.html` by default.
 - `fluxloop config set-llm` – update LLM provider/model in `configs/input.yaml`
+- `fluxloop data push|bind|gt status` – upload/bind Ground Truth (Validation) datasets and inspect GT materialization status
 - `fluxloop record enable|disable|status` – toggle recording mode across `.env` and simulation config
 - `fluxloop doctor` – summarize Python, FluxLoop CLI/MCP, and MCP index state for the active environment
 - `--yes/-y` (for `fluxloop run experiment`) – skip the interactive confirmation prompt, ideal for CI and the Pytest bridge
 
+### Ground Truth Data Workflow
+
+Use these commands to upload validation datasets, bind them to a scenario, and
+check GT materialization progress:
+
+```bash
+# 1) Upload as Ground Truth + bind + materialize
+fluxloop data push qa_pairs.csv \
+  --usage ground-truth \
+  --scenario <scenario_id> \
+  --split test \
+  --label-column expected_answer \
+  --row-filter "lang = 'ko'"
+
+# 2) Bind existing data as validation (auto materialize by default)
+fluxloop data bind <data_id> \
+  --scenario <scenario_id> \
+  --role validation \
+  --split test \
+  --label-column expected_answer
+
+# 3) Check GT materialization status
+fluxloop data gt status --scenario <scenario_id> [--data-id <data_id>]
+```
+
 ### Multi-turn supervisor options
 
 `fluxloop run experiment` supports multi-turn orchestration out of the box:

{fluxloop_cli-0.3.9 → fluxloop_cli-0.3.11}/README.md

@@ -28,10 +28,36 @@ The legacy `setting.yaml` is still supported, but new projects created with
 - `fluxloop parse experiment` – convert experiment outputs into readable artifacts and emit structured per-trace JSON at `per_trace_analysis/per_trace.jsonl`
 - `fluxloop evaluate experiment` – run the LLM-driven evaluation pipeline (LLM-PT → rule aggregation → LLM-OV → HTML render). Requires the parsed per-trace file (or `--per-trace`) and writes an interactive report to `evaluation_report/report.html` by default.
 - `fluxloop config set-llm` – update LLM provider/model in `configs/input.yaml`
+- `fluxloop data push|bind|gt status` – upload/bind Ground Truth (Validation) datasets and inspect GT materialization status
 - `fluxloop record enable|disable|status` – toggle recording mode across `.env` and simulation config
 - `fluxloop doctor` – summarize Python, FluxLoop CLI/MCP, and MCP index state for the active environment
 - `--yes/-y` (for `fluxloop run experiment`) – skip the interactive confirmation prompt, ideal for CI and the Pytest bridge
 
+### Ground Truth Data Workflow
+
+Use these commands to upload validation datasets, bind them to a scenario, and
+check GT materialization progress:
+
+```bash
+# 1) Upload as Ground Truth + bind + materialize
+fluxloop data push qa_pairs.csv \
+  --usage ground-truth \
+  --scenario <scenario_id> \
+  --split test \
+  --label-column expected_answer \
+  --row-filter "lang = 'ko'"
+
+# 2) Bind existing data as validation (auto materialize by default)
+fluxloop data bind <data_id> \
+  --scenario <scenario_id> \
+  --role validation \
+  --split test \
+  --label-column expected_answer
+
+# 3) Check GT materialization status
+fluxloop data gt status --scenario <scenario_id> [--data-id <data_id>]
+```
+
 ### Multi-turn supervisor options
 
 `fluxloop run experiment` supports multi-turn orchestration out of the box:

{fluxloop_cli-0.3.9 → fluxloop_cli-0.3.11}/fluxloop_cli/__init__.py

@@ -2,7 +2,7 @@
 FluxLoop CLI - Command-line interface for running agent simulations.
 """
 
-__version__ = "0.3.9"
+__version__ = "0.3.11"
 
 from .main import app
 

{fluxloop_cli-0.3.9 → fluxloop_cli-0.3.11}/fluxloop_cli/commands/bundles.py

@@ -229,6 +229,9 @@ def list_bundles(
     project_id: Optional[str] = typer.Option(
         None, "--project-id", help="Filter by project ID"
     ),
+    format: str = typer.Option(
+        "table", "--format", help="Output format (table, json)"
+    ),
     api_url: Optional[str] = typer.Option(
         None, "--api-url", help="FluxLoop API base URL"
     ),
@@ -275,6 +278,12 @@ def list_bundles(
                 )
             return
 
+        if format == "json":
+            import json
+
+            console.print_json(json.dumps(bundles, ensure_ascii=False, default=str))
+            return
+
         # Create table
         table = Table(title="Bundles")
         table.add_column("ID", style="cyan")