chore: release packages

Author: github-actions[bot]

.changeset/option-widgets-empty-hint-single-source.md

@@ -1,5 +1,12 @@
 # @object-ui/console
 
+## 17.2.1
+
+### Patch Changes
+
+- @object-ui/sdui-parser@17.2.1
+- @object-ui/react-runtime@17.2.1
+
 ## 17.2.0
 
 ### Minor Changes

.changeset/page-header-inputs-declare-subtitle.md

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/console",
-  "version": "17.2.0",
+  "version": "17.2.1",
   "description": "ObjectStack Console — opinionated, fork-ready runtime console built on @object-ui/app-shell with the full plugin set wired up. Ships as a Hono UI plugin serving a pre-built SPA.",
   "license": "MIT",
   "type": "module",

.changeset/record-chatter-loading-signal.md

@@ -1,5 +1,107 @@
 # @object-ui/app-shell — Changelog
 
+## 17.2.1
+
+### Patch Changes
+
+- 12bf669: The record discussion panel now says "loading" while it is loading, instead of
+  "No comments yet" (objectui#3209).
+
+  FROM: opening any record page showed the discussion/chatter panel asserting
+  `No comments yet` for the whole first leg of the page, then contradicting
+  itself when the comments appeared. TO: the panel shows the loading row until
+  the feed has actually answered, and only then commits to "this record has no
+  comments".
+
+  objectui#3205 gave `RecordActivityTimeline` the render branch that prefers a
+  loading row over the empty copy, and `RecordChatterPanel` already forwarded
+  `loading` to it in both positions — but on the chatter chain **nothing
+  produced the signal**, so that branch could never fire. `record:activity`
+  computes its own flag and was visibly fixed by #3205; chatter was not. The
+  four wiring points are one chain and are all closed here, because any one of
+  them left open still ships the empty copy to some user:
+
+  - `RecordDetailView` — the host that OWNS the feed fetch — now derives a
+    `feedLoading` flag from its two reads (`sys_comment` + `sys_activity`);
+  - `<DiscussionContextProvider loading={feedLoading}>` publishes it (the field
+    was already declared on `DiscussionContextValue`, and already read by
+    `record:activity`);
+  - the auto-appended `<RecordChatterPanel loading={feedLoading}>` — the panel
+    authored pages get when they place no discussion slot — receives it
+    directly;
+  - the `record:chatter` / `record:discussion` renderer forwards
+    `loading={discussion?.loading}`, so a hand-placed block is on the same
+    chain as the synthesized one.
+
+  The two reads run in parallel, so the flag closes over **both**: it clears on
+  `Promise.allSettled`, and a REJECTED read counts as an answer. A deployment
+  without the audit plugin 404s `sys_activity` and an object with
+  `enable.feeds: false` 403s `sys_comment`; neither may pin the panel in a
+  permanent spinner, which would be a worse bug than the one being fixed. The
+  flag is keyed by `object:recordId` rather than being a plain boolean, so the
+  first render of a record already reads as loading (no one-frame flash of the
+  empty state) and navigating between records cannot show the previous record's
+  settled answer.
+
+  No tolerance was added at the consumer. The timeline still does not guess that
+  "no items yet and just mounted" means loading — that guess is wrong the moment
+  a record genuinely has no comments, and the signal belongs to whoever owns the
+  fetch. Same shape as objectui#3165 / #3205: divergence converges at the
+  producer.
+
+- 30ac2e1: `ToolPreview` stops advertising retired `ToolSchema` flags (objectui#3236).
+
+  The metadata-admin tool preview painted a header strip of flag pills read
+  straight off the raw draft: `Requires confirmation`, `Active` / `Disabled`,
+  `built-in`, and the `category` tag. All four keys have been removed from
+  `@objectstack/spec`'s `ToolSchema` — `requiresConfirmation` in the 16.x line
+  (objectstack#3715, ADR-0033 §2) and `category` / `active` / `builtIn` in
+  17.0.0 (objectstack#3896 audit close-out). The schema is `.strict()` and now
+  rejects each by name with an upgrade prescription, so no newly authored tool
+  can carry them; verified against the `@objectstack/spec@17.0.0-rc.1` this repo
+  depends on.
+
+  New metadata could not reach these pills — but rows stored before the removals
+  still carry the keys, and for those the preview kept rendering. That is the
+  harmful direction, not a cosmetic one:
+
+  - `Requires confirmation` advertised a safety pause that no execution path has
+    ever performed. Nothing read the key — not the LLM tool set (a tool reaches
+    the model as name/description/parameters only), not `ToolRegistry.execute`,
+    not `POST /ai/tools/:name/execute`. A reviewer reading the preview saw a
+    destructive tool marked as gated when it was not. The real gate is
+    `action.ai.requiresConfirmation`, which the HITL approval queue reads.
+  - `Disabled` claimed a tool had been withdrawn while `ToolRegistry.getAll()`
+    kept handing it to the LLM and the execute route kept running it.
+
+  Same shape as objectui#2962: a UI badge advertising a capability the runtime
+  does not have. The pills are gone; the surviving header strip shows label,
+  machine name and the `objectName` pill (`objectName` is still a live spec key),
+  and nothing else in the preview changed — parameters table, example LLM call
+  and output schema are untouched.
+
+  New tests feed the preview a stale draft that still carries all four retired
+  keys and assert none of them renders, so the pills cannot grow back: the names
+  survive in the spec's tombstone guidance, which gives the next reader a
+  plausible-looking reason to "restore" them.
+
+- Updated dependencies [825bbe3]
+- Updated dependencies [d2363e7]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.2.1
+  - @object-ui/fields@17.2.1
+  - @object-ui/i18n@17.2.1
+  - @object-ui/layout@17.2.1
+  - @object-ui/plugin-editor@17.2.1
+  - @object-ui/react@17.2.1
+  - @object-ui/types@17.2.1
+  - @object-ui/core@17.2.1
+  - @object-ui/data-objectstack@17.2.1
+  - @object-ui/auth@17.2.1
+  - @object-ui/permissions@17.2.1
+  - @object-ui/collaboration@17.2.1
+  - @object-ui/providers@17.2.1
+
 ## 17.2.0
 
 ### Minor Changes

.changeset/textarea-mobile-fullscreen-single-source.md

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/app-shell",
-  "version": "17.2.0",
+  "version": "17.2.1",
   "type": "module",
   "license": "MIT",
   "description": "Minimal application shell for ObjectUI - framework-agnostic rendering engine",

.changeset/toolpreview-drop-retired-flag-pills.md

@@ -1,5 +1,11 @@
 # @object-ui/auth
 
+## 17.2.1
+
+### Patch Changes
+
+- @object-ui/types@17.2.1
+
 ## 17.2.0
 
 ### Minor Changes