fix(lint): the react-prop-deprecated warning states its reason in words, not a tracker number

.changeset/20597-react-prop-deprecated-message-words.md

@@ -0,0 +1,14 @@
+---
+'@objectstack/lint': patch
+---
+
+The `react-prop-deprecated` warning states its reason in words instead of citing a tracker number
+
+The finding `validateReactPageProps` reports for a react-page prop written in a
+deprecated react-tier spelling used to end by pointing the author at an issue
+number that no longer resolves. It now says what that decision was, in the
+sentence being read: the react tier converges on the metadata-tier vocabulary,
+so the deprecated spelling keeps working through the deprecation window and is
+removed after it. The block tag, the prop and the canonical metadata-tier
+spelling it names are unchanged, and so are the rule id, the `warning`
+severity, the hint and every other finding.

packages/lint/src/validate-react-page-props.ts

@@ -1195,7 +1195,7 @@ export function validateReactPageProps(stack: AnyRec): ReactPropFinding[] {
                 severity: 'warning',
                 rule: REACT_PROP_DEPRECATED,
                 where, path,
-                message: `<${tag}> prop "${u}" is the deprecated spelling of the metadata-tier "${dep.replacedBy}" and is removed after the deprecation window (#11284).`,
+                message: `<${tag}> prop "${u}" is the deprecated spelling of the metadata-tier "${dep.replacedBy}": the react tier converges on the metadata-tier vocabulary, so this spelling keeps working through the deprecation window and is removed after it.`,
                 hint: dep.note,
               });
             }

scripts/doc-authoring-prose-id.baseline.json

@@ -287,7 +287,6 @@
   "#7696": 1
  },
  "packages/lint/src/validate-react-page-props.ts": {
-  "#11284": 1,
   "#5583": 1
  },
  "packages/lint/src/validate-readonly-flow-writes.ts": {