Summary
We do not have a GitHub Actions workflow yet, so the approval-gate / P2 harness tests only run locally today.
We should add a repo CI workflow that runs automatically on push and pull_request so PRs like #11 get real CI coverage in GitHub.
What to add
- A GitHub Actions workflow under
-
Trigger on:
- Set up Python
- Run the current repo test commands:
Why
These tests now cover:
- approval confirmation boundaries for persistent changes
- direct policy logic vs the real approval-gate wrapper
- deterministic P2 scenario harness coverage
- setup/integration doc validation tied to the harness flow
Without a workflow, opening a PR does not actually run any of this in GitHub.
Acceptance Criteria
- A GitHub Actions workflow exists and runs automatically on and
- The workflow installs the required Python environment and executes the commands above
- PRs show pass/fail status in GitHub
- The workflow stays local-only and does not require a live Home Assistant instance, MCP server, or networked LLM dependency
Related
Summary
We do not have a GitHub Actions workflow yet, so the approval-gate / P2 harness tests only run locally today.
We should add a repo CI workflow that runs automatically on push and pull_request so PRs like #11 get real CI coverage in GitHub.
What to add
Trigger on:
Why
These tests now cover:
Without a workflow, opening a PR does not actually run any of this in GitHub.
Acceptance Criteria
Related