feat(automation): add automation profiles and guards #196

New issue

Closed

opened 2026-02-22 23:40:02 +00:00 by freemo · 0 comments

freemo commented

2026-02-22 23:40:02 +00:00

Owner

Metadata

Commit: feat(automation): add automation profiles and guards
Branch: feature/m5-automation-profiles

Subtasks

Implement automation profiles and enforcement hooks (approval gates, max tool calls, allowlist/denylist).
Update docs/reference/automation_profiles.md with profile defaults and CLI usage.
Tests (Behave): Add scenarios for profile enforcement and override behavior.
Tests (Robot): Add Robot tests for automation profile CLI flags.
Tests (ASV): Add benchmarks/automation_profiles_bench.py for guard overhead.
Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M5: ACMS v1 + Context Scaling (Day 26)
Status: Completed

## Metadata - **Commit**: `feat(automation): add automation profiles and guards` - **Branch**: `feature/m5-automation-profiles` ## Subtasks - [x] Implement automation profiles and enforcement hooks (approval gates, max tool calls, allowlist/denylist). - [x] Update `docs/reference/automation_profiles.md` with profile defaults and CLI usage. - [x] Tests (Behave): Add scenarios for profile enforcement and override behavior. - [x] Tests (Robot): Add Robot tests for automation profile CLI flags. - [x] Tests (ASV): Add `benchmarks/automation_profiles_bench.py` for guard overhead. - [x] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [x] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M5: ACMS v1 + Context Scaling (Day 26) **Status**: Completed

Rows
Columns