Backlogs changed from key-prefix to name-based identification.
Examples and gotchas now reflect this.

Assisted-by: Claude Opus 4.6 via pi

diff --git a/AGENTS.md b/AGENTS.md
index 2a45e53..74e958e 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -22,11 +22,13 @@ Use the `ranger` CLI to manage tasks for this project. The database lives at the
 ### Setup (first time only)
 
 ```bash
-ranger backlog create "Ranger"
+ranger backlog create "ranger"
 ```
 
 > **Note:** Always use the installed `ranger` binary for PM tasks, not `cargo run`. The repo may be in a non-compiling state during development. Install with `cargo install --path . --locked`.
 
+Set `RANGER_DEFAULT_BACKLOG=ranger` to skip `--backlog` on every command.
+
 ### Workflow
 
 All work must correspond to a task in the backlog. If the user asks for something that isn't tracked, create a task for it first, then pick it up.
@@ -134,6 +136,7 @@ The integration test (`tests/cli.rs`) exercises the full workflow via the compil
 - `sqlx::raw_sql` is used for migrations (multiple statements in one file). `sqlx::query` only runs one statement.
 - SQLite foreign keys must be enabled per-connection (`foreign_keys(true)` on connect options).
 - The `xdg` crate resolves `$XDG_DATA_HOME/ranger/ranger.db`. Override with `RANGER_DB` env var or `--db` flag.
+- Backlogs are identified by name, not key. `RANGER_DEFAULT_BACKLOG` sets the default for `--backlog` flags.
 - Migration uses `CREATE TABLE IF NOT EXISTS` so it's idempotent (safe to run on every connect).
 
 ## VCS
diff --git a/README.md b/README.md
index 3caef38..a9b5365 100644
--- a/README.md
+++ b/README.md
@@ -56,16 +56,18 @@ cargo run --bin ranger -- <command>
 ### Quick start
 
 ```
-ranger backlog create "My Project"
-ranger task create "First thing to do" --backlog <key>
-ranger task create "Second thing" --backlog <key> --state queued --tag urgent
-ranger task list --backlog <key>
+ranger backlog create "my-project"
+ranger task create "First thing to do" --backlog my-project
+ranger task create "Second thing" --backlog my-project --state queued --tag urgent
+ranger task list --backlog my-project
 ranger task edit <key> --state in_progress
 ranger comment add <key> "Started working on this"
 ranger task show <key>
 ```
 
-Use `--json` on any command for machine-readable output. Tasks and backlogs are referenced by key prefix — type just enough characters to be unique.
+Use `--json` on any command for machine-readable output. Backlogs are identified by name. Tasks are referenced by key prefix — type just enough characters to be unique.
+
+Set `RANGER_DEFAULT_BACKLOG` to skip `--backlog` on every command.
 
 The database lives at `$XDG_DATA_HOME/ranger/ranger.db` by default. Override with `--db <path>` or `RANGER_DB` env var.