@@ -14,4 +14,4 @@ Clause-②: yes (widening)
 - **Reading reactions for a feed.** Read the reactions of the comments on screen in one request, `comment_id` `$in` those ids, and group the rows by comment and emoji. Nothing is stored or computed on the comment row.
 - **Granting it.** The object's create, read and delete bits come from a permission set, as `sys_comment`'s do. The `everyone`-bound baseline (`member_default`) grants nothing on it.
 - **`@objectstack/spec`: the platform object registry lists it.** `PLATFORM_OBJECTS_BY_PACKAGE['plugin-audit']` now includes `sys_comment_reaction`, and so do `PLATFORM_PROVIDED_OBJECT_NAMES` and `isPlatformProvidedObjectName`. A stack that references the object is no longer reported as naming an unknown platform object. This is the only change in the package.
-- **`sys_comment.reactions` is unchanged in this release.** The column is still declared and still written by clients that write it. It is retired separately, and reactions stored in it are not converted into records.
+- **`sys_comment.reactions` is retired by a separate change on this line**, which carries its own entry. Reactions stored in that column are not converted into records.
@@ -0,0 +1,30 @@
+---
+'@objectstack/plugin-audit': minor
+'@objectstack/spec': minor
+---
+
+feat(plugin-audit)!: `sys_comment.reactions` retires; an emoji reaction lives only in `sys_comment_reaction`, and reactions stored in the old column are not migrated
+
+Clause-②: no (narrowing)
+
+<!-- adr-0087: registered sys-comment-reactions-column-retired -->
+
+**BREAKING**, shipped as `minor` under the repo's convention for breaking changes on this line.
+
+**Existing emoji reactions stored in `sys_comment.reactions` are gone after the upgrade.** They are not converted into `sys_comment_reaction` records, and no screen or API returns them again. Reactions now live in `sys_comment_reaction`, one row per comment, emoji and user, the reacting user's own record.
+
+- **`sys_comment`** (`@objectstack/plugin-audit`) no longer declares `reactions`. Nothing takes its place on the comment row: no stored aggregate, and no block computed on read. Its label leaves the four generated translation bundles.
+- **The data door refuses the field.** A create or an update of a comment that still carries `reactions`, and a list filter on it, answer `400 INVALID_FIELD` naming the field, and nothing is written. The rest of the payload is not applied either. A read of a comment no longer returns `reactions`.
+- **`@objectstack/spec`**: the protocol-18 step of the ADR-0087 migration chain gains the semantic entry `sys-comment-reactions-column-retired`, so `os migrate meta` and the upgrade guide carry the prescription below.
+
+**What moves for consumers.**
+
+| You wrote | Write instead |
+|:---|:---|
+| `sys_comment.reactions` read as a map of emoji to user ids | one read of `sys_comment_reaction` for the comments on screen (`comment_id` `$in` their ids), grouped by comment and emoji |
+| an update of `sys_comment` that rewrites `reactions` to add or remove a user | create the user's own `sys_comment_reaction` row (`comment_id`, `emoji`) to react; delete that row to un-react |
+| `reactions` in a seed row, filter or list-view column on `sys_comment` | delete it |
+
+An application that shows reactions grants `sys_comment_reaction` read, create and delete beside its `sys_comment` grant; without it a member cannot react. The console's record chatter already reads and writes `sys_comment_reaction` rows wherever the deployment declares that object, as this framework does.
+
+**Existing databases — nothing moves automatically.** Schema sync is additive: the physical `reactions` column stays with the values it holds, the boot drift report names it orphaned (`sys_comment.reactions: column exists in the database but not in metadata`), and the boot is otherwise clean. The data door neither returns nor accepts the column. To drop it, run `os migrate apply --allow-destructive` with the audit plugin composed (an auth secret resolves); the stored reactions go with it.
@@ -55,7 +55,11 @@ import { ObjectSchema, Field } from '@objectstack/spec/data';
  * `sys_comment_reaction` rows of the comments on screen (`comment_id` `$in`
  * their ids) and groups them by emoji. Reactions stored in the column are not
  * converted into records; the D3 record is the semantic entry
- * `sys-comment-reactions-column-retired`.
+ * `sys-comment-reactions-column-retired`. An existing database keeps the
+ * physical column and its values (schema sync is additive): the boot drift
+ * report names it orphaned, the data door neither returns nor accepts it
+ * (`400 INVALID_FIELD` on a write that names it), and
+ * `os migrate apply --allow-destructive` drops it.
  *
  * @namespace sys
  */