feat: add cost-aware workflow telemetry

.codex-marketplace-install.json

@@ -0,0 +1,7 @@
+{
+  "source_type": "git",
+  "source": "https://github.com/Team-Volt/voltflow.git",
+  "ref_name": null,
+  "sparse_paths": [],
+  "revision": "f6ac8e442b0897af3e4de3c2598eaf22107b112b"
+}

README.md

@@ -37,12 +37,14 @@ The bootstrap router uses five profiles:
 | --- | --- |
 | Discovery, tests, mechanical edits | Luna high |
 | Standard implementation | Terra max |
-| Planning, integration, composite review | Sol medium |
-| Routine adversarial or correctness review | Sol high |
+| Planning and integration | Sol medium |
+| Routine adversarial or correctness review | Terra high |
 | Security, architecture, migrations, difficult ambiguity | Sol max |
 
 Direct `model` and `reasoning_effort` overrides are used when the active spawn schema supports them. Otherwise VoltFlow selects a matching agent profile when possible; if neither route exists, it inherits the parent and reports `routing degraded` instead of pretending the requested profile ran.
 
+Routine review-only agents are cost-controlled: they must explicitly use Terra high. Sol is reserved for a named authorization, private-data, payment, booking, destructive/data-integrity migration, or cross-cutting-architecture risk, or a direct user request.
+
 This table starts from the community [Codex quota frontier analysis](https://www.reddit.com/r/codex/comments/1ut3bnp/the_codex_pareto_frontier_luna_high_terra_max_sol/), checked against the different [Artificial Analysis API-cost frontier](https://artificialanalysis.ai/articles/gpt-5-6-intelligence-vs-cost-across-sol-terra-luna). It is a prior, not a permanent benchmark result. OpenAI's [GPT-5.6 prompt guidance](https://developers.openai.com/api/docs/guides/prompt-guidance-gpt-5p6) supplies the prompt shape: one outcome, explicit constraints, evidence, and a stopping condition, with each rule stated once.
 
 ## Multi-agent compatibility
@@ -88,6 +90,12 @@ node <plugin-root>/scripts/voltflow.mjs validate \
   --data-dir <plugin-data> --session <session-id> \
   --evidence "npm test"
 
+node <plugin-root>/scripts/voltflow.mjs cost \
+  --data-dir <plugin-data> --session <session-id>
+
+node <plugin-root>/scripts/voltflow.mjs report \
+  --data-dir <plugin-data> --session <session-id>
+
 node <plugin-root>/scripts/voltflow.mjs review \
   --data-dir <plugin-data> --session <session-id> \
   --lane composite
@@ -100,7 +108,11 @@ node <plugin-root>/scripts/voltflow.mjs gate \
   --data-dir <plugin-data> --session <session-id>
 ```
 
-Give the token returned by `review` to that reviewer. Its final line must be `VOLTFLOW_REVIEW: PASS <lane> <token>` or `VOLTFLOW_REVIEW: FAIL <lane> <token>`.
+Give the token returned by `review` to that reviewer and include `VOLTFLOW_REVIEW_ASSIGNMENT: <lane> <token>` in that spawn prompt. VoltFlow binds the successful spawn's agent ID, requested model, and reasoning effort to the assignment; only that agent's matching final line is accepted: `VOLTFLOW_REVIEW: PASS <lane> <token>` or `VOLTFLOW_REVIEW: FAIL <lane> <token>`.
+
+`cost` reports the planned routine-review profile, current review-round pressure, and likely usage drivers. `report` adds whole-session proxies: observed parent model metadata, visible prompt size, tool input/output byte totals grouped by category, requested subagent profiles and handoff size, test/validation activity, and review waves. Run it after discovery, before review, and at finish.
+
+Neither command reports exact tokens, billing, quota, or hidden reasoning usage because the Codex session telemetry does not expose those values to the plugin. VoltFlow persists counts and byte sizes only; it does not persist prompt, tool, or reviewer content for this report.
 
 Put the final `gate` command immediately before the provider's deploy command in the same local session or deploy wrapper. Plugin hooks are useful guardrails, but `PreToolUse` cannot intercept every possible side effect. VoltFlow does not yet provide a portable signed receipt for a separate remote CI machine, so do not describe the local state file as an authoritative remote boundary.
 

hooks/hooks.json

@@ -29,7 +29,7 @@
     ],
     "PostToolUse": [
       {
-        "matcher": "^(Bash|exec|exec_command|apply_patch|Edit|Write)$",
+        "matcher": "*",
         "hooks": [
           {
             "type": "command",