# Monster Test Evidence

## Executed Baseline
- Command:
  - `node --test test/basic/*.test.js test/integration/*.test.js test/edge/*.test.js`
- Working directory:
  - `nodes/monster`
- Result:
  - `pass: 6`, `fail: 0`

## Test Matrix
| Test file | Scope | Contracts anchored |
|---|---|---|
| `nodes/monster/test/basic/constructor.basic.test.js` | initialization and output field contract | constructor, boundary setup, report output fields |
| `nodes/monster/test/basic/structure-module-load.basic.test.js` | required structure/module load guard | baseline architecture compliance |
| `nodes/monster/test/integration/flow-and-schedule.integration.test.js` | flow aggregation + rain/schedule ingestion | measured/manual flow merge, `handleInput`, schedule update path |
| `nodes/monster/test/integration/structure-examples.integration.test.js` | required examples contract guard | example flow presence/shape |
| `nodes/monster/test/edge/sampling-guards.edge.test.js` | sampling safety guards | invalid flow bounds guard, cooldown pulse throttling |
| `nodes/monster/test/edge/structure-examples-node-type.edge.test.js` | node-type structure guard | example includes `monster` node usage |

## Coverage Notes
- Structure guards now require both dashboard examples:
  - `nodes/monster/examples/monster-dashboard.flow.json`
  - `nodes/monster/examples/monster-api-dashboard.flow.json`
- Focused on the most operationally critical report fields:
  - `m3Total`
  - `m3PerPuls`
  - `pulse`
  - `running`
- Additional contract tests are still recommended for wrapper topic routes that currently map to unsupported domain handlers.