* feat(search): include closed issues by default (bd-t5yex)
The dominant real-world search query is 'was this already
found/filed/fixed?' — exactly the query where silently excluding closed
issues produces a false 'no'. Downstream repos grew shell wrappers
(wyvern's bd-find.sh) purely to undo the open-only default; when a repo
writes a wrapper to change a default, the default is probably wrong.
Reverses the hq-319 open-only default on both the embedded and
proxied-server paths. bd list keeps its open-only default. --status open
(etc.) narrows explicitly; --status all still works, now redundantly.
No in-repo programmatic caller depends on the old default (prime/skill
docs mention the command generically; docs/cli-reference regenerates
from the release pin). Changelog note added; embedded + proxied search
suites green including new default_includes_closed coverage both paths.
* fix(search): review fixes — conformance corpus spec, page-eviction + bd-query-divergence docs (bd-t5yex)
Fable adversarial review (FIX_THEN_MERGE) items:
- test/conformance corpus: the search-desc-contains-and-status scenario's
comment still documented the old closed-exclusion default (the corpus
comments are the written spec future backends build against), and the
flip left the scenario with two identical steps — comment updated and
one step switched to --status open to keep an explicit exclusion probe.
- CHANGELOG + help: document the page-eviction consequence (matches
beyond --limit are dropped under a status-blind sort; use --status open
or raise --limit when hunting live work) and that bd query / HTTP q=
deliberately keep their closed-exclusion default.