docs(releases): v17 upgrade checklist — the raw watcher values are gone from MetadataWatchEvent.type (#4536) (#4549)

* docs(releases): v17 upgrade checklist — the raw watcher values are gone from MetadataWatchEvent.type (#4536)

The checklist's #4411 entry told upgraders the surviving system copy "also
carries the raw watcher values add/change/unlink". True when written; false
since #4536 removed them (zero producers — both emit sites normalize). A
reader following the sentence would add narrowing for values the schema now
rejects.

Dedicated docs-only PR per the releases-freeze rule (CLAUDE.md): a factual
error on a releases page is fixed in its own PR, never as a rider on code
changes.

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

* chore: empty-frontmatter changeset — docs-only PR releases nothing

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

---------

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

Author: os-zhuang

.changeset/v17-watch-event-raw-values-note.md

@@ -0,0 +1,7 @@
+---
+---
+
+Releases nothing — docs-only. Corrects the v17 upgrade checklist sentence that
+still told upgraders `MetadataWatchEvent.type` carries the raw watcher values
+(`add`/`change`/`unlink`); they were removed in #4536 with zero producers. No
+package ships from this change.

content/docs/releases/v17.mdx

@@ -2120,9 +2120,11 @@ covers are folded into the list below rather than left to the changelog.)
   from `@objectstack/spec/kernel`, change the path to `@objectstack/spec/system`
   — same names, and that copy is the one the runtime has always emitted. It is
   the *looser* of the two, so a reader may need new narrowing: notably
-  `MetadataWatchEvent.type` also carries the raw watcher values
-  `add`/`change`/`unlink`, and `metadataType`/`name`/`timestamp` are optional
-  there. Nothing to migrate at runtime — the values were always these.
+  `metadataType`/`name`/`timestamp` are optional there. (`MetadataWatchEvent.type`
+  briefly also declared the raw watcher values `add`/`change`/`unlink`; they had
+  zero producers — both emit sites normalize — and were removed in #4536, so the
+  enum now carries exactly `added`/`changed`/`deleted`.) Nothing to migrate at
+  runtime — the values the runtime emits were always these.
 - **Multi-org:** the `group` posture requires the enterprise runtime — deployments
   relying on it self-activating must install `@objectstack/organizations` or move
   to `isolated`.