# Example Configurations

This folder provides ready-to-copy configuration sets for common project stacks.

- `node/`: Node.js-focused gate commands and coverage parsing (`lcov`).
- `java/`: Java (Maven)-focused gate commands and coverage parsing (`jacoco_xml`).

Each stack includes:

- `policy.yaml`
- `gates.yaml`
- `agents.yaml`

Usage:

1. Pick a stack folder.
2. Copy its files into `config/agentic/orchestrator/`.
3. Adjust commands, paths, and thresholds to your repository.

Important:

- `policy.yaml -> implementation.workspace` and `policy.yaml -> testing.framework` are control-plane invariants for this project and stay `nx`/`vitest`.
- Target-repo test/build behavior is defined by `gates.yaml` commands and coverage parsers.
- For Java projects, use the Java `gates.yaml` Maven commands (`./mvnw ...`) and `jacoco_xml` parser.
- `policy.yaml -> supervisor.max_iterations_per_phase` controls planner/builder/qa loop reconciliation iterations (default `6`).
- `policy.yaml -> rbac.orchestrator` includes `feature.delete` for the delete command path.
- `agents.yaml -> runtime.default_provider` supports `kiro-cli` and `copilot` in addition to existing providers.
- `agents.yaml -> runtime.provider_configs.<provider>` can hold provider-specific command payloads (for example `command: kiro-cli`, `args: [chat, --agent, dev]`).
