mmdmcy/katrust/katrust-refactor

KatRust Refactor

Read references/standard.md before editing.

Workflow

1. Confirm a clean or understood Git worktree. Preserve unrelated changes.
2. Run tests and record the baseline. Do not refactor an already failing project without identifying the failure first.
3. Run cargo katrust inspect when available; otherwise list top-level items and file sizes with rg and wc -l.
4. Classify every item in the target god module as app, feature, interface, integration, persistence, security, test, or narrowly shared code.
5. Write a capability map before moving code. Use product vocabulary already present in types, commands, routes, UI labels, and tests.
6. Add contract tests for behavior that lacks protection.
7. Move one responsibility cluster per checkpoint. Do not redesign logic while extracting it.

For large reviewed moves, scripts/extract_ranges.py may perform the mechanical copy/remove step from a hash-pinned JSON plan; semantic ownership must still be chosen before running it.

1. Run formatting, compilation, and focused tests after every move.
2. Minimize visibility. Prefer explicit imports and capability APIs over wildcard re-exports.
3. Move tests beside their owner or into matching integration-test modules.
4. Update docs/architecture.md with ownership and dependency direction.
5. Finish only when the former god module owns one clear responsibility; main.rs must contain startup and wiring only.

Guardrails

• Split by semantic ownership, never every N lines.
• Keep external process and protocol code in integrations.
• Keep durable storage in persistence or feature repositories.
• Keep UI/CLI/HTTP delivery in interfaces.
• Do not create utils.rs, speculative traits, registries, or runtime frameworks.
• Do not commit, push, reset, or delete runtime data unless explicitly requested.
• Stop and report ambiguity when naming a capability would require inventing product behavior.