Feat/metrics - #10
Merged
Merged
Feat/metrics#10
Conversation
added 15 commits
September 17, 2026 19:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several important improvements to ASAREE, focusing on measurement and metrics terminology, enhanced documentation, test infrastructure, and frontend API updates. The changes clarify how built-in and custom metrics are handled, improve developer and user documentation, add test runner support in Docker and Compose, and expand frontend capabilities for measurement plan management and testing.
Measurement and Metrics Documentation:
CONTEXT.mddefining key terms for experiments, metrics, and runs, clarifying the distinction between built-in and custom metrics.docs/adr/0001-measurements-have-explicit-producers.md) specifying that built-in metrics are evaluated by ASAREE, while custom metrics are reported from agent outputs without post-run evaluation.README.mdwith detailed explanations of measurement plans, metric states, CSV export structure, and legacy value handling.Test Infrastructure:
Dockerfileand a correspondingasaree-testsservice tocompose.yml, enabling backend tests to run in Docker Compose against a real Postgres instance, separate from the production image. [1] [2].dockerignoreto include thetests/directory, ensuring test code is not included in production images.README.md.Frontend and API Enhancements:
frontend/src/api/client.ts) to support measurement plan validation, retrieval of measurement capabilities, and test runs for protocols. Also updated experiment creation and update methods to include measurement plan data. [1] [2] [3] [4] [5] [6]Documentation and Project Metadata:
README.mdfor improved project visibility and status tracking.CLAUDE.mdwith sections on agent skills, issue tracking, triage labels, and domain documentation.Configuration and Limits:
.env.example.FROM python:3.13-slim AS application) for multi-stage builds.These changes collectively improve clarity around metrics, strengthen testability, and enhance both developer and user experience.