wip: retire renderNotification only; renderTemplate and interpolate stay pending a disposition ruling

Claude-Session: https://claude.ai/code/session_01CP5uvqW3aX2Tfwy6YAsNu5
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/25190-retire-body-taking-render-exports.md

@@ -1,21 +1,18 @@
 ---
-'@objectstack/plugin-email': patch
 '@objectstack/service-messaging': patch
 ---
 
-fix(plugin-email, service-messaging)!: retire the render exports that take a template body with no save moment (`renderTemplate`, `renderNotification`, `interpolate`)
+fix(service-messaging)!: retire `renderNotification`, the render export that takes a notification template body with no save moment
 
-The hole-placement rule is judged where a template is saved or registered: the `sys_notification_template` save hooks, and the authoring rule for email templates. Three exports took a template body inline and rendered it at once, with no save moment, so the rule could not see them. They leave the two packages' published entries. Nothing in this repository imported them from either entry. The renderers stay inside the packages: the mail service and the email and sms channels still render every stored template through them, unchanged.
+The hole-placement rule for notification templates is judged where a template is saved: the `sys_notification_template` save hooks. `renderNotification` took a template body inline and rendered it at once, with no save moment, so the rule could not see it. It leaves the published entry of `@objectstack/service-messaging`. Nothing in this repository imported it from that entry. The renderer stays inside the package: the email and sms channels still render every stored template through it, unchanged.
 
 Clause-②: no (narrowing)
 Metadata-protocol: none
 
-<!-- adr-0087: not-required (runtime-export-retired @objectstack/plugin-email#renderTemplate, @objectstack/service-messaging#renderNotification, @objectstack/service-messaging#interpolate) Three runtime functions leave two published package entries; no key of any metadata schema, no object definition and no stored shape is added, removed, renamed or re-shaped, so there is nothing for `objectstack migrate meta` to rewrite and no tombstone. A TypeScript consumer meets the break at its own import, and the lines below name the door to use instead. -->
+<!-- adr-0087: not-required (runtime-export-retired @objectstack/service-messaging#renderNotification) One runtime function leaves a published package entry; no key of any metadata schema, no object definition and no stored shape is added, removed, renamed or re-shaped, so there is nothing for `objectstack migrate meta` to rewrite and no tombstone. A TypeScript consumer meets the break at its own import, and the line below names the door to use instead. -->
 
-**BREAKING** (three runtime exports are removed). It ships as `patch` because the metadata protocol does not move. There is no staged window.
+**BREAKING** (a runtime export is removed). It ships as `patch` because the metadata protocol does not move. There is no staged window.
 
-- FROM `renderTemplate` imported from `@objectstack/plugin-email` TO a template saved or registered as an `email_template` and rendered by name through the mail service: `renderTemplate({ template, data, locale })` on the `email` service (render only) or `sendTemplate` (render and send).
-- FROM `renderNotification` imported from `@objectstack/service-messaging` TO a `sys_notification_template` row for the topic, channel and locale, which the delivering channel renders when the notification is emitted.
-- FROM `interpolate` imported from `@objectstack/service-messaging` TO the subject or plain-text body of a `sys_notification_template` row, rendered the same way by the delivering channel.
+- FROM `renderNotification` TO a `sys_notification_template` row for the topic, channel and locale, which the delivering channel renders when the notification is emitted.
 
-Unchanged: `requireVars` and `htmlToText` in `@objectstack/plugin-email`, and the mail service's `setTemplateLoader`; `NotificationTemplateStore`, `TEMPLATE_OBJECT`, `DEFAULT_LOCALE` and the template types in `@objectstack/service-messaging`; and how every stored template renders.
+Unchanged: `interpolate` (the plain-text face, which the placement rule judges at no door), `NotificationTemplateStore`, `TEMPLATE_OBJECT`, `DEFAULT_LOCALE` and the template types; and how every stored template renders.

packages/plugins/plugin-email/src/index.ts

@@ -85,12 +85,7 @@ export {
   type AttachmentReclaimOutcome,
   type ReclaimAttachmentContentOptions,
 } from './attachment-reclaim.js';
-// [#25190] `renderTemplate` (the HTML-face renderer) is not on this entry: it
-// took a template body inline and rendered it with no save moment, so the
-// hole-placement rule judged where a template is saved or registered could not
-// see it (ruling 6335348115 on #25082, F2 B3). A template is rendered from the
-// mail service by NAME: `IEmailService.renderTemplate` / `sendTemplate`.
-export { requireVars, htmlToText } from './template-engine.js';
+export { renderTemplate, requireVars, htmlToText } from './template-engine.js';
 export {
   ResendTransport,
   PostmarkTransport,

packages/plugins/plugin-email/src/render-export-retired.pin.test.ts

@@ -88,14 +88,16 @@ export type {
 
 // Templates + renderer (ADR-0030 P3)
 //
-// [#25190] The renderer itself (`renderNotification`, and `interpolate`, its
-// plain-text face) is not on this entry: both took a template body inline and
-// rendered it with no save moment, so the hole-placement rule the template
-// object's save hooks run could not see them (ruling 6335348115 on #25082,
-// F2 B3). A notification template is a `sys_notification_template` row, judged
-// when it is saved and rendered by the channels that deliver it.
+// [#25190] `renderNotification` is not on this entry: it took a template body
+// inline and rendered its html face with no save moment, so the hole-placement
+// rule the template object's save hooks run could not see it (ruling
+// 6335348115 on #25082, F2 B3). A notification template is a
+// `sys_notification_template` row, judged when it is saved and rendered by the
+// channels that deliver it. `interpolate` stays: it renders a plain-text face,
+// which that rule judges at no door.
 export {
     NotificationTemplateStore,
+    interpolate,
     TEMPLATE_OBJECT,
     DEFAULT_LOCALE,
 } from './template-renderer.js';

packages/services/service-messaging/src/index.ts

@@ -1,30 +1,31 @@
 // Copyright (c) 2025 ObjectStack. Licensed under the Apache-2.0 license.
 
 /**
- * #25190 — `renderNotification` and `interpolate`, the renderer that took a
- * template body inline, are retired from this package's published entry
- * (ruling 6335348115 on #25082, F2 B3; ADR-0087 `runtime-export-retired`). The
- * hole-placement rule is judged by the `sys_notification_template` save hooks,
- * and a body handed straight to either function was never saved, so they were
- * the one door the rule could not see.
+ * #25190 — `renderNotification`, the renderer that took a template body inline,
+ * is retired from this package's published entry (ruling 6335348115 on #25082,
+ * F2 B3; ADR-0087 `runtime-export-retired`). The hole-placement rule is judged
+ * by the `sys_notification_template` save hooks, and a body handed straight to
+ * it was never saved, so it was the one door the rule could not see.
+ * `interpolate` stays on the entry: it renders a plain-text face, which the
+ * rule judges at no door.
  *
- * Pinned both ways: the entry no longer names them (the template store and the
+ * Pinned both ways: the entry no longer names it (the template store and the
  * channels stay), and a stored template row still renders through a channel
  * built from the entry — the html body with every hole encoded, the subject
- * (`interpolate`'s plain-text face) verbatim.
+ * (the plain-text face) verbatim.
  */
 
 import { describe, it, expect } from 'vitest';
 import * as entry from './index.js';
 
 describe('service-messaging entry: the body-taking renderer is retired (#25190)', () => {
-  it('the published entry does not export renderNotification or interpolate', () => {
+  it('the published entry does not export renderNotification', () => {
     expect('renderNotification' in entry).toBe(false);
-    expect('interpolate' in entry).toBe(false);
   });
 
-  it('THE CONTROL: the entry still exports the template store and the channels that render', () => {
+  it('THE CONTROL: the entry still exports the template store, the plain-text face and the channels that render', () => {
     expect(typeof entry.NotificationTemplateStore).toBe('function');
+    expect(typeof entry.interpolate).toBe('function');
     expect(entry.TEMPLATE_OBJECT).toBe('sys_notification_template');
     expect(typeof entry.createEmailChannel).toBe('function');
     expect(typeof entry.createSmsChannel).toBe('function');