refactor(v4-removal)!: move the Rust SDK onto ACS v5 manifests

agent-governance-rust/Cargo.toml

@@ -10,6 +10,7 @@ repository = "https://github.com/microsoft/agent-governance-toolkit"
 rust-version = "1.89"
 
 [workspace.dependencies]
+agent_control_specification = { path = "../policy-engine/sdk/rust", version = "0.3.1-beta.0" }
 agentmesh-mcp = { path = "agentmesh-mcp", version = "5.0.0" }
 aes-gcm = "=0.11.0"
 assert_cmd = "=2.2.2"

agent-governance-rust/agentmesh/Cargo.toml

@@ -1,3 +1,3 @@
 [package]
 name = "agentmesh"
 version.workspace = true
@@ -29,6 +29,7 @@
 required-features = ["cli"]
 
 [dependencies]
+agent_control_specification.workspace = true
 agentmesh-mcp.workspace = true
 aes-gcm.workspace = true
 base64.workspace = true

agent-governance-rust/agentmesh/MIGRATION_V5.md

@@ -0,0 +1,84 @@
+# Rust framework policy migration
+
+`FrameworkGovernanceAdapter` now consumes native Agent Control Specification
+objects. The removed local framework policy and pattern types are not
+translated at runtime.
+
+```rust
+use agentmesh::{
+    AgentControl, FrameworkGovernanceAdapter, FrameworkKind, Manifest,
+};
+
+let manifest = Manifest::from_path("manifest.yaml")?;
+let control = AgentControl::from_manifest(manifest)?;
+let adapter = FrameworkGovernanceAdapter::new(
+    FrameworkKind::Tower,
+    MyHook,
+    control,
+);
+```
+
+Move tool catalogs, intervention-point bindings, budgets, approval rules, and
+content policies into the manifest. Keep framework-only drift and checkpoint
+settings in `FrameworkHostConfig`.
+
+Legacy-shaped YAML is rejected with `runtime_error:manifest_invalid`. The Rust
+SDK does not guess at or partially translate removed fields.
+
+## Budgets are host-reported
+
+`FrameworkGovernanceAdapter` counts tool calls itself and tracks elapsed time
+from construction, but it mediates requests without ever seeing a model
+response, so it cannot observe tokens or cost on its own.
+
+Call `record_usage` after each model call, or manifest budget rules keyed on
+`token_count` or `cost_usd` will evaluate against zero and never fire:
+
+```rust
+let adapter = FrameworkGovernanceAdapter::new(FrameworkKind::Actix, hook, control);
+// ... after a model call returns usage ...
+adapter.record_usage(response.total_tokens, response.cost_usd);
+```
+
+`tool_call_count` and `elapsed_seconds` need no host involvement.
+
+## Removed: `FrameworkExecutionResult::matched_patterns`
+
+The field carried the regex rule ids matched by the v4 pattern engine. ACS
+returns a verdict with a reason rather than a match list, so the field had no
+source and would have returned an empty vector on every call. It is removed
+rather than left in place, so code that read it fails to compile instead of
+silently seeing no matches. Read `decision` and the emitted `events` instead.
+
+## `with_host_config` returns `Result`
+
+It previously panicked on a `FrameworkHostConfig` outside the valid range. It
+now returns `RuntimeError::ManifestInvalid`. `new` is unchanged and stays
+infallible, because the default config is valid by construction.
+
+## A manifest must bind every point the adapter evaluates
+
+The runtime denies an intervention point the manifest does not declare
+(`runtime_error:intervention_point_unknown` becomes a `Deny`). Failing closed is
+the right default, but it makes a minimal first manifest look broken: the
+adapter evaluates `input` on every `execute()` and `pre_tool_call` on every tool
+call, so a manifest binding only one of them denies everything on the other path
+with no obvious cause.
+
+Bind both:
+
+```yaml
+intervention_points:
+  input:
+    policy_target: $.input.body
+    policy:
+      id: your_policy
+  pre_tool_call:
+    policy_target: $.tool_call.args
+    tool_name_from: $.tool_call.name
+    policy:
+      id: your_policy
+```
+
+If a deny appears with `intervention_point_unknown` in the reason, the manifest
+is missing the point rather than the policy rejecting the request.