@@ -2,14 +2,14 @@
 '@objectstack/objectql': minor
 '@objectstack/service-messaging': minor
 '@objectstack/service-automation': minor
-'@objectstack/plugin-approvals': patch
+'@objectstack/plugin-approvals': minor
 ---
 
 fix(objectql,service-messaging,service-automation,plugin-approvals)!: a notification carries the organization of what it is about, and one no organization owns is refused instead of stored with `organization_id` NULL
 
 Clause-②: no (narrowing) — notification rows gain the organization they should already carry; what narrows is an emit that names no organization on an install where none is derivable, which the engine now refuses where it used to store the event row with `organization_id` NULL.
 
-<!-- adr-0087: not-required (no-migration-prescription) A runtime narrowing of which notification writes the engine accepts, not a metadata change. No spec key, authorable spelling, export, option, config field or stored shape is added, removed, renamed or re-shaped, and no stored row is rewritten: rows already stored with organization_id NULL keep it until the v18 ownership ceremony attributes them, which already lists sys_notification with the attribution fate. The only type change is an additive optional `organizationId` on the approvals service's internal messaging surface, which is not exported by name. The other categories are closed on facts: the four packages publish (not unpublished); no ADR-0087 id covers notification ownership and this diff adds none (not registered / already-registered); nothing is removed or narrowed on an interface or type (not runtime-interface-only / type-surface-only); and no runtime export is retired (not runtime-export-retired). -->
+<!-- adr-0087: not-required (no-migration-prescription) A runtime narrowing of which notification writes the engine accepts, not a metadata change. No spec key, authorable spelling, export, option, config field or stored shape is added, removed, renamed or re-shaped, and no stored row is rewritten: rows already stored with organization_id NULL keep it until the v18 ownership ceremony attributes them, which already lists sys_notification with the attribution fate. The only type change is an additive optional `organizationId` on the input of `ApprovalMessagingSurface.emit`, the approvals service's messaging surface: the interface is not listed in the package index, but it is published surface, reachable through the exported `ApprovalServiceOptions.messaging` and the public `ApprovalService.attachMessaging`, so it is an additive widening that no existing implementation has to change for. The other categories are closed on facts: the four packages publish (not unpublished); no ADR-0087 id covers notification ownership and this diff adds none (not registered / already-registered); nothing is removed or narrowed on an interface or type (not runtime-interface-only / type-surface-only); and no runtime export is retired (not runtime-export-retired). -->
 
 **BREAKING** (an accept-set narrowing), shipped as `minor` under the launch-window convention for breaking changes.
 
 
@@ -60,19 +60,6 @@ function silentLogger(): any {
     return l;
 }
 
-/** A logger that records every warning line, for the fail-loud pin. */
-function recordingLogger(): { logger: any; warnings: string[] } {
-    const warnings: string[] = [];
-    const l: any = {
-        info: () => {},
-        warn: (...args: unknown[]) => { warnings.push(args.map(String).join(' ')); },
-        error: () => {},
-        debug: () => {},
-    };
-    l.child = () => l;
-    return { logger: l, warnings };
-}
-
 /** Every row this stack wrote, in insertion order, with the object it landed in. */
 interface WrittenRow { object: string; row: Record<string, unknown> }