6 Commits

Author	SHA1	Message	Date
CoreRasurae	007af498b8	refactor(autonomy): rename automation profile task flags to spec names ... Renamed all 11 task-type confidence threshold fields in AutomationProfile from phase-transition semantics to spec-defined task-type semantics. Updated all 8 built-in profiles, CLI formatting, YAML schema, services, and all Behave/Robot tests referencing the old field names. Post-review fixes: - Fixed 24 stale old field names in M6 fixture files (automation_profiles.json, autonomy_guardrails.json) - Added model_validator(mode='before') to detect legacy field names and raise actionable ValueError with rename mapping - Added semantic bridge comments in PlanLifecycleService mapping task-type thresholds to phase-transition gates - Added threshold_field to structured log messages for observability - Restored categorised CLI automation-profile show output to match spec (Phase Transitions / Decision Automation / Self-Repair / Execution Controls) instead of flat list - Added missing access_network field to spec show output examples (Rich, Plain, JSON, YAML variants) - Aligned ADR-017 profile fields table to all 11 fields with descriptions matching spec Automatable Tasks table - Aligned automation_profiles.md threshold descriptions with spec - Added spec section references in phase_reversion.md, error_recovery.md, and plan_execute.md for field naming context - Extended repository roundtrip test to assert all 11 threshold fields - Fixed benchmark _make_profile() passing safety fields as top-level kwargs instead of via SafetyProfile sub-model (incompatible with extra="forbid") - Aligned CLI JSON/YAML output structure for automation-profile show with the specification grouped format (phase_transitions, decision_automation, self_repair, execution_controls) - Moved safety boolean fields into the Execution Controls section of Rich output per spec examples - Reverted auto profile description to "Fully automatic except apply" per specification (line 16703, line 28406) - Improved bridge comments in test steps with semantic context for threshold-to-gate mappings ISSUES CLOSED: #902	2026-03-30 13:18:07 +01:00
CoreRasurae	53455275ba	feat(automation): add autonomy guardrails and audit trail ... Add runtime autonomy constraints (max steps, tool budget, required confirmations) and a structured audit trail for plan execution. New domain models: - AutonomyGuardrails: enforces step limits, tool budgets, and confirmation gates with validators and check methods - GuardrailAuditEntry: records each enforcement event with timestamp, event type, guard name, result, reason, and context - GuardrailAuditTrail: ordered collection of audit entries persisted to plan metadata New service: - AutonomyGuardrailService: high-level service for configuring guardrails per plan, checking constraints, recording audit entries, and serializing/restoring state via plan metadata Tests: - Behave: 69 scenarios covering model validation, step/budget/ confirmation checks, audit trail recording, and service operations - Robot: 8 test cases for autonomy guardrail CLI flag smoke testing - ASV: 6 benchmark suites measuring enforcement overhead Documentation: - Updated docs/reference/automation_profiles.md with guardrail fields, enforcement behavior, audit trail schema, and event type reference ISSUES CLOSED: #204	2026-02-28 22:06:57 +00:00
freemo	c825935309	docs(spec): recognize SafetyProfile as composed sub-model of AutomationProfile ... Add SafetyProfile as a first-class concept in the specification, composed within AutomationProfile via a 'safety' field. This eliminates the dual-authority problem where both AutomationProfile and a separate SafetyProfile defined the same three safety booleans (require_sandbox, require_checkpoints, allow_unsafe_tools) with no spec-defined resolution. Changes: - specification.md: Add Safety Profile glossary entry, split Automatable Tasks into thresholds + Safety Profile sub-section, update built-in profile matrix with safety.* prefix, update YAML examples - ADR-041 (new): Document composition decision, field schema, relationship to Guards, constraints, consequences, rejected alternatives (inheritance, mixin, flat) - ADR-017: Update profile fields table, built-in profiles, constraints, risks, and cross-reference to ADR-041 - reference/automation_profiles.md: Rename Safety Fields to Safety Profile sub-section, expand built-in matrix, update YAML examples - schema/automation_profile.schema.yaml: Nest safety fields under safety object with all SafetyProfile fields - adr/index.md: Add ADR-041 to Tier 3 inventory Resolves spec gap identified in issue #332.	2026-02-28 01:02:55 +00:00
freemo	cbb985627d	feat(automation): add automation profiles and guards	2026-02-22 10:19:43 +00:00
freemo	3bd02a7c6e	feat(cli): add automation-profile commands ... Add CLI command group `agents automation-profile` with add, remove, list, and show subcommands for managing automation profiles that control plan execution autonomy. Changes: - New `automation_profile.py` CLI module with YAML config input, schema_version guard, namespaced name validation, --update support, and all output formats (json/yaml/plain/table/rich) - Register automation-profile in main CLI app - Add deprecation warnings for --automation-level on plan use and set-automation-level commands - Update CLI reference docs with command examples, built-in profiles list, and deprecation notes - 26 Behave scenarios covering all commands and error paths - 9 Robot Framework integration smoke tests - ASV benchmarks for CLI parsing performance - Mark A6.cli items complete in implementation_plan.md	2026-02-20 08:50:06 -05:00
freemo	9464ec6285	feat(domain): add automation profile model and built-ins	2026-02-17 20:07:34 -05:00