0.3.0: implement reactive triggers, >=90% test coverage, and Pentad synergy

.agents/AGENTS.md

@@ -150,7 +150,7 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 5. **Intention Dispatch**: Create execution directives with `manage_intentions(action: "create", ...)` for the runtime engine.
 6. **Reactive Replanning**: If an unexpected blocker occurs, invoke `replan(action: "blocker", goal_id: "...", blocker_description: "...")`.
 
-## 10 Core MCP Tools
+## 15 Core MCP Tools
 - `set_goal`: Manage goal hierarchy and task DAGs.
 - `evaluate_situation`: Score and rank candidate actions from environment snapshots.
 - `replan`: Adaptively reconstruct subgoals upon obstacles.
@@ -161,6 +161,11 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 - `manage_beliefs`: Structured belief state with exponential confidence decay.
 - `manage_intentions`: Wire contract directives queue for runtime execution.
 - `manage_reasoning_db`: Snapshots, diagnostics, and SHA-256 Merkle audit verification.
+- `classify`: Zero-LLM deterministic classification against hierarchical taxonomy (<2ms SLA).
+- `ask_noul`: Fast binary (Yes/No/Abstain) heuristic gate evaluating conditions (<2ms SLA).
+- `ask_choice`: Deterministic multi-alternative selection ranking candidate choices (<2ms SLA).
+- `ask_score`: Heuristic utility evaluation scoring target entities on a bounded scale (<2ms SLA).
+- `gate_intention`: Fast-path safety & feasibility filter checking preconditions before execution (<1ms SLA).
 <!-- agent-reasoning-mcp:end -->
 
 <!-- webcrypt-mcp:start -->
@@ -183,11 +188,11 @@ This project provides native `webcrypt-mcp` tooling for zero-dependency AES-256-
 
 Active Supervised MCP Servers:
 * `putervision-harness`: pv-harness start --project test_slug
-* `state-memory-mcp`: state-memory-mcp --project test_slug
-* `vision-memory-mcp`: vision-memory-mcp --project test_slug
-* `world-model-mcp`: world-model-mcp --project test_slug
-* `agent-reasoning-mcp`: agent-reasoning-mcp --project test_slug
-* `behavior-mcp`: behavior-mcp --project test_slug
+* `state-memory-mcp`: state-memory-mcp 
+* `vision-memory-mcp`: vision-memory-mcp 
+* `world-model-mcp`: world-model-mcp 
+* `agent-reasoning-mcp`: agent-reasoning-mcp 
+* `behavior-mcp`: behavior-mcp 
 * `test-custom`: npx -y @org/test-custom
 
 Always use `harness_start_loop` and supervise tasks via the PuterVision Harness.

.agents/skills/agent-reasoning-mcp/SKILL.md

@@ -27,7 +27,7 @@ This skill provides step-by-step guidance and operational patterns for interacti
 
 ---
 
-## 3. Complete 10 Consolidated MCP Tools Reference
+## 3. Complete 15 Consolidated MCP Tools Reference
 
 | Tool Name | Key Actions | Key Parameters | Description |
 |---|---|---|---|
@@ -41,3 +41,8 @@ This skill provides step-by-step guidance and operational patterns for interacti
 | `manage_beliefs` | `set`, `get`, `decay`, `list` | `key`, `value`, `confidence`, `decay_rate` | Structured belief state with temporal exponential confidence decay. |
 | `manage_intentions` | `create`, `get`, `list`, `dispatch`, `cancel` | `goal_id`, `behavior_name`, `parameters` | Execution directives queue connecting strategic plans to runtime engines. |
 | `manage_reasoning_db` | `stats`, `audit`, `snapshot`, `restore`, `prune` | `action`, `name`, `description` | Database diagnostics, snapshots, and SHA-256 Merkle audit verification. |
+| `classify` | evaluation | `category`, `input`, `taxonomy`, `state_pack` | Zero-LLM deterministic classification against hierarchical taxonomy (<2ms SLA). |
+| `ask_noul` | evaluation | `condition`, `state_pack`, `threshold` | Fast binary (Yes/No/Abstain) heuristic gate evaluating conditions (<2ms SLA). |
+| `ask_choice` | evaluation | `choices`, `context`, `state_pack` | Deterministic multi-alternative selection ranking candidate choices (<2ms SLA). |
+| `ask_score` | evaluation | `target`, `metric`, `scale`, `state_pack` | Heuristic utility evaluation scoring target entities on a bounded scale (<2ms SLA). |
+| `gate_intention` | evaluation | `project`, `proposed_action`, `state_pack` | Fast-path safety & feasibility filter checking preconditions before execution (<1ms SLA). |

.cursor/rules/agent-reasoning-mcp.mdc

@@ -11,7 +11,7 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 5. **Intention Dispatch**: Create execution directives with `manage_intentions(action: "create", ...)` for the runtime engine.
 6. **Reactive Replanning**: If an unexpected blocker occurs, invoke `replan(action: "blocker", goal_id: "...", blocker_description: "...")`.
 
-## 10 Core MCP Tools
+## 15 Core MCP Tools
 - `set_goal`: Manage goal hierarchy and task DAGs.
 - `evaluate_situation`: Score and rank candidate actions from environment snapshots.
 - `replan`: Adaptively reconstruct subgoals upon obstacles.
@@ -22,4 +22,9 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 - `manage_beliefs`: Structured belief state with exponential confidence decay.
 - `manage_intentions`: Wire contract directives queue for runtime execution.
 - `manage_reasoning_db`: Snapshots, diagnostics, and SHA-256 Merkle audit verification.
+- `classify`: Zero-LLM deterministic classification against hierarchical taxonomy (<2ms SLA).
+- `ask_noul`: Fast binary (Yes/No/Abstain) heuristic gate evaluating conditions (<2ms SLA).
+- `ask_choice`: Deterministic multi-alternative selection ranking candidate choices (<2ms SLA).
+- `ask_score`: Heuristic utility evaluation scoring target entities on a bounded scale (<2ms SLA).
+- `gate_intention`: Fast-path safety & feasibility filter checking preconditions before execution (<1ms SLA).
 <!-- agent-reasoning-mcp:end -->

.gemini/instructions.md

@@ -161,7 +161,7 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 5. **Intention Dispatch**: Create execution directives with `manage_intentions(action: "create", ...)` for the runtime engine.
 6. **Reactive Replanning**: If an unexpected blocker occurs, invoke `replan(action: "blocker", goal_id: "...", blocker_description: "...")`.
 
-## 10 Core MCP Tools
+## 15 Core MCP Tools
 - `set_goal`: Manage goal hierarchy and task DAGs.
 - `evaluate_situation`: Score and rank candidate actions from environment snapshots.
 - `replan`: Adaptively reconstruct subgoals upon obstacles.
@@ -172,6 +172,11 @@ This project uses `agent-reasoning-mcp` with project slug "behavior-mcp" to mana
 - `manage_beliefs`: Structured belief state with exponential confidence decay.
 - `manage_intentions`: Wire contract directives queue for runtime execution.
 - `manage_reasoning_db`: Snapshots, diagnostics, and SHA-256 Merkle audit verification.
+- `classify`: Zero-LLM deterministic classification against hierarchical taxonomy (<2ms SLA).
+- `ask_noul`: Fast binary (Yes/No/Abstain) heuristic gate evaluating conditions (<2ms SLA).
+- `ask_choice`: Deterministic multi-alternative selection ranking candidate choices (<2ms SLA).
+- `ask_score`: Heuristic utility evaluation scoring target entities on a bounded scale (<2ms SLA).
+- `gate_intention`: Fast-path safety & feasibility filter checking preconditions before execution (<1ms SLA).
 <!-- agent-reasoning-mcp:end -->
 
 ## State Memory (state-memory-mcp)
@@ -389,3 +394,75 @@ If the project was just initialized or is missing high-level structure (Plans, M
 1. **Inspect the Codebase**: Read the README and core files to understand the roadmap and architecture.
 2. **Scaffold the Roadmap**: Create a `plan` node (e.g., "Project Roadmap") and add `milestone` nodes representing key target phases, connecting them using `part_of` edges.
 3. **Scaffold Architecture**: Create `decision` nodes representing core technical choices (e.g., choice of databases, frameworks) and link them to the milestones/tasks using `decided_in` edges.
+
+## State Memory (state-memory-mcp)
+
+This project tracks workflow state, tasks, design decisions, and blockers using `state-memory-mcp` with project slug `"behavior-mcp"`.
+
+### 1. Priority Order
+Before doing any coding or investigation:
+1. `manage_sessions(action: "start")` — Start a tracking session for full change attribution.
+2. `get_analytics(action: "summary")` — Run to understand current project state, active branches, and overall progress.
+3. `manage_tasks(action: "next")` — Query prioritized runnable tasks.
+4. `manage_tasks(action: "find_blockers")` — Identify any active blockers preventing progress.
+5. `manage_nodes(action: "list")` — Find pending tasks, past decisions, or milestones.
+6. `query_graph(action: "trace")` — Trace what depends on or blocks a task.
+
+### 2. When to Write to the Graph
+You MUST update the graph as you work:
+- **Starting a session**: Always call `manage_sessions(action: "start", agent_id: "my-agent")` to track all mutations under a unique session.
+- **Starting a new task**: Create a node with `manage_nodes(action: "create", type: "task", title: "...", session_id: session_id)`.
+- **Making a design or implementation decision**: Document it with `manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session_id)`.
+- **Encountering a blocker**: Record the blocker with `manage_nodes(action: "create", type: "blocker", title: "...", session_id: session_id)` and connect it using `manage_edges(action: "add", type: "blocks", source_id: blocker_id, target_id: task_id, session_id: session_id)`.
+- **Adding observation notes**: Atomically log notes using `manage_nodes(action: "add_note", text: "...", attach_to: node_id)`.
+- **Batch updates**: Bulk update tasks/nodes using `manage_nodes(action: "batch_update", ids: ["..."], status: "done")`.
+- **Completing a task**: Update status to done using `manage_tasks(action: "complete", task_id: task_id)` or `manage_nodes(action: "update", id: task_id, status: "done")`.
+- **Creating/generating a new file**: Create an artifact node with `manage_nodes(action: "create", type: "artifact", title: "...", session_id: session_id)` and connect it using `manage_edges(action: "add", type: "produces", source_id: task_id, target_id: artifact_id)`.
+
+### 3. Workflow Pattern
+1. **Start of session**: Call `manage_sessions(action: "start")` to align and track work, then run `get_analytics(action: "summary")`, `manage_tasks(action: "next")`, and `manage_tasks(action: "find_blockers")`.
+2. **Task decomposition**: Decompose user requests into tasks and add them to the graph.
+3. **Execution**: Mark tasks as "in_progress", document design decisions as they occur, and log blockers if you hit any obstacles.
+4. **Validation & Resolution**: Run `run_diagnostics(action: "validate")` to ensure no cycles/orphans/contradictions, mark tasks as "done", document completed artifacts, and resolve blockers. Call `manage_sessions(action: "end")` to finalize.
+
+### 4. Codebase Seeding on Initialization
+If the project was just initialized or is missing high-level structure (Plans, Milestones, Decisions):
+1. **Inspect the Codebase**: Read the README and core files to understand the roadmap and architecture.
+2. **Scaffold the Roadmap**: Create a `plan` node (e.g., "Project Roadmap") and add `milestone` nodes representing key target phases, connecting them using `part_of` edges.
+3. **Scaffold Architecture**: Create `decision` nodes representing core technical choices (e.g., choice of databases, frameworks) and link them to the milestones/tasks using `decided_in` edges.
+
+## State Memory (state-memory-mcp)
+
+This project tracks workflow state, tasks, design decisions, and blockers using `state-memory-mcp` with project slug `"behavior-mcp"`.
+
+### 1. Priority Order
+Before doing any coding or investigation:
+1. `manage_sessions(action: "start")` — Start a tracking session for full change attribution.
+2. `get_analytics(action: "summary")` — Run to understand current project state, active branches, and overall progress.
+3. `manage_tasks(action: "next")` — Query prioritized runnable tasks.
+4. `manage_tasks(action: "find_blockers")` — Identify any active blockers preventing progress.
+5. `manage_nodes(action: "list")` — Find pending tasks, past decisions, or milestones.
+6. `query_graph(action: "trace")` — Trace what depends on or blocks a task.
+
+### 2. When to Write to the Graph
+You MUST update the graph as you work:
+- **Starting a session**: Always call `manage_sessions(action: "start", agent_id: "my-agent")` to track all mutations under a unique session.
+- **Starting a new task**: Create a node with `manage_nodes(action: "create", type: "task", title: "...", session_id: session_id)`.
+- **Making a design or implementation decision**: Document it with `manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session_id)`.
+- **Encountering a blocker**: Record the blocker with `manage_nodes(action: "create", type: "blocker", title: "...", session_id: session_id)` and connect it using `manage_edges(action: "add", type: "blocks", source_id: blocker_id, target_id: task_id, session_id: session_id)`.
+- **Adding observation notes**: Atomically log notes using `manage_nodes(action: "add_note", text: "...", attach_to: node_id)`.
+- **Batch updates**: Bulk update tasks/nodes using `manage_nodes(action: "batch_update", ids: ["..."], status: "done")`.
+- **Completing a task**: Update status to done using `manage_tasks(action: "complete", task_id: task_id)` or `manage_nodes(action: "update", id: task_id, status: "done")`.
+- **Creating/generating a new file**: Create an artifact node with `manage_nodes(action: "create", type: "artifact", title: "...", session_id: session_id)` and connect it using `manage_edges(action: "add", type: "produces", source_id: task_id, target_id: artifact_id)`.
+
+### 3. Workflow Pattern
+1. **Start of session**: Call `manage_sessions(action: "start")` to align and track work, then run `get_analytics(action: "summary")`, `manage_tasks(action: "next")`, and `manage_tasks(action: "find_blockers")`.
+2. **Task decomposition**: Decompose user requests into tasks and add them to the graph.
+3. **Execution**: Mark tasks as "in_progress", document design decisions as they occur, and log blockers if you hit any obstacles.
+4. **Validation & Resolution**: Run `run_diagnostics(action: "validate")` to ensure no cycles/orphans/contradictions, mark tasks as "done", document completed artifacts, and resolve blockers. Call `manage_sessions(action: "end")` to finalize.
+
+### 4. Codebase Seeding on Initialization
+If the project was just initialized or is missing high-level structure (Plans, Milestones, Decisions):
+1. **Inspect the Codebase**: Read the README and core files to understand the roadmap and architecture.
+2. **Scaffold the Roadmap**: Create a `plan` node (e.g., "Project Roadmap") and add `milestone` nodes representing key target phases, connecting them using `part_of` edges.
+3. **Scaffold Architecture**: Create `decision` nodes representing core technical choices (e.g., choice of databases, frameworks) and link them to the milestones/tasks using `decided_in` edges.