kaiten-cli: Instructions file for Codex

Working on kaiten-cli

Facts and rules that are not derivable from the code. Keep it short; when a rule changes, change it here in the same PR.

Layout

• crates/kaiten-client — the published library (kaiten-client on crates.io): HTTP client, models, per-resource facades (client.cards(), client.files(), …).
• crates/kaiten — the kaiten binary (kaiten-cli on crates.io): the CLI and the MCP stdio server (kaiten mcp serve, rmcp). Both share config::resolve() and the same auth.
• One workspace version for both crates (Cargo.toml [workspace.package] + the kaiten-client pin in crates/kaiten/Cargo.toml).

Toolchain and gates

• Build with the stable toolchain. If the default toolchain is nightly without cargo, use cargo +stable … (or RUSTUP_TOOLCHAIN=stable for tools that shell out to cargo).
• Before every commit (not only before a push): cargo fmt --all -- --check, cargo clippy --all-targets -- -D warnings (clippy pedantic is on), cargo test --workspace. A failing gate blocks the commit — never commit or push code that does not compile or has red tests, even on a feature branch; if a script drives the edit, check its exit status before git commit.
• kaiten-client changes: cargo semver-checks check-release -p kaiten-client --baseline-rev v<last tag> (cargo install cargo-semver-checks --locked). CI runs it on every pull request against the PR's base commit; the check against the last release is the local one before tagging.
• Bugs are fixed test-first: write the failing test that reproduces the bug, watch it fail, then fix. New behaviour likewise gets its tests before the implementation.
• Get an independent review of the whole diff before asking the owner to merge; fix Important findings, note Minor ones.
• Commits, pushes, merges and releases happen only when the owner explicitly asks. No Co-Authored-By trailers. Commit messages follow type(scope): summary (feat, fix, test, docs, ci, chore; ! for breaking).