Next Steps — Durable Agent Runtimes & Harness Engineering

Part of durable-agent-runtime/index

Open questions

Which repos get the .agents/setup-style contract first (clan-private, law retrieval, idx-cli)?
Should the dev-server + ports-file pattern be a shared script library in clan-private or per-repo?
Is hypeman worth an evaluation build on hermes-vm (per-task VM with standby) vs NixOS containers?
Revisit Cloudflare Code Mode for our Effect TS stack: tools-as-typed-API vs tool-calling.
Does the Forgejo webhook → kanban wake need a new service, or does an existing cron/webhook path cover it?

Research topic: durable-agent-runtime — covers durable objects, stateful machines, and harness engineering (sandboxed or not).
Do NOT build a distributed durable-object layer (celld) or actor platform (rivet) on a single box.
Do NOT build an E2B-style per-thread VM fleet; use NixOS-native isolation when needed.
DO build environment contracts: per-repo setup hooks, AGENTS.md per repo, dev-server skills, event wake.