llm-wiki-engine 0.1.1

Git-backed wiki engine with MCP server — bring your own LLM
Documentation
# Contributing to llm-wiki

## Prerequisites

- Rust 1.93.0 — pinned in `.tool-versions`. Install via [asdf]https://asdf-vm.com/ or [rustup]https://rustup.rs/.
- `git`

## Build and Test

```bash
cargo build                      # debug build
cargo build --release            # release build
cargo test                       # all tests
cargo clippy -- -D warnings      # lint — must pass with zero warnings
cargo fmt -- --check             # check formatting
cargo fmt                        # auto-format
```

## Documentation

| Area                    | Location                                              |
| ----------------------- | ----------------------------------------------------- |
| Specifications          | [docs/specifications/]docs/specifications/README.md |
| Implementation notes    | [docs/implementation/]docs/implementation/README.md |
| Architectural decisions | [docs/decisions/]docs/decisions/README.md           |


## Adding a Feature

1. Read the relevant spec in `docs/specifications/`.
2. Implement in the correct module — see
   [docs/implementation/]docs/implementation/README.md for the module map.
3. Write tests in `tests/<module>.rs` using `tempfile::tempdir()` for all
   filesystem operations.
4. Run `cargo test`, `cargo clippy -- -D warnings`, `cargo fmt -- --check`.

### Adding an MCP tool

See [docs/implementation/mcp-tool-pattern.md](docs/implementation/mcp-tool-pattern.md).

## No LLM Dependency Rule

The wiki engine makes zero LLM calls. All intelligence is supplied by an
external LLM that calls the wiki via CLI or MCP. Do not add any LLM client
crate as a dependency.

## Dev Standards

See [docs/implementation/rust.md](docs/implementation/rust.md) for toolchain
details, error handling conventions, testing patterns, and code quality rules.

## Release Process

1. Bump `version` in `Cargo.toml`.
2. Update `CHANGELOG.md`.
3. Commit: `chore: bump version to x.y.z`.
4. Tag: `git tag vx.y.z && git push origin vx.y.z`.

Tagging triggers the release workflow — builds binaries for Linux x86_64,
macOS Intel, and macOS Apple Silicon, creates a GitHub release, and publishes
to crates.io.