You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b0d255b
Browse filesBrowse the repository at this point in the historyBrowse files
docs(spec): key the fieldPatches example option by a value crm_account.industry stores
The documented example patched option `tech`, which crm_account.industry
does not store, so a copy was refused at os validate and install. Re-key it
as `technology: { label: 'Tech' }` in the schema description, TSDoc, the
option-list refusal text, the object-extensions guide and the two unreleased
changesets that carried it.
Claude-Session: https://claude.ai/code/session_01ADHkmQfYHca8dfoXTJfeKp
Co-authored-by: Claude <noreply@anthropic.com>
docs(spec): the documented `fieldPatches` example keys its option by a value `crm_account.industry` really stores
6
+
7
+
Clause-②: no
8
+
Metadata-protocol: none
9
+
10
+
The `fieldPatches` description, its TSDoc example and the refusal text for an option list under `options` showed `options: { tech: { label: 'Technology' } }`. `crm_account.industry` stores `technology`, not `tech`, so a copy of that example was refused at `os validate` and at install as naming an option the field does not have. The example now reads `options: { technology: { label: 'Tech' } }`, the same spelling the published skill uses. Prose only: no schema accepts or refuses anything differently.
0 commit comments