docs(integrations/openmanus): update to v0.6.0 — bourdon CLI, commit_to_federation, PATH gotcha

[ryandavispro1-cmyk]

Summary

Brings `docs/integrations/openmanus.md` in line with current Bourdon state. Three drift issues caught while cleaning up the equivalent stdio example over on FoundationAgents/OpenManus#1363:

1. Stale command. This doc still uses `python -m core.l6_server` everywhere. Every other published integration doc (`claude-desktop.md`, `claude-code.md`, `cursor.md`) uses `bourdon serve --quiet` — the `bourdon` CLI shipped in v0.5.0 and is the canonical pattern. This doc was the odd one out.
2. Missing `commit_to_federation`. v0.6.0 shipped the write-side tool 2026-05-11. The tool table here only lists the six read-side tools from v0.5.0. OpenManus is exactly the kind of cloud-only agent that benefits from the write-side path (no adapter code needed; the agent contributes via MCP directly).
3. No PATH gotcha. MCP subprocesses inherit a minimal PATH, so `"command": "bourdon"` silently fails when Bourdon lives in a venv. Both `claude-desktop.md` and `claude-code.md` document this; this doc didn't.

Changes

• Tool table gains a `commit_to_federation` row marked `(v0.6.0+)`.
• Prerequisites step 1: `pip install bourdon (currently 0.3.0)` → `pip install 'bourdon[server]'` (no version pin — drifts less). Drops the dual `bourdon` + `python -m core.l6_server` requirement in favor of just the CLI.
• Prerequisites step 3 verification command: `python -m core.l6_server --library ~/agent-library` → `bourdon serve --quiet`.
• Three config blocks updated (default stdio, stdio with `--library`, HTTP/sse fallback). All now use `bourdon serve [--quiet]`.
• Troubleshooting bullet about Python paths replaced with a pointer to the new PATH gotcha section.
• New PATH gotcha section at the end mirroring the content in `claude-desktop.md` and `claude-code.md`. Documents the absolute-venv-path fix.

No content changes to the visibility model, tradeoffs, or related sections. This is a CLI-pattern + version + missing-tool update, not a rewrite.

Why this PR exists

PR #58 in this repo added `claude-code.md` using `bourdon serve --quiet` as the canonical command. PR FoundationAgents/OpenManus#1363 adds the same shape as an example in OpenManus's `mcp.example.json`. Both reference back to this doc. Without this PR, the trail of breadcrumbs leads readers to a doc that contradicts the example they just saw — exactly the kind of inconsistency that gets a downstream docs PR pushed back.

Test plan

• All three config-block JSON snippets validate
• PATH gotcha section content matches `claude-desktop.md` and `claude-code.md` for consistency
• No links broken (`docs/agent-integration-status.md`, `docs/integrations/claude-code.md` exist after PR docs: add Claude Code MCP integration guide #58)
• CI green

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes that update commands and troubleshooting guidance; no runtime or security-sensitive code paths are modified.

Overview
Updates the OpenManus integration docs to use the canonical bourdon serve --quiet CLI (including install instructions and all stdio/--library/HTTP examples) instead of python -m core.l6_server.

Adds the new commit_to_federation tool to the L6 tool table and introduces a PATH gotcha troubleshooting section explaining why "command": "bourdon" can fail under MCP subprocess PATHs and how to fix it with an absolute venv binary path.

^{Reviewed by Cursor Bugbot for commit 04f65b9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sentry]

Bug: A Markdown link in the prerequisites points to claude-code.md, a file that does not exist, which will result in a 404 error for users.
_{Severity: MEDIUM}

Suggested Fix

Create the missing claude-code.md file with the appropriate content. Alternatively, if the link is incorrect, update its target to the correct file. If the linked content is not supposed to exist, remove the link entirely.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/integrations/openmanus.md#L28

Potential issue: The updated prerequisites in `docs/integrations/openmanus.md` introduce
a Markdown link `[docs/integrations/claude-code.md](claude-code.md)`. This link points
to a file, `claude-code.md`, which does not exist in the `docs/integrations/` directory.
Any user who follows the setup instructions for the Claude Code adapter and clicks this
link will encounter a 404 error, breaking the documentation flow and preventing them
from completing the setup.

_{Did we get this right? 👍 / 👎 to inform future reviews.}