Context
The server exposes health and metrics endpoints, and plugins have debug logging, but there is no one-command local harness that starts an isolated mem9 runtime, captures logs, runs smoke checks, and tears down cleanly.
A stronger harness would let agents reproduce bugs and validate fixes without relying on human copy-paste across terminals.
Scope
- Add scripts/dev-harness.sh or make dev-harness.
- Start server and dashboard on isolated configurable ports.
- Capture server logs, dashboard logs, health checks, and metrics snapshots.
- Run local smoke tests where possible.
- Ensure cleanup handles interrupts and failed runs.
- Document required env vars and safe defaults.
Acceptance Criteria
- One command starts a local isolated server/dashboard harness.
- Harness records logs to a predictable temp directory.
- Harness verifies /healthz and /metrics availability.
- Harness can run at least one local smoke check.
- Harness exits cleanly and tears down child processes.
- It does not require production credentials for basic operation.
Effort
~200-500 LoC net.
Context
The server exposes health and metrics endpoints, and plugins have debug logging, but there is no one-command local harness that starts an isolated mem9 runtime, captures logs, runs smoke checks, and tears down cleanly.
A stronger harness would let agents reproduce bugs and validate fixes without relying on human copy-paste across terminals.
Scope
Acceptance Criteria
Effort
~200-500 LoC net.