feat(freehire-search): add --no-description for cheap discovery passes

A default search hydrates full bodies - ~73% of the payload, ~20k tokens
per query fed into agent context - while /scrape's own Step 2 says to
pre-filter by title before reading bodies. The flag keeps every other
field and drops the bodies (live 10-result search: ~58k -> ~10k chars);
hydration stays the default per the documented trade-off. The API
returns bodies regardless of include_description=false (verified live),
so the lean guarantee is enforced client-side. Review opportunity O1
(2026-08-19), approved as an enhancement.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -15,6 +15,13 @@ per-file diff commands.
 
 ### Added
 
+- **`freehire-search` gains `--no-description` for cheap discovery passes** - a default
+  search hydrates full description bodies (~73% of the payload, ~20k tokens per query)
+  while `/scrape` is told to pre-filter by title before reading bodies. The new flag
+  drops the bodies (a live 10-result search shrinks from ~58k to ~10k chars) while
+  keeping every other field; hydration stays the default. The API currently returns
+  bodies regardless of `include_description=false`, so the lean guarantee is enforced
+  client-side. Pinned in `tests/commands.test.ts`.
 - **Fixture coverage for linkedin's date/location and jobindex's `parseSearchPage`** -
   linkedin's search-card fixture carried no `<time>` or location element, so deleting
   the `date` extraction (a `/scrape` contract field on a default-ON portal) left every