pikasTech-HWLAB/docs/dev-m4-agent-loop.md

DEV M4 Agent Loop

This document records the DEV-only M4 agent loop smoke for pikasTech/HWLAB#37.

Scope

• Verify the agent manager, worker workspace, explicit skills commit injection, trace/evidence chain, and cleanup behavior.
• Keep the runtime path on the fixed DEV boundary at http://74.48.78.17:16667.
• Avoid secret reads, PROD access, long-running agent tasks, and direct gateway access.

Local Checks

Run the source-only smoke first:

node scripts/m4-agent-loop-smoke.mjs

That smoke stays local and checks the runtime skeleton, workspace isolation, and explicit skills commit handling.

Live DEV Preflight

Run the live preflight only if the DEV route is reachable and the operator has authorized a short read-only window:

node scripts/dev-m4-agent-loop-smoke.mjs --live --confirm-dev --confirmed-non-production

The live path must only observe existing DEV state. It must not read tokens or secrets, must not try to run a real agent workload, and must stop if the M3 runtime preconditions are not ready.

Expected Evidence

• agent-mgr creates a scoped worker session.
• The worker workspace is isolated per session.
• The skills artifact is tied to an explicit commit.
• Trace, evidence, and cleanup records stay linked.
• If live DEV is blocked, the report must say why and keep the blocker class explicit.