# v0.4 — Agent Topology and Governance

## v0.4.1 — Registry and model aliases
Agent identity is separated from model identity and runtime. `@brain` and `@workhorse` are aliases, not hard-coded policy in routing logic.

## v0.4.2 — Profiles and JSONC compiler
`.harness/agents.source.jsonc` is maintained source. `.harness/generated/agents.json` is generated runtime. Prompt paths are hashed and inlined; `aeh agents check` fails on active-profile drift.

## v0.4.3 — Routing and output contracts
Routing can match intent, domains, file scopes and risk. Planner, implementer, reviewer, validator, recovery and orchestrator outputs have Zod contracts. A normalized delegation task contains `id`, `summary`, `agent`, `scope`, `dependencies`, `acceptance` and `risk`.

## v0.4.4 — Typed recovery
Failures use the canonical taxonomy: `PATCH_CONTEXT_MISMATCH`, `TOOL_FAILURE`, `MISSING_CONTEXT`, `WRONG_AGENT`, `VALIDATION_FAILURE`, `REVIEW_FAILURE`, `AMBIGUOUS_OUTPUT`, `CONFLICTING_RESULTS`. Recovery actions are versioned data and bounded by the existing repair budget.

## v0.4.5 — Drift gates
The topology audit checks model/runtime references, prompt files, skills, routing references, output contracts, permission/capability coherence and source-to-generated-runtime drift.

## v0.4.6 — Permissions, capabilities and native agents
A logical agent resolves to runtime + model + optional runtime-native agent. OpenCode direct/Podman execution maps this to `opencode run --model ... --variant ... --agent ...`. Harness permissions are translated to OpenCode runtime permissions through `OPENCODE_CONFIG_CONTENT` for direct/Podman execution; OpenCode merges inline runtime config with project/global config. `gitWrite` produces explicit deny/ask/allow rules for mutating Git commands. Codex direct execution uses its bare model name. Paseo remains cross-provider transport; native-agent selection through Paseo is only allowed when that runtime explicitly declares `nativeAgentViaPaseo`, and runtime permission enforcement remains the responsibility of the configured Paseo provider.

## v0.4.7 — Graphify-assisted parallelism
Planner tasks are scheduled into waves. Dependencies and overlapping file scopes are hard conflicts. When a Graphify before-snapshot maps both scopes into the same structural community, the scheduler conservatively keeps them apart. Missing Graphify data falls back to dependency/scope scheduling.

## v0.4.8 — Finding normalization
Reviewer findings use one schema with severity, category, location, evidence, impact, recommended fix and suggested agent. Findings at the same/adjacent location with compatible categories are merged while preserving the highest severity and merge provenance.

## Compatibility
`orchestration.worker` remains as a legacy fallback when no agent topology is configured. New projects receive the topology template automatically.
