feat(connectors): add Codebuff (Manicode) — 20th agent

[anandghegde]

Summary

Wires Codebuff (formerly Manicode) into cass as the 20th supported coding-agent connector — the only one of the major CLI coding agents currently missing from the unified timeline.

README intro before / after:
…OpenClaw, Clawdbot, Vibe, Crush, Kimi Code, Qwen Code, Codebuff (Manicode), and Factory (Droid)…

The on-disk discovery + parser implementation lives in franken_agent_detection; this PR adds the cass-side wiring following the established pattern (see aider.rs / amp.rs).

Changes

• src/connectors/codebuff.rs — new module: thin pub use franken_agent_detection::CodebuffConnector; re-export stub.
• src/connectors/mod.rs — registers pub mod codebuff;.
• README.md:
  • Added Codebuff to the top-line supported-providers blurb.
  • Added a new bullet under How it reads data documenting the
    ~/.config/manicode/projects/<project>/chats/<chatId>/chat-messages.json
    layout, the run-state.json cwd recovery, the manicode-dev /
    manicode-staging channels, and the CODEBUFF_DATA_DIR /
    MANICODE_DATA_DIR overrides.
• CHANGELOG.md — [Unreleased] entry.
• Cargo.toml + build.rs — franken-agent-detection git pin temporarily flipped to @anandghegde/franken_agent_detection rev e7fffb67c4dd52007a487cd06401ea7197d9a664 so the cass build is fully self-contained while the FAD-side PR is in review. Both files carry a TODO comment pointing at each other.

Storage layout (recap)

Reverse-engineered from getagentseal/codeburn#124:

~/.config/manicode/                       # legacy on-disk name still used post-rebrand
  projects/<projectBasename>/
    chats/<chatId>/
      chat-messages.json                  # serialized ChatMessage[]
      run-state.json                      # SDK RunState snapshot

chatId is the chat's ISO-8601 timestamp with : replaced by -. The connector consults run-state.json to recover the real cwd, so sessions group by the originating project directory (not the sanitized folder name).

Verification

cargo check          # green on x86_64-apple-darwin

The 12 unit tests for the connector itself live in the upstream PR (FAD connectors::codebuff::tests::*, all passing alongside the existing 663 FAD tests).

Companion PR

• Dicklesworthstone/franken_agent_detection — adds the actual CodebuffConnector implementation. This cass PR depends on the FAD PR landing first, after which the maintainer (or I, in a follow-up commit) should:
  1. Flip the FAD git URL in Cargo.toml and build.rs back to Dicklesworthstone/franken_agent_detection.
  2. Bump the rev to the merge commit.

Filed as a draft until the FAD PR is reviewed.

[Dicklesworthstone]

Thanks for the cass-side wiring. Closing per project policy (no outside merges) — same disposition as the FAD companion at Dicklesworthstone/franken_agent_detection#6.

The thin-stub pub use franken_agent_detection::CodebuffConnector; pattern matches the existing connector style cleanly, and the README pointers to the on-disk storage layout (chat-messages.json, run-state.json cwd recovery, manicode-dev/staging channels, CODEBUFF_DATA_DIR override) are useful intel either way.

If I do pick up Codebuff coverage later I'll do the implementation independently per policy. Until then, the temporary @anandghegde/franken_agent_detection git pin in Cargo.toml/build.rs is a clean signal that this is a draft-state PR — fine to close as-is.

Thanks again.