docs(spec): ApproverType's description points at os explain approval-approvers-may-resolve-empty

Claude-Session: https://claude.ai/code/session_01KNKBCRDJCu5tGy3TEbvtrF
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/22161-spec-approver-type-describe.md

@@ -0,0 +1,10 @@
+---
+"@objectstack/spec": patch
+---
+
+docs(spec): `ApproverType`'s description points at `os explain approval-approvers-may-resolve-empty` for the graded `manager` routes
+
+Clause-②: no
+
+- **What changes:** the `.describe()` text of `ApproverType` (`@objectstack/spec/automation`), which the generated reference page renders for every approver entry (`content/docs/references/automation/approval.mdx`). It said `os lint` "carries the graded population routes and the full remedy". Since `@objectstack/lint` shortened `approval-approvers-may-resolve-empty`'s fix line to one sentence, the finding names two routes in one line, and `os explain approval-approvers-may-resolve-empty` prints the graded routes and the full remedy. The description now says so. Its "the request waits" clause now reads that the request falls to the node's `onEmptyApprovers` policy, which by default opens it on the organization's administrators.
+- **Unchanged:** the `ApproverType` values, the schema's shape, and what it accepts or refuses. Only the description text moves.

packages/spec/src/automation/approval.zod.ts

@@ -80,8 +80,10 @@ export const ApproverType = z.enum([
   //
   // ⛔ It POINTS at the remedy, it does not restate it. The remedy's single
   // authoritative copy is `MANAGER_ONLY_REMEDY` / `MANAGER_ONLY_ROUTES` in
-  // `packages/lint/src/validate-approval-approvers.ts`, mirrored for readers by
-  // the Approvals guide; a third copy here would be one more line to keep in
+  // `packages/lint/src/rule-explanations.ts` — the explanation
+  // `os explain approval-approvers-may-resolve-empty` prints, since the
+  // finding's `fix:` line became one sentence (#22161) — mirrored for readers
+  // by the Approvals guide; a third copy here would be one more line to keep in
   // step, and a pointer cannot drift into disagreement with what it points at.
   // ⛔ It said "that column has no product write surface" until the write
   // surface landed — the exact staleness the pointer discipline above exists to
@@ -98,11 +100,12 @@ export const ApproverType = z.enum([
   .describe(
     'Approval step approver type. `manager` is resolved from the directory rather than configured ' +
     "here: it reads the submitter's `sys_user.manager_id` at runtime, and that column is not a " +
-    'profile field an author edits, so until an operator populates it through one of the routes ' +
-    '`os lint` names, a manager step resolves to nobody and the request waits. `os lint` reports ' +
-    'that at authoring time as `approval-approvers-may-resolve-empty` and carries the graded ' +
-    'population routes and the full remedy, the node-level `onEmptyApprovers` fallback included; ' +
-    'the Approvals guide states the same remedy in prose.',
+    'profile field an author edits, so until an operator populates it, a manager step resolves to ' +
+    "nobody and the request falls to the node's `onEmptyApprovers` policy. `os lint` reports that at " +
+    'authoring time as `approval-approvers-may-resolve-empty`, and ' +
+    '`os explain approval-approvers-may-resolve-empty` carries the graded population routes and the ' +
+    'full remedy, the node-level `onEmptyApprovers` fallback included; the Approvals guide states the ' +
+    'same remedy in prose.',
   );
 export type ApproverType = z.input<typeof ApproverType>;