@aglyn/aglyn 1.0.0-beta.252 → 1.0.0-beta.254

package/src/lib/app-utils/email-block-starters.d.ts

@@ -0,0 +1,39 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+/** The email plugin's bundle id: the `pluginId` of every element in its bands. */
+export declare const EMAIL_BLOCK_STARTER_PLUGIN_ID = "email";
+/** One element of a nested starter tree, as an element preset's `data` holds it. */
+export interface EmailBlockStarterNode {
+    $id: null;
+    componentId: string;
+    pluginId: string;
+    props: Record<string, unknown>;
+    nodes?: EmailBlockStarterNode[];
+}
+/**
+ * The Footer's small print, a muted gray that still reads at 5:1 on white.
+ * A literal on purpose: it is written into the sent mail's own HTML, where no
+ * theme token resolves.
+ */
+export declare const EMAIL_FOOTER_TEXT_COLOR = "#6b6b6b";
+export declare const EMAIL_BLOCK_STARTER_TREES: Readonly<Record<'header' | 'footer', EmailBlockStarterNode>>;
+/**
+ * {@link EMAIL_BLOCK_STARTER_TREES} as JSON text: the form the native apps
+ * read them in (`Contracts.emailBlockStarterTreesJson`), parsed when a block
+ * is started.
+ */
+export declare const EMAIL_BLOCK_STARTER_TREES_JSON: string;

package/src/lib/app-utils/email-block-starters.js

@@ -0,0 +1,122 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */ /*
+ * The two email bands a Header or Footer email block starts from (AGL-3287),
+ * as plain data: the email plugin registers them as element presets (so an
+ * author can drop one into an email), the Components page starts a reusable
+ * block from the same trees, and the native apps start theirs from the values
+ * generated from here. One tree each, wherever it is started from.
+ *
+ * The words are placeholders to replace. No merge token names the company in
+ * both kinds of email — a campaign supplies `{{org.name}}`, and no token is
+ * supplied by every one of a site's own emails — while a token an email does
+ * not supply is blanked before sending, which would leave the header with no
+ * name at all.
+ *
+ * The footer carries no unsubscribe link: a campaign send appends its own,
+ * and a second one would do the same thing twice.
+ */ /** The email plugin's bundle id: the `pluginId` of every element in its bands. */ export const EMAIL_BLOCK_STARTER_PLUGIN_ID = 'email';
+/**
+ * The Footer's small print, a muted gray that still reads at 5:1 on white.
+ * A literal on purpose: it is written into the sent mail's own HTML, where no
+ * theme token resolves.
+ */ export const EMAIL_FOOTER_TEXT_COLOR = '#6b6b6b';
+const FOOTER_TEXT_COLOR = EMAIL_FOOTER_TEXT_COLOR;
+export const EMAIL_BLOCK_STARTER_TREES = {
+    header: {
+        $id: null,
+        componentId: 'emailSection',
+        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+        // Marks the band as the email's header, so the sender's own header is
+        // not drawn above it (AGL-3372).
+        props: {
+            align: 'center',
+            padding: 24,
+            emailRole: 'header'
+        },
+        nodes: [
+            {
+                $id: null,
+                componentId: 'emailImage',
+                pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+                props: {
+                    alt: 'Your company logo',
+                    width: 160,
+                    align: 'center'
+                }
+            },
+            {
+                $id: null,
+                componentId: 'emailText',
+                pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+                props: {
+                    children: 'Your company',
+                    variant: 'subheading',
+                    align: 'center'
+                }
+            }
+        ]
+    },
+    footer: {
+        $id: null,
+        componentId: 'emailSection',
+        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+        // Marks the band as the email's footer, so the sender's own footer is
+        // not drawn under it (AGL-3372).
+        props: {
+            align: 'center',
+            padding: 24,
+            emailRole: 'footer'
+        },
+        nodes: [
+            {
+                $id: null,
+                componentId: 'emailDivider',
+                pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+                props: {}
+            },
+            {
+                $id: null,
+                componentId: 'emailText',
+                pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+                props: {
+                    children: 'Your company · 123 Main St, City',
+                    variant: 'caption',
+                    align: 'center',
+                    color: FOOTER_TEXT_COLOR
+                }
+            },
+            {
+                $id: null,
+                componentId: 'emailText',
+                pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,
+                props: {
+                    children: "You're receiving this because you're a customer of Your company.",
+                    variant: 'caption',
+                    align: 'center',
+                    color: FOOTER_TEXT_COLOR
+                }
+            }
+        ]
+    }
+};
+/**
+ * {@link EMAIL_BLOCK_STARTER_TREES} as JSON text: the form the native apps
+ * read them in (`Contracts.emailBlockStarterTreesJson`), parsed when a block
+ * is started.
+ */ export const EMAIL_BLOCK_STARTER_TREES_JSON = JSON.stringify(EMAIL_BLOCK_STARTER_TREES);
+
+//# sourceMappingURL=email-block-starters.js.map

package/src/lib/app-utils/email-block-starters.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../libs/aglyn/src/lib/app-utils/email-block-starters.ts"],"sourcesContent":["/**\n * @license\n * Copyright 2026 Aglyn LLC\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n *   http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n\n/*\n * The two email bands a Header or Footer email block starts from (AGL-3287),\n * as plain data: the email plugin registers them as element presets (so an\n * author can drop one into an email), the Components page starts a reusable\n * block from the same trees, and the native apps start theirs from the values\n * generated from here. One tree each, wherever it is started from.\n *\n * The words are placeholders to replace. No merge token names the company in\n * both kinds of email — a campaign supplies `{{org.name}}`, and no token is\n * supplied by every one of a site's own emails — while a token an email does\n * not supply is blanked before sending, which would leave the header with no\n * name at all.\n *\n * The footer carries no unsubscribe link: a campaign send appends its own,\n * and a second one would do the same thing twice.\n */\n\n/** The email plugin's bundle id: the `pluginId` of every element in its bands. */\nexport const EMAIL_BLOCK_STARTER_PLUGIN_ID = 'email'\n\n/** One element of a nested starter tree, as an element preset's `data` holds it. */\nexport interface EmailBlockStarterNode {\n  $id: null\n  componentId: string\n  pluginId: string\n  props: Record<string, unknown>\n  nodes?: EmailBlockStarterNode[]\n}\n\n/**\n * The Footer's small print, a muted gray that still reads at 5:1 on white.\n * A literal on purpose: it is written into the sent mail's own HTML, where no\n * theme token resolves.\n */\nexport const EMAIL_FOOTER_TEXT_COLOR = '#6b6b6b'\nconst FOOTER_TEXT_COLOR = EMAIL_FOOTER_TEXT_COLOR\n\nexport const EMAIL_BLOCK_STARTER_TREES: Readonly<\n  Record<'header' | 'footer', EmailBlockStarterNode>\n> = {\n  header: {\n    $id: null,\n    componentId: 'emailSection',\n    pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n    // Marks the band as the email's header, so the sender's own header is\n    // not drawn above it (AGL-3372).\n    props: { align: 'center', padding: 24, emailRole: 'header' },\n    nodes: [\n      {\n        $id: null,\n        componentId: 'emailImage',\n        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n        props: { alt: 'Your company logo', width: 160, align: 'center' },\n      },\n      {\n        $id: null,\n        componentId: 'emailText',\n        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n        props: {\n          children: 'Your company',\n          variant: 'subheading',\n          align: 'center',\n        },\n      },\n    ],\n  },\n  footer: {\n    $id: null,\n    componentId: 'emailSection',\n    pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n    // Marks the band as the email's footer, so the sender's own footer is\n    // not drawn under it (AGL-3372).\n    props: { align: 'center', padding: 24, emailRole: 'footer' },\n    nodes: [\n      {\n        $id: null,\n        componentId: 'emailDivider',\n        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n        props: {},\n      },\n      {\n        $id: null,\n        componentId: 'emailText',\n        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n        props: {\n          children: 'Your company · 123 Main St, City',\n          variant: 'caption',\n          align: 'center',\n          color: FOOTER_TEXT_COLOR,\n        },\n      },\n      {\n        $id: null,\n        componentId: 'emailText',\n        pluginId: EMAIL_BLOCK_STARTER_PLUGIN_ID,\n        props: {\n          children:\n            \"You're receiving this because you're a customer of Your company.\",\n          variant: 'caption',\n          align: 'center',\n          color: FOOTER_TEXT_COLOR,\n        },\n      },\n    ],\n  },\n}\n\n/**\n * {@link EMAIL_BLOCK_STARTER_TREES} as JSON text: the form the native apps\n * read them in (`Contracts.emailBlockStarterTreesJson`), parsed when a block\n * is started.\n */\nexport const EMAIL_BLOCK_STARTER_TREES_JSON: string = JSON.stringify(\n  EMAIL_BLOCK_STARTER_TREES,\n)\n"],"names":["EMAIL_BLOCK_STARTER_PLUGIN_ID","EMAIL_FOOTER_TEXT_COLOR","FOOTER_TEXT_COLOR","EMAIL_BLOCK_STARTER_TREES","header","$id","componentId","pluginId","props","align","padding","emailRole","nodes","alt","width","children","variant","footer","color","EMAIL_BLOCK_STARTER_TREES_JSON","JSON","stringify"],"mappings":"AAAA;;;;;;;;;;;;;;;CAeC,GAED;;;;;;;;;;;;;;;CAeC,GAED,gFAAgF,GAChF,OAAO,MAAMA,gCAAgC,QAAO;AAWpD;;;;CAIC,GACD,OAAO,MAAMC,0BAA0B,UAAS;AAChD,MAAMC,oBAAoBD;AAE1B,OAAO,MAAME,4BAET;IACFC,QAAQ;QACNC,KAAK;QACLC,aAAa;QACbC,UAAUP;QACV,sEAAsE;QACtE,iCAAiC;QACjCQ,OAAO;YAAEC,OAAO;YAAUC,SAAS;YAAIC,WAAW;QAAS;QAC3DC,OAAO;YACL;gBACEP,KAAK;gBACLC,aAAa;gBACbC,UAAUP;gBACVQ,OAAO;oBAAEK,KAAK;oBAAqBC,OAAO;oBAAKL,OAAO;gBAAS;YACjE;YACA;gBACEJ,KAAK;gBACLC,aAAa;gBACbC,UAAUP;gBACVQ,OAAO;oBACLO,UAAU;oBACVC,SAAS;oBACTP,OAAO;gBACT;YACF;SACD;IACH;IACAQ,QAAQ;QACNZ,KAAK;QACLC,aAAa;QACbC,UAAUP;QACV,sEAAsE;QACtE,iCAAiC;QACjCQ,OAAO;YAAEC,OAAO;YAAUC,SAAS;YAAIC,WAAW;QAAS;QAC3DC,OAAO;YACL;gBACEP,KAAK;gBACLC,aAAa;gBACbC,UAAUP;gBACVQ,OAAO,CAAC;YACV;YACA;gBACEH,KAAK;gBACLC,aAAa;gBACbC,UAAUP;gBACVQ,OAAO;oBACLO,UAAU;oBACVC,SAAS;oBACTP,OAAO;oBACPS,OAAOhB;gBACT;YACF;YACA;gBACEG,KAAK;gBACLC,aAAa;gBACbC,UAAUP;gBACVQ,OAAO;oBACLO,UACE;oBACFC,SAAS;oBACTP,OAAO;oBACPS,OAAOhB;gBACT;YACF;SACD;IACH;AACF,EAAC;AAED;;;;CAIC,GACD,OAAO,MAAMiB,iCAAyCC,KAAKC,SAAS,CAClElB,2BACD"}

package/src/lib/app-utils/screen-route.d.ts

@@ -15,136 +15,7 @@
  * limitations under the License.
  */
 import { type ScreenUid } from '../foundation';
-/**
- * Route path of a host's root screen. The tenant matcher joins the catch-all
- * segments and collapses an empty one to this value (`load-page-data.ts`:
- * `slugSegments.length ? slugSegments.join('/') : SCREEN_ROOT_PATH`), so the
- * root is `'/'` and every other path is slash-joined segments WITHOUT a
- * leading slash (`about`, later `company/about`).
- */
-export declare const SCREEN_ROOT_PATH = "/";
-/**
- * Normalizes user slug input into the routing-map path format described on
- * {@link SCREEN_ROOT_PATH}. `'/'` normalizes to the root path; anything else
- * becomes a single lowercase url-safe segment.
- *
- * Returns `undefined` for EMPTY input and for anything that sanitizes away
- * (`'###'`) — the two cases are deliberately the same answer, and the caller
- * decides what it means. In the Screens page's slug field an empty string
- * means "no address typed"; in a starter template it meant "home". Two
- * meanings for one value is what made AGL-1575 possible, so this function
- * refuses to pick one: a caller that wants the root must say `'/'`.
- *
- * This docstring used to claim empty input normalized to the root, which the
- * code has never done (see the spec, which asserts the `undefined`). A fix
- * written against the docstring instead of the behaviour would have shipped
- * broken; if you are here to make the code match the comment, do not.
- */
-export declare function normalizeScreenSlug(input: string | null | undefined): string | undefined;
-/**
- * Route segments the published site CANNOT serve, whatever the routing map
- * says (AGL-2076).
- *
- * Every entry was measured against production on 2026-08-19 with a fresh
- * `x-vercel-cache: MISS`, because a stale negative always passes. Two
- * mechanisms, both of which resolve ahead of `[host]/[scheme]/[[...slug]]`:
- *
- *  - `404`, `500` — Next emits `pages/404.html` and `pages/500.html` even for
- *    an app-router-only build, and the deployed filesystem answers them as
- *    static files (`content-disposition: inline; filename="404"`,
- *    `accept-ranges`, an `etag`, and no `x-nextjs-prerender`). The tenant
- *    middleware's own CSP headers are on those responses, so the middleware
- *    ran and its rewrite still lost. There is no rewrite this app can write
- *    that beats them, which is why the honest fix is to refuse the slug at
- *    authoring time rather than to keep promising an address that is dead.
- *  - `search`, `api`, `_next`, `_static` — routes and exclusions the tenant
- *    app owns. `/search` matches `app/[host]/[scheme]/search`; the other three are the
- *    middleware matcher's exclusions, so no host rewrite happens at all and
- *    the path is parsed as `[host]` with an empty slug.
- *  - `aglyn-preview` — the same mechanism as `search`, one route over
- *    (AGL-3205). The live-site preview of an unpublished collection entry is
- *    a rewrite to `app/[host]/[scheme]/aglyn-preview/[...slug]`, because it
- *    must be a DIFFERENT Next route from the ISR-cached catch-all; a static
- *    folder wins over the optional catch-all beside it, so `/aglyn-preview/x`
- *    would reach the preview page and 404 rather than render a screen. The
- *    bare `/aglyn-preview` would in fact still serve — the preview route's
- *    catch-all is required, not optional — and it is reserved anyway for the
- *    reason given below about child paths: a child's path is composed from
- *    its parent's slug, and this rule refuses that slug.
- *  - `_aglyn` — the platform's own pages on every site, the leaving notice
- *    at `/_aglyn/leaving` first (AGL-3452). The middleware rewrites that path
- *    to an api route before the catch-all could see it.
- *
- * NOT reserved, and deliberately so, because measuring found them fine:
- * `401`, `403`, `503` (`/401` returns 200 through the catch-all — two of the
- * four designed error screens have always been viewable at their slugs, which
- * is what made the `404` case look like a Next.js defect), and `index`.
- *
- * `fonts` and `examples` USED to be dead for the third reason and are not
- * here: they were exclusions inherited from the Vercel platforms starter kit
- * for directories `apps/tenant/public` has never contained. They are given
- * back rather than reserved — see the matcher in `apps/tenant/middleware.ts`.
- */
-export declare const RESERVED_SCREEN_ROUTE_SEGMENTS: readonly string[];
-/**
- * The reserved segment a routing-map path would collide with, or `undefined`
- * when the path is servable. The segment rather than a boolean, so a refusal
- * can name what it is refusing over.
- *
- * Reads the FIRST segment only. For `api`/`_next`/`_static` that is exactly
- * right — the middleware excludes the whole subtree, so `api/docs` is as dead
- * as `api`. For `404`/`500`/`search` it over-refuses in principle (`/404/why`
- * would serve), and that is deliberate: a child path is composed from its
- * PARENT's slug, the parent would have to hold `404`, and this same rule
- * refuses that slug wherever one is typed. A second list to express a case
- * that cannot arise would be a second list to keep correct.
- *
- * Takes a composed routing-map path (`about`, `company/about`, `'/'`), not a
- * raw slug field — `'/'` is the home screen and is never reserved.
- */
-export declare function reservedScreenRouteSegment(path: string | null | undefined): string | undefined;
-/**
- * The refusal an author reads when {@link reservedScreenRouteSegment} names a
- * segment. One sentence, in one place, because the Screens page, the version
- * view and the besigner all have to say the same thing — three surfaces
- * wording a platform constraint three ways is how AGL-2093's precheck drifted.
- */
-export declare function reservedScreenRouteMessage(segment: string): string;
-/**
- * Does a raw slug value carry a path separator the one segment it describes
- * cannot hold (AGL-2572)?
- *
- * {@link normalizeScreenSlug} answers with a SINGLE segment, and it gets there
- * by deleting every character outside `[a-z0-9-_]` — an interior `/` included.
- * Whitespace becomes a `-`, but a `/` becomes nothing at all, so
- * `alternatives/webflow` normalizes to `alternativeswebflow` and the two words
- * are stored glued. Nothing about that is visible: the field accepts the
- * keystroke, the composed path reads plausibly, and the screen ends up
- * answering an address nobody typed. Two screens on `aglyn-marketing` carry a
- * slug of that shape.
- *
- * So the separator is a question a slug field asks BEFORE normalizing, and the
- * answer is a refusal rather than a silent repair — the caller cannot know
- * which segment the author meant, and guessing is how the glue happened.
- *
- * LEADING and TRAILING slashes are not separators here. `normalizeScreenSlug`
- * strips them deliberately (`/about/` → `about`), an author typing an address
- * writes them without meaning a hierarchy, and refusing them would reject a
- * value the normalizer has always handled correctly. `'/'` alone is the home
- * page and is never a separator.
- */
-export declare function screenSlugHasPathSeparator(input: string | null | undefined): boolean;
-/**
- * The refusal an author reads when {@link screenSlugHasPathSeparator} answers
- * true. One sentence, in one place, for the same reason
- * {@link reservedScreenRouteMessage} is: the Screens page, the version view
- * and the besigner all take a slug, and a constraint worded three ways drifts
- * into three different constraints.
- *
- * It names the alternative, because a `/` in this field almost always means
- * "nest me" and the hierarchy is what actually composes the longer path.
- */
-export declare const SCREEN_SLUG_PATH_SEPARATOR_MESSAGE: string;
+export { normalizeScreenSlug, RESERVED_SCREEN_ROUTE_SEGMENTS, reservedScreenRouteMessage, reservedScreenRouteSegment, SCREEN_ROOT_PATH, SCREEN_SLUG_PATH_SEPARATOR_MESSAGE, screenSlugHasPathSeparator, } from './screen-slug';
 /**
  * `kind` of a page GROUP (AGL-3463): a folder in the Pages list that holds
  * pages and is not one.

package/src/lib/app-utils/screen-route.js

@@ -16,159 +16,10 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
  * limitations under the License.
  */ import { HOST_ERROR_SCREEN_SLOTS } from "../foundation/index.js";
 import { collectionListUrl } from "./collection-entries.js";
-import { ENTRY_PREVIEW_ROUTE_SEGMENT } from "./entry-preview-link.js";
-import { LEAVING_NOTICE_ROUTE_SEGMENT } from "./leaving-notice.js";
-import { PLATFORM_BRAND_NAME } from "./platform-brand.js";
 import { SCREEN_KIND_EMAIL } from "./screen-kind.js";
+import { SCREEN_ROOT_PATH } from "./screen-slug.js";
 import { formatCollectionLinkValue, formatEntryLinkValue, formatFeedLinkValue, parseEntryLinkValue } from "./screen-link-value.js";
-/**
- * Route path of a host's root screen. The tenant matcher joins the catch-all
- * segments and collapses an empty one to this value (`load-page-data.ts`:
- * `slugSegments.length ? slugSegments.join('/') : SCREEN_ROOT_PATH`), so the
- * root is `'/'` and every other path is slash-joined segments WITHOUT a
- * leading slash (`about`, later `company/about`).
- */ export const SCREEN_ROOT_PATH = '/';
-/**
- * Normalizes user slug input into the routing-map path format described on
- * {@link SCREEN_ROOT_PATH}. `'/'` normalizes to the root path; anything else
- * becomes a single lowercase url-safe segment.
- *
- * Returns `undefined` for EMPTY input and for anything that sanitizes away
- * (`'###'`) — the two cases are deliberately the same answer, and the caller
- * decides what it means. In the Screens page's slug field an empty string
- * means "no address typed"; in a starter template it meant "home". Two
- * meanings for one value is what made AGL-1575 possible, so this function
- * refuses to pick one: a caller that wants the root must say `'/'`.
- *
- * This docstring used to claim empty input normalized to the root, which the
- * code has never done (see the spec, which asserts the `undefined`). A fix
- * written against the docstring instead of the behaviour would have shipped
- * broken; if you are here to make the code match the comment, do not.
- */ export function normalizeScreenSlug(input) {
-    const trimmed = (input != null ? input : '').trim();
-    if (!trimmed) return undefined;
-    if (trimmed === SCREEN_ROOT_PATH) return SCREEN_ROOT_PATH;
-    const segment = trimmed.toLowerCase().replace(/^\/+|\/+$/g, '').replace(/\s+/g, '-').replace(/[^a-z0-9-_]/g, '').replace(/-{2,}/g, '-').replace(/^-+|-+$/g, '');
-    return segment || undefined;
-}
-/**
- * Route segments the published site CANNOT serve, whatever the routing map
- * says (AGL-2076).
- *
- * Every entry was measured against production on 2026-08-19 with a fresh
- * `x-vercel-cache: MISS`, because a stale negative always passes. Two
- * mechanisms, both of which resolve ahead of `[host]/[scheme]/[[...slug]]`:
- *
- *  - `404`, `500` — Next emits `pages/404.html` and `pages/500.html` even for
- *    an app-router-only build, and the deployed filesystem answers them as
- *    static files (`content-disposition: inline; filename="404"`,
- *    `accept-ranges`, an `etag`, and no `x-nextjs-prerender`). The tenant
- *    middleware's own CSP headers are on those responses, so the middleware
- *    ran and its rewrite still lost. There is no rewrite this app can write
- *    that beats them, which is why the honest fix is to refuse the slug at
- *    authoring time rather than to keep promising an address that is dead.
- *  - `search`, `api`, `_next`, `_static` — routes and exclusions the tenant
- *    app owns. `/search` matches `app/[host]/[scheme]/search`; the other three are the
- *    middleware matcher's exclusions, so no host rewrite happens at all and
- *    the path is parsed as `[host]` with an empty slug.
- *  - `aglyn-preview` — the same mechanism as `search`, one route over
- *    (AGL-3205). The live-site preview of an unpublished collection entry is
- *    a rewrite to `app/[host]/[scheme]/aglyn-preview/[...slug]`, because it
- *    must be a DIFFERENT Next route from the ISR-cached catch-all; a static
- *    folder wins over the optional catch-all beside it, so `/aglyn-preview/x`
- *    would reach the preview page and 404 rather than render a screen. The
- *    bare `/aglyn-preview` would in fact still serve — the preview route's
- *    catch-all is required, not optional — and it is reserved anyway for the
- *    reason given below about child paths: a child's path is composed from
- *    its parent's slug, and this rule refuses that slug.
- *  - `_aglyn` — the platform's own pages on every site, the leaving notice
- *    at `/_aglyn/leaving` first (AGL-3452). The middleware rewrites that path
- *    to an api route before the catch-all could see it.
- *
- * NOT reserved, and deliberately so, because measuring found them fine:
- * `401`, `403`, `503` (`/401` returns 200 through the catch-all — two of the
- * four designed error screens have always been viewable at their slugs, which
- * is what made the `404` case look like a Next.js defect), and `index`.
- *
- * `fonts` and `examples` USED to be dead for the third reason and are not
- * here: they were exclusions inherited from the Vercel platforms starter kit
- * for directories `apps/tenant/public` has never contained. They are given
- * back rather than reserved — see the matcher in `apps/tenant/middleware.ts`.
- */ export const RESERVED_SCREEN_ROUTE_SEGMENTS = [
-    '404',
-    '500',
-    'search',
-    ENTRY_PREVIEW_ROUTE_SEGMENT,
-    'api',
-    '_next',
-    '_static',
-    LEAVING_NOTICE_ROUTE_SEGMENT
-];
-/**
- * The reserved segment a routing-map path would collide with, or `undefined`
- * when the path is servable. The segment rather than a boolean, so a refusal
- * can name what it is refusing over.
- *
- * Reads the FIRST segment only. For `api`/`_next`/`_static` that is exactly
- * right — the middleware excludes the whole subtree, so `api/docs` is as dead
- * as `api`. For `404`/`500`/`search` it over-refuses in principle (`/404/why`
- * would serve), and that is deliberate: a child path is composed from its
- * PARENT's slug, the parent would have to hold `404`, and this same rule
- * refuses that slug wherever one is typed. A second list to express a case
- * that cannot arise would be a second list to keep correct.
- *
- * Takes a composed routing-map path (`about`, `company/about`, `'/'`), not a
- * raw slug field — `'/'` is the home screen and is never reserved.
- */ export function reservedScreenRouteSegment(path) {
-    if (!path || path === SCREEN_ROOT_PATH) return undefined;
-    const [first] = path.replace(/^\/+/, '').split('/');
-    return RESERVED_SCREEN_ROUTE_SEGMENTS.includes(first) ? first : undefined;
-}
-/**
- * The refusal an author reads when {@link reservedScreenRouteSegment} names a
- * segment. One sentence, in one place, because the Screens page, the version
- * view and the besigner all have to say the same thing — three surfaces
- * wording a platform constraint three ways is how AGL-2093's precheck drifted.
- */ export function reservedScreenRouteMessage(segment) {
-    return `"/${segment}" is a reserved address on every ${PLATFORM_BRAND_NAME} site — pick another slug`;
-}
-/**
- * Does a raw slug value carry a path separator the one segment it describes
- * cannot hold (AGL-2572)?
- *
- * {@link normalizeScreenSlug} answers with a SINGLE segment, and it gets there
- * by deleting every character outside `[a-z0-9-_]` — an interior `/` included.
- * Whitespace becomes a `-`, but a `/` becomes nothing at all, so
- * `alternatives/webflow` normalizes to `alternativeswebflow` and the two words
- * are stored glued. Nothing about that is visible: the field accepts the
- * keystroke, the composed path reads plausibly, and the screen ends up
- * answering an address nobody typed. Two screens on `aglyn-marketing` carry a
- * slug of that shape.
- *
- * So the separator is a question a slug field asks BEFORE normalizing, and the
- * answer is a refusal rather than a silent repair — the caller cannot know
- * which segment the author meant, and guessing is how the glue happened.
- *
- * LEADING and TRAILING slashes are not separators here. `normalizeScreenSlug`
- * strips them deliberately (`/about/` → `about`), an author typing an address
- * writes them without meaning a hierarchy, and refusing them would reject a
- * value the normalizer has always handled correctly. `'/'` alone is the home
- * page and is never a separator.
- */ export function screenSlugHasPathSeparator(input) {
-    const trimmed = (input != null ? input : '').trim();
-    if (!trimmed || trimmed === SCREEN_ROOT_PATH) return false;
-    return trimmed.replace(/^\/+|\/+$/g, '').includes('/');
-}
-/**
- * The refusal an author reads when {@link screenSlugHasPathSeparator} answers
- * true. One sentence, in one place, for the same reason
- * {@link reservedScreenRouteMessage} is: the Screens page, the version view
- * and the besigner all take a slug, and a constraint worded three ways drifts
- * into three different constraints.
- *
- * It names the alternative, because a `/` in this field almost always means
- * "nest me" and the hierarchy is what actually composes the longer path.
- */ export const SCREEN_SLUG_PATH_SEPARATOR_MESSAGE = 'A slug is one path segment — remove the "/" and nest the page under a ' + 'parent page instead';
+export { normalizeScreenSlug, RESERVED_SCREEN_ROUTE_SEGMENTS, reservedScreenRouteMessage, reservedScreenRouteSegment, SCREEN_ROOT_PATH, SCREEN_SLUG_PATH_SEPARATOR_MESSAGE, screenSlugHasPathSeparator } from "./screen-slug.js";
 /**
  * `kind` of a page GROUP (AGL-3463): a folder in the Pages list that holds
  * pages and is not one.