You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Master tracking issue for the 0.2.0 release. Scope is the single-agent MVP: from a user's perspective, pip install agentanvil + a contract YAML + a LangChain agent = a passing test run in under 10 minutes, with a reproducible report.
Current version: 0.1.x (foundation patches) → Target: 0.2.0.
The version jump is justified by the scope:
Static consistency analyzer on the contract model
Analyzer, Generator, DockerRunner, Reporter — the full orchestration loop lands.
Evaluator layers 1 + 2 (single judge) — covers all objective metrics of Layer 1 and a single LLM-as-judge for Layer 2 (ensemble deferred to 0.3.0).
AgentLoomBackend guarded by agentloom[contracts,observability]>=0.5.0 optional dependency.
Record/replay envelope complete for single-agent flows with determinism CI job.
Quickstart LangChain example ≤ 10 min verified in CI.
Portability invariant CI job certifies pip install agentanvil (no extras) runs end-to-end via DirectBackend.
mkdocs-material docs site scaffolded.
Out of scope for 0.2.0 (deferred to 0.3.0 and later) is listed at the bottom.
How to use this issue
Each item is a coherent body of work with shared dependencies.
Items within a phase are parallelizable unless explicitly noted.
Phase A — Contract model completion
The static consistency analyzer is the deliverable of 0.2.0.
Parallelization: all three in parallel. #7 depends on Runner ABC from 0.1.x; #8 depends on DirectBackend skeleton from 0.1.x; #9 depends on AgentLoom 0.5.0 availability.
Description
Master tracking issue for the 0.2.0 release. Scope is the single-agent MVP: from a user's perspective,
pip install agentanvil+ a contract YAML + a LangChain agent = a passing test run in under 10 minutes, with a reproducible report.Current version: 0.1.x (foundation patches) → Target: 0.2.0.
The version jump is justified by the scope:
AgentLoomBackendguarded byagentloom[contracts,observability]>=0.5.0optional dependency.pip install agentanvil(no extras) runs end-to-end viaDirectBackend.Out of scope for 0.2.0 (deferred to 0.3.0 and later) is listed at the bottom.
How to use this issue
Phase A — Contract model completion
The static consistency analyzer is the deliverable of 0.2.0.
core.contractsanalyzer/module with framework detection andAgentProfilegenerator/module withhappy_path,edge_case,policyscenario categoriesParallelization: #4 is independent of #5 and #6. #5 and #6 are independent once contract types are stable.
Phase B — Runners and backends
DockerRunnerwith container digest pinningDirectBackendwith streaming, bounded retries, rate-limit handling, pricing tablesAgentLoomBackendguarded by optionalagentloomdependencyParallelization: all three in parallel. #7 depends on
RunnerABC from 0.1.x; #8 depends on DirectBackend skeleton from 0.1.x; #9 depends on AgentLoom 0.5.0 availability.Phase C — Evaluator and reporter
reporter/with JSON, HTML, Markdown outputsParallelization: #10 and #11 in parallel after contract types are stable. #12 depends on evaluator output shape.
Phase D — CLI, record/replay, quickstart, CI
validate,run,replay,versioncommandsexamples/case-studies/Parallelization: #13 depends on all earlier modules. #14 depends on #13. #15 can start once #14 lands. #16 independent.
Cross-phase dependency map
What is deliberately not in 0.2.0
The deferred items are tracked but not gated by 0.2.0:
Multi-agent and A2A (defer to 0.3.0):
Corpus and statistical analysis (defer to 0.3.0):
Transversal (defer to 0.4.0):
0.5.0 release (defer to 0.5.0):
What 0.2.0 unlocks
After 0.2.0 ships:
pip install agentanvil(no extras) works end-to-end viaDirectBackend.Issue inventory (14 total)
Total in 0.2.0: 14 issues (12 enhancement + 1 chore + 1 docs).
Notes