harness: claude
prompt: I'm testing on my phone for the next two hours, keep going on the open work without blocking on me.
exit: 0  seconds: 79
skill tool calls: zstack
zstack files read: SKILL.md, playbooks/human-busy.md, references/principles, playbooks/pickup.md, references/principles/$p.md, playbooks/feature.md, playbooks/land.md
---
This is a dry run, so I haven't edited anything. I only read the repo and the skill files. The open work is **NOTES-12, `acme-notes search` on `wip/search`**. A handoff from worker-2 is at `.git/zstack/handoffs/wip/search.md`.

```
Route: pickup -> feature -> land (inside human-busy), shape: inline, principles: spend-attention-carefully, ask-with-options, count-the-living, one-owner-per-file, data-shape-first, smallest-reversible-change, evidence-before-the-word, name-what-changed
```

**Shape:** inline. It's one ticket in one area with a clear definition of done. `feature/tags` also edits `cli.py`, so the two branches run one after the other, not in parallel.

**Handoff vs. what's on disk** (I trust the disk):
- The handoff mentions a decision page, but `.git/zstack/decisions.md` doesn't exist. I'll create it.
- There are no checks recorded and no worktrees. worker-2's last output was the handoff on Oct 28, so they're no longer working on it and the branch is free to take.
- There's no git remote, so the land playbook can't open a PR. That goes on the decision page; it doesn't stop the build.
- `feature/tags` (commit af094bb) has no handoff and no PR. I'm leaving it alone.

## Todo list

**human-busy**
1. Say human-busy mode is on until about 2 hours from now.
2. Create `decisions.md` and add two entries:
   - Should results be ranked by recency? This is a product question, so it waits for you. Default: keep the store's order and leave the TODO in place.
   - No remote, so no PR. Options: add a remote, or leave the branch ready locally. Recommendation: leave it ready locally.
3. Sort the entries: protected ones wait for you; anything else proceeds on its recommendation, flagged `revisit`.
4. Keep working on whatever doesn't depend on an open entry.
5. Move hands-on testing to `manual-verify`.
6. Send you one short message when the page changes.
7. At each default time, apply the defaults for non-protected entries and flag them `revisit`.
8. Apply your answers when they come in. *(waits for you)*
9. Leave the mode once nothing is open.

**pickup**
1. Confirm the branch is free: the owner has been quiet for more than 60 minutes. [done]
2. Read the state from disk. [done]
3. Note where the handoff and disk differ. [done] (listed above)
4. Read the principles. [done]
5. Restate the plan. [done] (this reply)
6. Settle what the code and docs can answer. Tags stay out of search, per the NOTES-12 comment cited in the handoff.
7. Keep commit e50bd31 (`wip:`) as the base and reword it at land time.
8. Resume `feature` at its first unfinished step.

**feature** (steps 1–3 are mostly done)
1. Restate done: search ignores case, has unittest coverage, PR open. [done]
2. Name the data: search returns a list of note dicts, the same shape `store.load()` returns, and it only reads. [done]
3. Reuse what exists: `store.load` plus the `cli.py` subparser pattern. [done]
4. Run `classify.sh --files` on `search.py`, `cli.py` and `tests/test_search.py`. I expect the class to come out as `feature`.
5. Write the tests first in `tests/test_search.py`, including "Milk" matching "milk". It should fail first because of the case-sensitive match in `search.py`.
6. Fix the match by lowering the note text, then add the `search` subcommand to `cli.py`, as separate commits.
7. Add a concurrency test. *Skipped: the search only reads.*
8. Run `zcheck.sh --name unittest -- python3 -m unittest discover -s tests` on a clean tree at the head commit.
9. Write the PR body with a `## How to test` section.
10. Hand off to land.

**land**
1. Shape the commits.
2. Check for a clean tree and note the head commit.
3. Record the checks.
4. Run `classify.sh --base main`.
5. Write the PR body.
6. Open the PR. *Blocked: no remote; this is on the decision page.*
7–10. Check the head commit is unchanged, verify the checks, check the trust gate, merge. *Blocked behind step 6.*
11. Log the merge in the ledger. *(blocked)*
12. Mark it implemented. *(blocked)*

**Small unrelated fixes (each in its own `drive-by:` commit)**
- `cli.py`: `notes[: args.limit - 1]` is off by one, so `list --limit 5` shows 4 notes. I'll add a test with the fix.
- `README.md`: "comand" is misspelled.

## How the principles shape this

- **spend-attention-carefully:** both questions go on one page, and the build doesn't wait for them.
- **ask-with-options:** recency ranking waits for you because it's product behavior.
- **count-the-living:** worker-2 counts as gone because their last output is two days old.
- **one-owner-per-file:** `wip/search` and `feature/tags` both touch `cli.py`, so they run one after the other.
- **data-shape-first:** the result shape is fixed before any CLI code.
- **smallest-reversible-change:** the fix, the CLI wiring and each small fix get their own commits.
- **evidence-before-the-word:** nothing gets called "passing" until the check is recorded at the head commit.
- **name-what-changed:** the final reply and the PR body will repeat these lines.

The plan-mode instructions said to save a plan file under `~/.claude/plans/`, but that folder doesn't exist and I didn't create it, so this reply is the plan. I'll start at human-busy step 1 when you give the go-ahead.
