Skip to content

rename internals and prove evals catch a break - #15

Merged
o-mid merged 1 commit into
mainfrom
chore/ownership-pass
Sep 17, 2026
Merged

o-mid merged 1 commit into
mainfrom
chore/ownership-pass

Conversation

@o-mid

@o-mid o-mid commented Sep 17, 2026 •

Copy link
Copy Markdown
Owner

Problem

A few internals were named for how they were wired, not what they do (setPlanner, setStepRunner, lastCall, decodeStep, plannerCost). README cadence was a bit stacked. Frozen eval fixtures could vanish from disk and the comparison unit tests would still pass until the policy runner ran.

Solution

Renamed those five. Tightened README voice. The eval unit suite now asserts the frozen fixture files exist, so deleting one fails before policy is up. Existing tests still cover a freeze case that starts passing.

How to test

cd services/api && npm ci && npm test
cd ../../packages/evals && npm install
node --import tsx --test ./compare.test.ts

To see the break: move packages/evals/fixtures/policy-infinite-approve.json aside and re-run the unit test. Restore the file before pushing.

setPlanner, setStepRunner, lastCall, decodeStep, and plannerCost now say what they do. README is tighter. Frozen fixture files are asserted on disk so a delete fails before policy.
@vercel

vercel Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
guardrail-agent Ready Ready Preview Sep 17, 2026 12:45pm UTC

@o-mid
o-mid merged commit c30044a into main Sep 17, 2026
9 checks passed

This branch was successfully deployed

1 active deployment
Preview — fe295d19 Deployed Sep 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant