docs(spec): JobHandler docblock states degraded consumption is wired (#10266) (#10434)

The `JobHandler` TSDoc's "not yet wired" paragraph was inverted twice over by
#7072's landing: consuming a resolved `{ outcome: 'degraded' }` is no longer
discarded, and "safe because unread" no longer holds.

Re-measured against current main:

- cron-job-adapter.ts and interval-job-adapter.ts map a resolved `degraded`
  outcome onto `execution.status = 'degraded'` / `execution.error`.
- db-job-adapter.ts settles the run as `degraded`, writes the reason to
  `error` / `last_error`, and leaves `failure_count` flat.
- sys_job_run.status and sys_job.last_status both carry `degraded` in their
  ObjectQL-enforced select vocabularies (#7072), pinned to stay in step with
  JobExecutionStatus.

Rewrote the paragraph to state the wired behaviour, aligned in wording with
JobExecutionStatus's already-correct TSDoc in system/job.zod.ts rather than
inventing a third phrasing. The #5548/#6617 framing above stays untouched.
Prose only — no signature or type change (Clause-②: no).

No changeset: JSDoc/TSDoc block-comment change, not a Zod `.describe()` call
that feeds generated reference docs — same precedent as #10168, not #10173.

Claude-Session: https://claude.ai/code/session_016gcKVsiywU9CcS96S5t9qD

Co-authored-by: Claude <noreply@anthropic.com>

Author: Jack Q

packages/spec/src/contracts/job-service.ts

@@ -106,8 +106,16 @@ export interface JobRunOutcome {
  *
  * The reporting channel is deliberately opt-in on **both** ends. Consuming it
  * — mapping `degraded` onto a `sys_job_run.status` distinct from `success` —
- * is #5548's half and is **not yet wired**: the shipped adapters currently
- * discard the resolved value, which is precisely why doing so is safe.
+ * is #5548's half, and it is wired: all three shipped adapters
+ * (`cron-job-adapter.ts`, `interval-job-adapter.ts`, `db-job-adapter.ts`) map
+ * a resolved `{ outcome: 'degraded' }` onto a run status distinct from
+ * `success`, the `reason` lands in `error` / `last_error`, and
+ * `failure_count` stays flat — never a retry, never an alert. Both
+ * `sys_job_run.status` and `sys_job.last_status` carry `degraded` in their
+ * ObjectQL-enforced select vocabularies (#7072), which must stay in step with
+ * {@link JobExecutionStatus} in `system/job.zod.ts` — see that type's TSDoc
+ * for the full mapping and the cost of routing `reason` through an "Error"
+ * column.
  */
 export type JobHandler = (context: { jobId: string; data?: unknown }) => Promise<void | JobRunOutcome>;