Decision CLI and MCP Driver

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

The decision driver gives operators one compact surface for governed classification workflows without replacing the existing dispatcher.

CLI:

Use AIWG to complete this documented outcome: The decision driver gives operators one compact surface for governed classification workflows without replacing the existing dispatcher.
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

MCP:

Set `AIWG_MCP_TOOLSETS=decision` to expose the decision tools. Evaluation is disabled unless both `AIWG_DECISION_ENABLED=1` and the per-call `opt_in` flag are present. MCP evaluation accepts only named profiles from `AIWG_DECISION_MCP_REQUESTS`, for example:

{
  "demo": {
    "requestPath": "/absolute/path/to/dispatcher-request.json",
    "hostPolicyModulePath": "/trusted/decision-host-policies.mjs"
  }
}

MCP tools never accept arbitrary adapter or host-policy module paths from tool arguments. If advanced dispatcher `hostPolicies` are needed, the server operator pins the trusted module in `AIWG_DECISION_MCP_REQUESTS` and the tool call selects only the profile name. The CLI keeps `the request option <path>` and `the host-policy-module option <path>` for an operator-controlled shell workflow.

The synthetic setup command emits reviewable JSON files and a dispatcher request that points to the shipped offline fixture adapter. It does not configure live defaults and it does not execute actions.