boundflow-charter 0.1.0.dev122__tar.gz → 0.1.0.dev128__tar.gz

{boundflow_charter-0.1.0.dev122 → boundflow_charter-0.1.0.dev128}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boundflow-charter
-Version: 0.1.0.dev122
+Version: 0.1.0.dev128
 Summary: Declarative, governed agents on BoundFlow — objective, tools, and policy as YAML.
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://github.com/boundflow/charter
@@ -40,6 +40,8 @@ Dynamic: license-file
 
 **The easiest way to build and manage production-ready agents.**
 
+![The Charter console: the fleet with an agent parked on an approval, the decision waiting on a human, and the policy and run history behind it](docs/console.gif)
+
 > **Pre-alpha, and in the open early.** The design is settled enough to read and
 > argue with; the code is not settled enough to run anything you care about.
 > Expect the configuration format to change.
@@ -463,16 +465,25 @@ decisions behind it, and [examples/](examples/) for complete configurations.
 
 ```bash
 python -m venv .venv
-.venv/bin/pip install -e ../boundflow/sdk/python   # your BoundFlow checkout
-.venv/bin/pip install -e '.[dev]'
+.venv/bin/pip install -e '.[dev,ui,otel]'
 .venv/bin/pytest
 ```
 
-End-to-end tests require a BoundFlow control plane and are excluded by default:
+`boundflow` comes from PyPI; add `--pre --upgrade boundflow` to track its main, which
+is what CI's second unit job does.
+
+End-to-end tests need a control plane, and skip themselves without one. The compose
+file CI uses runs the published image:
 
 ```bash
-docker compose -f ../boundflow/docker-compose.dist.yml up -d
-export BOUNDFLOW_API_KEY=<...>
+docker compose -f .github/boundflow.compose.yml up -d --wait
+key=$(docker compose -f .github/boundflow.compose.yml run --rm server \
+        -mode=provision -name=dev | awk '/^api_key/{print $NF}')
+
+export BOUNDFLOW_API_KEY=$key
+export BOUNDFLOW_SERVER_ADDRESS=http://localhost:50051
+export BOUNDFLOW_WORKER_ADDRESS=http://localhost:50052
+export CHARTER_STORE_URL=postgres://charter:charter@localhost:5434/charter
 pytest tests/e2e
 ```
 

{boundflow_charter-0.1.0.dev122 → boundflow_charter-0.1.0.dev128}/README.md

@@ -2,6 +2,8 @@
 
 **The easiest way to build and manage production-ready agents.**
 
+![The Charter console: the fleet with an agent parked on an approval, the decision waiting on a human, and the policy and run history behind it](docs/console.gif)
+
 > **Pre-alpha, and in the open early.** The design is settled enough to read and
 > argue with; the code is not settled enough to run anything you care about.
 > Expect the configuration format to change.
@@ -425,16 +427,25 @@ decisions behind it, and [examples/](examples/) for complete configurations.
 
 ```bash
 python -m venv .venv
-.venv/bin/pip install -e ../boundflow/sdk/python   # your BoundFlow checkout
-.venv/bin/pip install -e '.[dev]'
+.venv/bin/pip install -e '.[dev,ui,otel]'
 .venv/bin/pytest
 ```
 
-End-to-end tests require a BoundFlow control plane and are excluded by default:
+`boundflow` comes from PyPI; add `--pre --upgrade boundflow` to track its main, which
+is what CI's second unit job does.
+
+End-to-end tests need a control plane, and skip themselves without one. The compose
+file CI uses runs the published image:
 
 ```bash
-docker compose -f ../boundflow/docker-compose.dist.yml up -d
-export BOUNDFLOW_API_KEY=<...>
+docker compose -f .github/boundflow.compose.yml up -d --wait
+key=$(docker compose -f .github/boundflow.compose.yml run --rm server \
+        -mode=provision -name=dev | awk '/^api_key/{print $NF}')
+
+export BOUNDFLOW_API_KEY=$key
+export BOUNDFLOW_SERVER_ADDRESS=http://localhost:50051
+export BOUNDFLOW_WORKER_ADDRESS=http://localhost:50052
+export CHARTER_STORE_URL=postgres://charter:charter@localhost:5434/charter
 pytest tests/e2e
 ```
 

{boundflow_charter-0.1.0.dev122 → boundflow_charter-0.1.0.dev128}/boundflow_charter.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boundflow-charter
-Version: 0.1.0.dev122
+Version: 0.1.0.dev128
 Summary: Declarative, governed agents on BoundFlow — objective, tools, and policy as YAML.
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://github.com/boundflow/charter
@@ -40,6 +40,8 @@ Dynamic: license-file
 
 **The easiest way to build and manage production-ready agents.**
 
+![The Charter console: the fleet with an agent parked on an approval, the decision waiting on a human, and the policy and run history behind it](docs/console.gif)
+
 > **Pre-alpha, and in the open early.** The design is settled enough to read and
 > argue with; the code is not settled enough to run anything you care about.
 > Expect the configuration format to change.
@@ -463,16 +465,25 @@ decisions behind it, and [examples/](examples/) for complete configurations.
 
 ```bash
 python -m venv .venv
-.venv/bin/pip install -e ../boundflow/sdk/python   # your BoundFlow checkout
-.venv/bin/pip install -e '.[dev]'
+.venv/bin/pip install -e '.[dev,ui,otel]'
 .venv/bin/pytest
 ```
 
-End-to-end tests require a BoundFlow control plane and are excluded by default:
+`boundflow` comes from PyPI; add `--pre --upgrade boundflow` to track its main, which
+is what CI's second unit job does.
+
+End-to-end tests need a control plane, and skip themselves without one. The compose
+file CI uses runs the published image:
 
 ```bash
-docker compose -f ../boundflow/docker-compose.dist.yml up -d
-export BOUNDFLOW_API_KEY=<...>
+docker compose -f .github/boundflow.compose.yml up -d --wait
+key=$(docker compose -f .github/boundflow.compose.yml run --rm server \
+        -mode=provision -name=dev | awk '/^api_key/{print $NF}')
+
+export BOUNDFLOW_API_KEY=$key
+export BOUNDFLOW_SERVER_ADDRESS=http://localhost:50051
+export BOUNDFLOW_WORKER_ADDRESS=http://localhost:50052
+export CHARTER_STORE_URL=postgres://charter:charter@localhost:5434/charter
 pytest tests/e2e
 ```
 

{boundflow_charter-0.1.0.dev122 → boundflow_charter-0.1.0.dev128}/pyproject.toml

@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"
 # apiVersion stay `charter`. PyPI refuses the bare name, and the prefix is how this
 # is branded anyway.
 name = "boundflow-charter"
-version = "0.1.0.dev122"
+version = "0.1.0.dev128"
 description = "Declarative, governed agents on BoundFlow — objective, tools, and policy as YAML."
 readme = "README.md"
 requires-python = ">=3.10"