test(portals): cover linkedin card date/location and jobindex parseSearchPage

The linkedin fixture was purpose-built for entity decoding and had no
<time> or location element, so removing the date extraction - a /scrape
contract field on a default-ON portal - survived the suite. jobindex's
parseSearchPage (the Stash parser behind every search) had zero tests,
so meta.total silently dropping hitcount survived too. Both mutations
now fail exactly the new tests. The ASAP deadline branch is deliberately
left to the F12 fix, which changes its behaviour to null. Review finding
F35 (2026-08-19).

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

CHANGELOG.md

@@ -15,6 +15,13 @@ per-file diff commands.
 
 ### Added
 
+- **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
+  test green; jobindex's Stash parser had no tests at all, so `meta.total` could stop
+  using `hitcount` unnoticed. Four new linkedin cases (both listdate class variants,
+  location, absent-element nulls) and a new jobindex `search-page.test.ts` (hitcount
+  vs page count, contract-field mapping, deadline fallbacks). Both mutation-verified.
 - **Tests for `check_framework_version.py`** - the CI gate that stops a framework file
   from being edited without a `framework_version` bump had zero tests, so the one-line
   mutation `return meaningful_changes > 0` -> `return False` disabled it while the suite