Skip to content

Release v0.2.0

Choose a tag to compare

@homer6 homer6 released this 25 Oct 21:08
· 25 commits to main since this release
e8324f6

agent-project v0.2.0

Released 2026-10-25. A minor release. Three changes since v0.1.0: two fixes from the
2026-10-21 security review and a change in what a Lake turn returns. Private repository and image,
docker.io/oramasearch/agent-project:v0.2.0. Tracking issue:
agent-project#35.

This release is the tree of dev at db8835f with these notes and the version.

What it includes

Every pull request merged into dev since v0.1.0:

PR Change
#29 The service token is compared in constant time, and turns are refused when it is unset (#23)
#31 A turn's credential goes only to Lake at the service's own LAKE_URL (#30)
#32 A Lake turn designs a pipeline, or proposes a solution, without a write (lake#796); prompt v7
#26 Docs: the v0.1.0 image digest recorded in its notes
#25 main merged back into dev after v0.1.0

The service token is always required — #29

POST /v1/turn checks the bearer with hmac.compare_digest instead of !=, and fails closed:
with AGENT_SERVICE_TOKEN unset or empty every turn is refused with 503 (in v0.1.0 the route was
open). A wrong or missing bearer is 401, as before. Turns from Lake's agent bus are unaffected.

A turn's credential goes only to LAKE_URL — #31

v0.1.0 took zetta_base_url and lake_url from the turn and sent the turn's bearer there. Now
service.run_turn settles every address before any request goes out:

  • the model gateway is always the service's own LAKE_URL; a turn's lake_url is never used for it;
  • zetta_base_url and lake_url are accepted only on LAKE_URL's origin and under its path, with
    no user info, query, fragment, backslash or ./.. segment; any other address refuses the turn;
  • with LAKE_URL unset, every turn that would send its credential is refused;
  • a turn that names no zetta_base_url still uses the environment's ZETTA_BASE_URL.

Behaviour change: a Lake turn never writes, and a named solution is a solution_proposal — #32

In v0.1.0 a request that named no methodology went to solution operation, which calls
create_solution and run_solution. Lake's turn key for the Project Agent deliberately grants no
solution action, so the turn ended declined with a 403 defect (lake#796). Now:

  • Only a request that names a solution operates one. Any other request is a pipeline design on
    the methodology path, on every engine; its result.pipeline is what Lake's build flow applies.
  • A Lake turn never builds. The solution action tools are not offered, and a call to one is
    rejected before it reaches the workspace. A named solution is answered as
    kind: solution_proposal: id, project, a live level, sources, production_ready / missing,
    the policy proposal and label definitions for sign-off, a reply ending Proposed, not built,
    applied: false. A proposal for an unread entry, a sketch or an absent level is declined. Lake
    creates the solution only when the person confirms (start_solution → confirm_solution). The
    command line keeps the build-and-operate flow.
  • compile_intent stores a graph in a project, so the methodology design calls it, and the
    validator requires it, only when the turn names a project.
  • Prompt v7 for the methodology design (v6 plus that rule and the routing wording). Solution
    operation stays on v5; v1 to v6 stay in the package.

A caller that read a solution result from a Lake turn now gets a solution_proposal instead. Lake's
e2e test T7 (a build turn returns a pipeline design) is owed: it needs this image on
lake-testing before it can pass.

Before it rolls: settings

Setting Needed by Rendered by
AGENT_SERVICE_TOKEN #29: without it every /v1/turn is refused with 503 the operator, already, on every library agent
LAKE_URL #31: without it every turn that carries a credential is refused the operator, already

No new setting is introduced. The model is still PROJECT_MODEL (default gpt-4o) or the turn's
model.

What it does not include

Unchanged from v0.1.0, and:

  • No turn trace off the pod's disk. The sibling agents stopped writing turn traces to disk in
    this wave; this one still does (#34).
  • No bus back-pressure. The agent-ask-orama fix for LSR-075 is not ported yet
    (#33).
  • No class-imbalance handling (#27).
  • No live model evaluation.

Known issues

Security-relevant first. All open at this tag.

  1. #34: every service turn writes a trace
    (the turn without its tokens, the task and the full result, which carry workspace content) to
    TRACE_DIR on the pod's disk, outside the workspace Zetta. Found by this release.
  2. #33 (LSR-075, medium, denial of
    service): the bus consumer claims every task it receives into an unbounded executor queue before a
    worker is free, so one tenant's burst holds other tenants' tasks and their leases.
  3. #17: the task's workspace_id is not
    passed explicitly on data-plane calls and delegated turns, and the idle bus receive runs more
    often than once a minute.
  4. lake#989 (LSR-183): Lake's agent confirmation
    gates do not establish a separate human confirmer. This agent's proposals rely on those gates.
  5. Lake e2e T7 has not run against this image (above).
  6. #28: the foundation's analysis
    fallback drops get_dataset's typed column objects (zetta#1299), so on a current engine it yields
    no columns when analyze_dataset returns none.
  7. #27: no class-imbalance detection or
    PR-AUC/lift reporting.
  8. zetta#989: the corpus trajectories used as
    few-shot precedent were generated with model-written observations.

Where it has run

The v0.2.0 tree has not run on the dev environment. No dev build of this repository was pinned
on lake-nonprod's dev member; every Lake runs oramasearch/agent-project:v0.1.0 from the
operator's default Agent Library. What has run is the test suite below.

The image

Built from the tag v0.2.0 (e8324f6) on the cluster BuildKit with build-agent.sh (linux/amd64, the repository's Dockerfile, with the catalog context catalog-cf20d264 and the corpus context agent-project-corpus-4537bcb), then tagged :v0.2.0 on that digest without rebuilding:

docker.io/oramasearch/agent-project:e8324f6@sha256:dc94533fa32954cc710e1b9f774475977efe67c07858cd8e8fb5e6d723cf2545, also tagged :v0.2.0 (same digest). The Docker Hub repository answers 404 anonymously (private).

It is not rolled anywhere yet: pinning it on an environment is a separate change to the operator's set files, through dev, testing, staging and prod in order.

Verification

Proof Result
Test suite (uv run --frozen pytest -q -ra, macOS arm64, Python 3.12) 91 tests: 91 passed, 0 failed, 0 skipped: test_apps.py 6, test_catalog.py 1, test_edit.py 7, test_experiments.py 7, test_foundations.py 4, test_lake_bus.py 4, test_methodologies.py 6, test_release.py 2, test_service.py 7, test_service_auth.py 13, test_solutions.py 10, test_turn_destinations.py 24
Release notes for the code's version tests/test_release.py reads [project].version from pyproject.toml (0.2.0), checks the installed package agrees, and fails if these notes are missing or not indexed
Live model evaluation Not run (needs a live model)
Lake e2e T7 Not run (needs this image on lake-testing)
Linux image build (cluster BuildKit, from the tag) Built from v0.2.0 with build-agent.sh: oramasearch/agent-project:e8324f6, also :v0.2.0, sha256:dc94533fa32954cc710e1b9f774475977efe67c07858cd8e8fb5e6d723cf2545; private (404 anonymously)