fix(jobindex-search): reject a --sort other than score or date instead of sending it to the portal (#647)

* fix(jobindex-search): reject a --sort other than score or date instead of sending it to the portal

--sort was a free z.string(), and jobindex does not reject an unknown sort:
--sort newest came back exit 0 in an order that is neither relevance nor
date, so the newest-first sort a caller asked for was silently not applied.
Make it an enum of the two documented values, like --format, so any other
value fails schema validation before a request is sent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* changelog: place the #647 entry under [Unreleased]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Mads Lorentzen <madslorentzen_17@hotmail.com>

CHANGELOG.md

@@ -131,6 +131,13 @@ per-file diff commands.
   the flag is still a location-only search. The Danish portals (#573) and `freehire-search`
   (#568) already reject a value-less option.
 
+- **`jobindex-search` rejects a `--sort` other than `score` or `date` instead of sending it to the
+  portal** (#647, `.agents/skills/jobindex-search/cli/src/commands/search.ts`,
+  `tests/sort-values.test.ts`) - the option was a free string, and jobindex does not reject an
+  unknown sort: `--sort newest` returned exit 0 in an order that was neither relevance nor date,
+  so the requested newest-first sort was silently not applied. The option is now an enum like
+  `--format`, and any other value exits 1 with the CLI's validation error before any request.
+
 ## [1.7.3] - 2026-10-19
 
 ### Added