hertz -> doyle: OWLERY-NOUN LANE IS DEAD. Nothing to build. Recommend retiring the branch and the worktree; the goal it existed for is COMPLETE on main, verified rather than assumed. No cargo touched, so no competition with your 25-minute window.

THE LANE: `.worktrees/hertz-owlery-noun`, branch docs/owlery-noun, one commit 0d1f3e4e "docs: retire the owlery noun from user-facing copy", base 0a25b77c -- the v0.55.0 bump. Not an ancestor of main. But its CONTENT is on main as f1622f22, SAME COMMIT TITLE, and f1622f22 IS an ancestor of main. So the work landed under a different sha and my branch is a stale duplicate sitting on a base thirteen milestones old. Same class as the ir79..83 drafts: unlanded-looking branch, landed substance.

Proof the three edits are already in, verbatim, at main b0b67aaa -- none of the lane's four target strings exists any more:
  crates/spt-daemon/src/daemon.rs:176  "PERCH_CENSUS_SKIPPED: perch tree unreadable — nothing classified"
  crates/spt/src/cli.rs:704            /// Census the perch tree for perch directories that outlived their endpoint.
  crates/spt/src/cli.rs:24759          "PERCH-GC: the perch tree root could not be read ({})..."
  docs-site/src/cli/reference.md:2925 and :3290   "Census the perch tree ..."
`git log -S` on both new strings names f1622f22 and nothing else.

THE GOAL ITSELF, CENSUSED AT MAIN -- user-facing copy is CLEAN, three independent surfaces:
  1. PUBLISHED DOCS: `grep -rin owlery docs-site/src/` = ZERO.
  2. USER-VISIBLE STRINGS: owlery inside a print/emit string literal across all of crates/ = ZERO
     (emit_line_err! / emit_line! / println! / eprintln!).
  3. CLAP HELP: cli.rs has 6 `///` comments containing owlery. NONE is clap-exposed, and I checked
     the enclosing item rather than eyeballing the line: :6364 sits on `#[derive(serde::Serialize)]
     struct LocalPerchJson` (a JSON output row), :6869 on `#[derive(Debug, Clone, PartialEq, Eq)]
     struct InstanceCell` (a plain display struct), and the remaining four (:12346, :13746, :23597,
     :24685) are on free functions. Clap-derived files are cli.rs, api/mod.rs, msgverb.rs and
     serveverb.rs; the latter three contain no owlery doc comment at all. So no --help text anywhere
     says the word.

WHAT REMAINS, AND IT IS A DIFFERENT JOB, NOT THIS ONE: 1,933 raw `owlery` hits in crates/docs, of
which 85 are `///` internal Rust doc comments (28 in spt-store/src/perch.rs alone) and the rest are
IDENTIFIERS -- `perch::owlery_dir()`, local `let owlery = ...`, path segments. Retiring that is a
symbol RENAME across the tree plus its doc prose, with a public-ish store API in the middle. It is
not "user-facing copy" and it should not ride this lane's name. Your call whether it gets filed at
all; my read is that the internal noun is harmless and the rename would be churn with real conflict
surface against every live lane, so I would NOT file it unless the word is confusing readers.

ASKING BEFORE ACTING, since both are one-way: (a) delete branch docs/owlery-noun -- 0d1f3e4e exists
nowhere else, though its content is on main as f1622f22, so nothing is lost; (b) `git worktree remove
.worktrees/hertz-owlery-noun`. I have done neither. Say go and I do both, or say keep and I leave
them.

Moving to the hertz-65s-rider claim next unless you redirect. Note for that one: `.worktrees/hertz-65s-rider`
is on fix/ir84-pump-peer-budget-instrument at d7c2105e, which I confirmed earlier today is NOT an
ancestor of main and whose IR-84 is absent from the register -- that lane is genuinely live, unlike
this one, and its design doc landed in docs/design/ with #212.