Implemented optional estimation_actor role for cost, risk, and duration
estimation during plan lifecycle. Estimates are persisted to plan metadata
and surfaced in CLI output. Key implementation details:
- EstimationOutput (Pydantic models): CostEstimate with currency, token
estimates, and confidence ranges; RiskScore with 0-100 scale and factors;
DurationEstimate with min/expected/max seconds. All include confidence
levels and validation. EstimationSkipped records when estimation is opted out.
- EstimationService: stateless async service that invokes estimation actor
(stub implementation for M6). Handles actor output parsing, error recovery,
and fallback to EstimationSkipped on failure.
- Integration: Plan model gains estimation_output and estimation_skipped fields.
LifecyclePlanModel adds JSON columns for persistence. PlanLifecycleService
invokes estimation during use_action unless skip_estimation is true.
- CLI: --no-estimate flag added to 'agents plan use'. plan status displays
cost (USD with token estimates), risk (score/100 with confidence), and
duration (seconds with ranges) in rich format.
- Database: Alembic migration m6_003_estimation_metadata adds
estimation_output_json and estimation_skipped_json columns to v3_plans.
- Tests: 44 BDD scenarios (features/estimation.feature) covering validation,
lifecycle integration, persistence, CLI display, and edge cases. 18 Robot
Framework smoke tests. 19 ASV benchmark suites for schema, serialization,
validation, and plan integration performance.
- Documentation: docs/reference/estimation.md with schema, configuration,
and examples. plan_cli.md updated with --no-estimate flag usage.
ISSUES CLOSED: #209
aditya
50680612d5