skills: satisfy role-word guard (ADR-0090 D3)

Replace the two new 'role' usages introduced by the review wave
(junction-attribute example → position; phantom-key example → approvals:)
and ratchet the baseline down for the three files whose role-word count
improved.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Kj2MJEPXoUXC4LiC3XYJc

Author: claude

scripts/role-word-baseline.json

@@ -34,12 +34,12 @@
   "content/docs/releases/v14.mdx": 5,
   "content/docs/releases/v16.mdx": 5,
   "content/docs/ui/forms.mdx": 3,
-  "skills/objectstack-ai/SKILL.md": 8,
+  "skills/objectstack-ai/SKILL.md": 6,
   "skills/objectstack-api/SKILL.md": 1,
   "skills/objectstack-automation/SKILL.md": 1,
-  "skills/objectstack-data/SKILL.md": 8,
+  "skills/objectstack-data/SKILL.md": 4,
   "skills/objectstack-data/rules/relationships.md": 1,
-  "skills/objectstack-platform/SKILL.md": 3,
+  "skills/objectstack-platform/SKILL.md": 2,
   "skills/objectstack-query/rules/filters.md": 9,
   "skills/objectstack-ui/SKILL.md": 2
 }

skills/objectstack-data/rules/field-types.md

@@ -76,7 +76,7 @@ options: [
 > **`multiple: true` lookup ≠ junction object.** A multi-value lookup is stored
 > and read as an **array of ids** on the record — it is NOT a junction table.
 > Reach for a **junction object** (two lookups) only when the relationship
-> itself carries attributes (role, added_at, …). (#1872)
+> itself carries attributes (position, added_at, …). (#1872)
 
 ## Media
 

skills/objectstack-platform/evals/README.md

@@ -13,7 +13,7 @@ When implemented, evals will follow this structure:
 ```
 evals/
 ├── bootstrap/
-│   ├── test-definestack-keys.md        # no phantom keys (driver:, workflows:, roles:)
+│   ├── test-definestack-keys.md        # no phantom keys (driver:, workflows:, approvals:)
 │   ├── test-manifest-required-fields.md
 │   └── test-template-selection.md      # blank | todo | compliance | content | contracts | procurement
 ├── drivers-adapters/