Merge remote-tracking branch 'origin/main' into claude/issue-6484-same-dir-bare-path-fromcategory

Author: claude

.changeset/lifecycle-reclaim-rotation-abort-legs.md

@@ -0,0 +1,14 @@
+---
+'@objectstack/objectql': patch
+---
+
+LifecycleService 的空间回收(VACUUM 级)与分片轮转(DROP 过期分片)现在也尊重 #4747 的 teardown abort 位。
+
+PR #5956 / #5755 / PR #6397 依次给 reap 分页循环、Archiver 批循环和冷侧 `keep` prune 补上了 abort 判定,但 `sweep()` 里还剩两条同形的腿:
+
+- **空间回收**:abort 判定在对象循环的**头部**,teardown 落在**最后一个**声明对象的 reap 内时,`batchedReap` 因读到 `aborted === true` 而 break,对象循环随即自然结束(不再经过那个判定),控制流直接落到回收循环 —— 向正在关闭的 datasource 发一次 VACUUM 级操作。
+- **分片轮转**:对象同时声明 `ttl` 与 `storage.strategy: 'rotation'` 时,ttl reap 已经读过位并 break,返回后轮转仅由 strategy 与驱动能力把关,无判定地 DROP 过期物理分片。
+
+两条腿都是「已经拿到答案之后作出的决定」,而不是恰好横跨 teardown 的一次 await。推迟均无代价:回收是纯粹的页面归还,不删任何行;轮转是 O(1) 的窗口回收,下一轮 sweep 用同一个 `shards × unit` 推出同一个窗口、清同一批分片 —— 至多晚一个 sweep 间隔。
+
+仅声明 `rotation`(无 `ttl`)的一路行为不变:该形态下 `reapObject` 在轮转之前没有任何 await,位在结构上必为 false,而非「无人读过」。

.changeset/notification-dual-source-c3.md

@@ -10,36 +10,63 @@ each resolved to **two different declarations** depending on the import
 path — the #4411 dual-source trap. Resolution (three-repo,
 import-statement-level consumer scan: framework, cloud, objectui):
 
+> **Correction (#5781): the `./ui` declarations were NOT consumer-free — the
+> removal stands, the evidence sentence does not.** The scan above matched
+> `import … from` statement text, and objectui reached these two names by two
+> hops it could not see: `packages/types/src/index.ts` re-exported both with
+> `export … from '@objectstack/spec/ui'`, and
+> `packages/core/src/protocols/NotificationProtocol.ts` consumed them via the
+> `@object-ui/types` barrel in the public signatures of
+> `resolveNotificationConfig` / `specNotificationToToast` (objectui#3310, at
+> 17.0.0-rc.1). objectui does not ask for the retirement back: that bridge had
+> zero in-repo callers, `@object-ui/react`'s locally-declared
+> `NotificationSystemConfig` is what runs, and objectui deleted the bridge to
+> follow this retirement. A cross-repo liveness verdict must be read off the
+> resolved SYMBOL GRAPH — covering `export … from` re-exports and
+> barrel-indirect consumption — never off import-statement text; this was the
+> third miss of that class, after #4667 / #4709 (`app.homePageId`).
+
 - **Removed** `NotificationSchema` / `Notification` from
   `@objectstack/spec/ui`. This was a toast/banner "notification instance"
   shape (`type`/`severity`/`message`/`duration`/`actions`/`position` + ARIA
-  props) with **zero importers** in all three repos — objectui's toaster
-  never adopted it. The live contract is `./api`'s `Notification(Schema)`:
+  props) that objectui's toaster never adopted — its only holders were the
+  re-export bridge named in the correction above, which objectui has since
+  deleted. The live contract is `./api`'s `Notification(Schema)`:
   the REST inbox row (`id`/`type`/`title`/`body`/`read`/`data`/`actionUrl`/
   `createdAt`) embedded in `ListNotificationsResponseSchema`, served by
   `/api/v1/notifications`, implemented by `@objectstack/client`, and
   mirrored by `InboxNotification` in `@objectstack/spec/contracts`
   (ADR-0030: the bell reads this shape).
   - FROM `import { NotificationSchema, type Notification } from '@objectstack/spec/ui'` →
-    TO `import { NotificationSchema, type Notification } from '@objectstack/spec/api'`.
-    **Shape change**: the api row is an inbox record, not a presentation
-    config — the ui shape's `severity` / `duration` / `dismissible` /
-    `actions` / `position` / ARIA fields do not exist there. For the
+    TO: **no replacement.** Do NOT re-point this import at
+    `@objectstack/spec/api` — that is the same name under a different
+    contract, and following it does not compile. The api `Notification` is the
+    REST inbox row (`id` / `type` / `title` / `body` / `read` / `data` /
+    `actionUrl` / `createdAt`); the removed ui shape was a toast instance
+    (`message` / `severity` / `position` / `duration` / `dismissible` /
+    `actions` + ARIA). The two share zero fields, and aliasing one to the
+    other would re-create the dual-source trap this change closed. For the
     presentation vocabulary keep using the ui enums, which are unchanged:
-    `NotificationTypeSchema`, `NotificationSeveritySchema`,
-    `NotificationPositionSchema`, `NotificationActionSchema` (+ their
-    types) still live in `@objectstack/spec/ui`.
+    `NotificationTypeSchema`, `NotificationSeveritySchema` and
+    `NotificationPositionSchema` (+ their types) still live in
+    `@objectstack/spec/ui`. Declare the instance shape locally, as objectui
+    does. (`NotificationActionSchema` was listed here too at the time of this
+    change; #5015 retired it in 17.0.0-rc.3, so three enums survive, not
+    four.)
 - **Removed** `NotificationConfigSchema` / `NotificationConfig` from **both**
   `@objectstack/spec/system` and `@objectstack/spec/ui` — the bare name left
-  the spec export surface entirely. Both declarations had zero importers in
-  all three repos and were wired into no parent schema. The system side (a
+  the spec export surface entirely. Neither declaration was wired into any
+  parent schema; the `./system` one had no importers in any of the three
+  repos, and the `./ui` one was held only by the objectui re-export bridge
+  named in the correction above. The system side (a
   channel + template + recipients + schedule + retryPolicy + tracking
   "unified notification management protocol") predates ADR-0030's accepted
   delivery architecture and advertised capability the runtime does not
   deliver (its channel enum's `push`/`slack`/`teams`/`webhook` dead-letter,
   #3197; nothing reads `schedule`/`retryPolicy`/`tracking`). The ui side (a
   toaster global config: `defaultPosition`/`defaultDuration`/`maxVisible`/
-  `stackDirection`/`pauseOnHover`) was never adopted by objectui.
+  `stackDirection`/`pauseOnHover`) was never adopted by objectui's toaster,
+  which reads its own `NotificationSystemConfig` instead.
   - FROM `import { NotificationConfigSchema } from '@objectstack/spec/system'` (or `.../ui`) →
     TO: no direct replacement. The live delivery vocabulary is
     `NotificationService.emit` (`INotificationService`,

.changeset/notification-retirement-evidence-corrected.md

@@ -0,0 +1,74 @@
+---
+'@objectstack/spec': patch
+---
+
+docs(spec): correct two published claims about the #4610 Notification retirement, and forward-note the stale `areas` caveat in the shipped rc.2 changelog (#5781, #5809)
+
+**What changes is what the repo SAYS, not what it does.** No schema byte, no
+export, no conversion and no baseline moves; `@objectstack/spec/ui` still does
+not publish `Notification(Schema)` / `NotificationConfig(Schema)` and
+`@objectstack/spec/system` still does not publish `NotificationConfig(Schema)`.
+Two of the three corrections are to live contract prose, one is a forward-note
+on a shipped changelog section, and one unconsumed changeset (a v17 GA release
+input) is corrected at the source.
+
+**1. "zero importers in all three repos" was false for objectui (#5781).** #4610
+justified removing the two `./ui` notification wrappers with a three-repo,
+import-statement-level consumer scan. objectui#3310 measured the same names at
+17.0.0-rc.1 and found both alive: `packages/types/src/index.ts` re-exported them
+with `export … from '@objectstack/spec/ui'`, and
+`packages/core/src/protocols/NotificationProtocol.ts` consumed them through the
+`@object-ui/types` barrel, in the public signatures of `resolveNotificationConfig`
+/ `specNotificationToToast`. The scan matched `import … from` statement text and
+could see neither hop.
+
+⛔ **The retirement is not reopened.** objectui does not ask for it back: the
+`@object-ui/core` bridge had zero in-repo callers, the implementation that runs
+is `@object-ui/react`'s locally-declared `NotificationSystemConfig`, and objectui
+deleted the bridge to FOLLOW the retirement rather than re-declare vocabulary the
+spec had just dropped. Only the sentence that justified the removal changes.
+
+**2. The FROM → TO would have sent an author to code that does not compile
+(#5781).** #4610 published `from '@objectstack/spec/ui'` → `from
+'@objectstack/spec/api'` for `Notification(Schema)`. `./api`'s `Notification` is
+the REST inbox row (`id` / `type` / `title` / `body` / `read` / `data` /
+`actionUrl` / `createdAt`); the removed `./ui` shape was a toast instance
+(`message` / `severity` / `position` / `duration` / `dismissible` / `actions` +
+ARIA). They share zero fields — same name, a different contract, which is the
+dual-source trap #4610 closed rather than a new home for the old shape. The
+guidance is now **no replacement**: keep `./ui`'s presentation enums and declare
+the instance shape locally, as objectui does. Counted honestly while rewriting
+it: **three** enums survive (`NotificationType` / `NotificationSeverity` /
+`NotificationPosition`), not the four #4610 listed — #5015 retired
+`NotificationAction` at 17.0.0-rc.3.
+
+**3. The methodology, written down beside the tombstone.** A cross-repo liveness
+verdict must be read off the RESOLVED SYMBOL GRAPH, covering at minimum
+`export … from` re-exports and consumption that reaches the spec indirectly
+through a downstream barrel package — never off import-statement text. This was
+the third miss of that class, after #4667 / #4709 (`app.homePageId`).
+
+**4. Shipped changelog sections get forward-notes, never rewrites (#5809).** A
+changelog's value is in being a faithful record of what was shipped and said, so
+the stale sentences stay and a clearly-marked correction is added inside the
+section, pointing at where the corrected statement lives. Three notes land in
+`## 17.0.0-rc.2`: two on the #4610 entry (`0a936ea`, the evidence and the
+FROM → TO), and one on the #4651 app-area entry (`ad047d2`), whose caveat *"per-item
+gating inside an area is enforced by the shell only, because the server does not
+walk `areas`"* has not held since #4722 — `filterAppForUser` runs the same
+`filterNav` over every `areas[].navigation`. The same file's `## 17.0.0-rc.4`
+entry `e4c8b6c` (#5337 / PR #5796) already carries the corrected statement, so
+until now one `CHANGELOG.md` asserted a prescription in one section and refuted
+it in another; a reader arriving by keyword search could be sent off to do an
+unnecessary navigation-tree refactor.
+
+Corrected directly (live contract text and GA inputs, not shipped records):
+`packages/spec/src/ui/notification.zod.ts`'s tombstone,
+`packages/spec/src/migrations/registry.ts`'s protocol-17 `#5015` rationale (which
+projects verbatim into `docs/protocol-upgrade-guide.md` and `spec-changes.json`
+via `gen:upgrade-guide` / `gen:spec-changes` — both regenerated, never hand-edited),
+and the still-unconsumed `.changeset/notification-dual-source-c3.md`, which is a
+legal input to the v17 GA release notes while the repo is in changesets pre mode.
+New pin tests keep both false premises from returning: the registry `reason` is
+pinned in `migrations.test.ts`, the tombstone's four verdicts in
+`notification.test.ts`. ⛔ `content/docs/releases/` is untouched.