chore: enforce lint-fix, import style, and doc-alignment in review

Add three style rules to review protocol:
- Forbid #[allow(...)] — all warnings must be fixed at source
- Require use-imports at file top with grouped common prefixes
- Require doc-code alignment on public API changes

Author: ktmlm

.claude/commands/mm-review.md

@@ -64,7 +64,16 @@ Check every change for:
 2. **Performance** — does this add latency to hot paths?
 3. **API compatibility** — does this change observable behavior?
 
-### Task 4: Unsafe Code Audit
+### Task 4: Code Style Enforcement
+
+Check changed files against project style rules:
+
+1. **No lint suppression** — `#[allow(clippy::...)]`, `#[allow(unused_...)]`, `#[allow(dead_code)]` etc. are forbidden. All warnings must be fixed at the source, not silenced. Report every `allow(...)` attribute in changed code as a finding.
+2. **No inline paths** — Types must be imported via `use` at the top of the file, not referenced inline as `std::collections::HashMap::new()`. The only exception is disambiguation in a single call site where two types share a name.
+3. **Import grouping** — Imports with a common prefix must be merged using nested braces: `use std::sync::{Arc, Mutex};` not separate `use std::sync::Arc; use std::sync::Mutex;`.
+4. **Doc-code alignment** — If the change modifies a public function signature, struct field, or module-level behavior, verify that the corresponding doc comments, README, and CLAUDE.md still accurately describe the current behavior. Report any stale documentation as a finding.
+
+### Task 5: Unsafe Code Audit
 
 If ANY `unsafe` block is added or modified:
 1. Read `.claude/docs/patterns/unsafe-audit.md`

.claude/docs/review-core.md

@@ -88,6 +88,13 @@ If the change touches the write path, flush, compaction, or MANIFEST:
 - Are new public APIs consistent with existing naming conventions?
 - Do new options have sensible defaults?
 
+### 4.4 Code Style Rules
+These are enforced project conventions — violations are findings (severity LOW):
+- **No lint suppression**: `#[allow(...)]` is forbidden. Warnings must be fixed, not silenced.
+- **No inline paths**: Use `use` imports at file top. No `std::foo::Bar::new()` in function bodies (exception: single-site disambiguation of name collisions).
+- **Grouped imports**: Common prefixes must be merged — `use std::sync::{Arc, Mutex};` not two separate `use` lines.
+- **Doc-code alignment**: Public API changes must have matching doc comment / README / CLAUDE.md updates. Stale docs are a finding.
+
 ## Phase 5: Reporting
 
 ### Finding Format

CLAUDE.md

@@ -50,6 +50,10 @@ Supporting documentation in `.claude/docs/`:
 ## Conventions
 
 - All clippy warnings are errors (CI enforced)
+- **No `#[allow(...)]`** — fix warnings at the source, never suppress them
+- **No inline paths** — use `use` imports at file top; no `std::foo::Bar::new()` in function bodies
+- **Grouped imports** — merge common prefixes: `use std::sync::{Arc, Mutex};`
+- **Doc-code alignment** — public API changes must update corresponding docs
 - `parking_lot` for Mutex/RwLock (non-reentrant, no poisoning)
 - `thiserror` for error types
 - `tracing` for logging