Docs: Campfire as a supervision UI for generated harnesses?

[stretchcloud]

Hi — thanks for MetaHarness, the generator model (harness + MCP server + governance per repo) is a great fit for how teams actually want to run agents.

I maintain Campfire (bunx the-campfire, MIT), a self-hosted, browser-based control plane for CLI coding agents (Claude Code, Codex, Goose, Aider, OpenHands, OpenClaw, OpenCode). While building out our Claude Code / Codex support I noticed that MetaHarness harnesses compose with Campfire with zero code changes: because Campfire supports runtime MCP injection, you can attach a generated harness's MCP server to a live session and its tools/governance immediately run under Campfire's permission-voting UI, session recording/replay, and cost tracking.

I've documented the flow on our side already: docs/integrations/metaharness.md.

Would you be open to a short docs page on your side covering this (something like docs/integrations/campfire.md), for harness authors targeting the claude-code/codex hosts who want a supervision UI? I'm happy to:

• write it to match your docs conventions and keep it concise/vendor-neutral in tone,
• defer entirely to you on placement (or drop it if it's not a fit),
• keep it to the integration mechanics rather than a Campfire pitch.

Totally understand if you'd rather not carry third-party integration docs — figured I'd ask before sending anything rather than open a cold PR. Either way, thanks for the project. 🔥