Agent Guide

Before making any changes, read these files to understand the project and its conventions:

README.md — what wq does, its commands, configuration, and environment variables
CONTRIBUTING.md — how to build, test, lint, and navigate the source tree

Rules

When tracking work on wq itself, always invoke it through cargo run --. Use cargo run -- --help to get the most up to date list of commands.
When encountering a Jira-style key, assume the user is talking about a ticket within wq, and use cargo run -- show <key> to view the relevant work item.
IMPORTANT: NEVER pass -C to git commands. The working directory is already the project root, so git log, git status, etc. work as-is. Do not use git -C <path> under any circumstances.
IMPORTANT: DO NOT ATTEMPT TO INSTALL cram Cram is not expected to be installed. It can be run through uv run cram.
When encountering whitespace issues in Cram tests, regenerate the expected output by running Cram with -i