[knihit]

Description

CI:

• validate-pr.yml runs the root make lint, which lints cli, mcp and shared (clippy with -D warnings, then cargo fmt --check), so a crate added there is linted in CI too. PR CI ran the Rust tests but never linted them, so formatting drift went unnoticed.
• Only the lint step is pinned: it installs Rust 1.98.1 with clippy and rustfmt and runs make lint CARGO="cargo +$RUST_LINT_TOOLCHAIN". On floating stable, each Rust release could add clippy lints that -D warnings turns into failures on every PR. Builds and tests stay on floating stable, the toolchain release.yml ships with, so a stable-only break still shows up in PR CI. A root rust-toolchain.toml was not used, because it would also pin release builds and every contributor's local cargo. Bump RUST_LINT_TOOLCHAIN deliberately.

Formatting:

• cargo fmt on four mcp/servers/skill-lookup/tests/ files that had drifted from rustfmt's output: find_skills_shakedown.rs, full_tool_surface.rs, get_skill_shakedown.rs and handshake_shakedown.rs. Line wrapping only.

CHANGELOG: one bullet in a new ### Added section under [Unreleased].

Docs: appendix/contributing.md (and both HTML bundles) give make lint CARGO="cargo +1.98.1" as the pre-PR check, so a local run matches CI's lint toolchain.

Type of Change

• Infrastructure / pipeline

Testing

• make lint passes on Rust 1.98.1 (RUSTUP_TOOLCHAIN=1.98.1). Before the formatting change, make -C mcp lint failed on those four files.
• make -C mcp test-rust passes after formatting.
• The workflow parses.
• npm test: not affected
• cd cli && make test: no cli/ changes

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own changes
• My changes generate no new warnings

Notes for Reviewers

• docs/site/.user-guide.manifest is re-recorded because contributing.md changed, and build-user-guide.sh --check hashes the Markdown tree. It does not hide anything new: main already records the current Markdown hash and its --check passes, while both bundles on main still lack the install-kiro-power and install-claude-plugin-marketplace pages. Getting those pages into the bundles needs a full guide rebuild, which belongs in its own PR.
• Lint stays the last step of Status Checks rather than a separate job. Status Checks is the required check, so a separate job would block nothing until the branch rule is changed, and running lint first would hide test results instead.
• make guide-check now compares the lint toolchain named in the guide and both bundles with RUST_LINT_TOOLCHAIN.