devharness-contributing

Conventions for writing code in the devharness repo itself (as opposed to using its tools to debug some other app) — how tool failures propagate, why behaviour must read _meta rather than rendered text, where each kind of documentation lives, and the release rules an agent gets wrong. Use when editing files under src/, adding or changing an MCP tool, cutting a release, or debugging why a rebuild didn't take effect…