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

[qq9340100]

Fixes#10266

What was stale

JobHandler's docblock in packages/spec/src/contracts/job-service.ts still said
consuming a { outcome: 'degraded' } resolution was "not yet wired" — that the
shipped adapters discarded the value, and that this was precisely why doing so was
safe. #7072 landed the wiring and inverted both halves of that sentence: the value
is consumed, and the "safe because unread" argument no longer holds.

Re-measured against current main

• packages/services/service-job/src/cron-job-adapter.ts —
  if (outcome && outcome.outcome === 'degraded') { execution.status = 'degraded'; execution.error = outcome.reason; }
• packages/services/service-job/src/interval-job-adapter.ts — same mapping
• packages/services/service-job/src/db-job-adapter.ts — settles the run as
  degraded (onAttemptSettled), writes the reason to error / last_error
  (bumpJob), and leaves failure_count flat
• packages/platform-objects/src/audit/sys-job-run.object.ts and sys-job.object.ts
  — both status / last_status selects carry degraded in their ObjectQL-enforced
  vocabularies, each with a [#7072] comment pinning them to JobExecutionStatus

The fix

Rewrote the "not yet wired" paragraph to state the wired behaviour, aligned in
wording with JobExecutionStatus's already-correct TSDoc in system/job.zod.ts
(same "NOT a failure, never retries" framing, same reason-in-error-column /
failure_count-flat facts) rather than inventing a third phrasing. The #5548/#6617
framing above the paragraph is untouched. No signature or type change (Clause-②: no).

Changeset

Skipped, following the #10168 precedent (JSDoc/TSDoc block-comment change, not a
Zod .describe() call, no changeset) rather than #10173's (which changed
.describe() text feeding generated reference docs and shipped one). This PR
touches only a /** ... */ block comment above a type alias — no .describe(),
no generated reference page derives from it (verified: no match for job-service,
JobHandler, or JobRunOutcome under content/docs).

Tests

Prose-only change to a docblock; no behaviour, type, or test-visible surface
changed. Verified by re-reading the three adapters and the two enforced select
vocabularies on current main (excerpts above) rather than by transcribing the
issue card's measurements.

Gates run against node scripts/pm/dispatch-gates.mjs's named list (all VERDICT
command-exit 0, re-run at 176acc71c — identical tree to what was staged, no
further edits after):

• pnpm check:changeset-gate-self-tests, pnpm check:cross-package-test-inputs,
  pnpm check:merge-driver, pnpm check:slot-lookup, pnpm check:spec-parsed-alias,
  pnpm check:type-source-resolution
• pnpm --filter @objectstack/lint run check:doc-formula-expressions
• pnpm --filter @objectstack/spec run check:empty-state / check:liveness / check:strictness-ledger / check:variant-docs
• node scripts/check-adr-0087-registration.mjs, node scripts/check-dev-prereqs.mjs
  (after a full pnpm build), node scripts/docs-audit/check-affected-docs.mjs
• pnpm --filter @objectstack/spec typecheck (tsc --noEmit clean; test-typecheck
  debt ledger unchanged, shrink-only)

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 1 changed file(s) yielded no anchor (packages/spec/src/contracts/job-service.ts) — pages documenting those are invisible to this run

Coarse fallback — 116 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 6276651dc1ece03f93f17227ac957b908a2dbd9e → packageMentionDocs.