astroidjs 0.12.1 → 0.14.0

package/dist/email/inquiry.d.ts

@@ -3,7 +3,7 @@ import type { SecretSource } from "../secrets.js";
 import type { EmailSender } from "./send.js";
 import { type DeliveryResult } from "./send.js";
 import { type MailThemeOverrides } from "./theme.js";
-/** The bindings the inquiry hook reads. All optional — an unprovisioned mail
+/** The bindings the inquiry hook reads. All optional—an unprovisioned mail
  *  setup logs instead of sending, per the dormant-until-provisioned convention. */
 export interface AstroidMailEnv {
     /** Cloudflare Email Sending binding. */
@@ -11,7 +11,7 @@ export interface AstroidMailEnv {
     /**
      * Envelope sender; its domain must be onboarded for Email Sending. A
      * `SecretSource` rather than a plain string so a Secrets Store binding works
-     * here too — and so the placeholder sentinel reads as unconfigured.
+     * here too—and so the placeholder sentinel reads as unconfigured.
      */
     MAIL_FROM?: SecretSource;
     /** Where owner notifications go. Also the first editor's address. */

package/dist/email/inquiry.js

@@ -7,7 +7,7 @@
 // the submission is already durable, so mail is a notification of something that
 // already happened and can fail without the visitor ever knowing.
 //
-// Two messages, not one — every site converged on the pair. The owner needs the
+// Two messages, not one—every site converged on the pair. The owner needs the
 // message; the visitor needs to know it arrived, because a contact form with no
 // acknowledgement is indistinguishable from one that's broken.
 import { resolveMailer, sendTransactional } from "./send.js";

package/dist/email/send.d.ts

@@ -18,7 +18,7 @@ export interface MailerStatus {
     /** True only when a binding AND a real sender address are both present. */
     configured: boolean;
     values: ModuleSecrets<"MAIL_FROM">["values"];
-    /** What's unprovisioned — secret names and/or `"EMAIL"`. */
+    /** What's unprovisioned—secret names and/or `"EMAIL"`. */
     missing: string[];
     /** Whether an Email Sending binding is present at all. */
     hasBinding: boolean;
@@ -34,7 +34,7 @@ export interface MailerEnv {
  * Both halves are required, and for the same reason: a binding with no sender
  * address can't build an envelope, and a sender address with no binding has
  * nothing to send through. Either one missing means log-and-continue, which
- * under `wrangler dev` (no EMAIL binding at all) is the normal case — and the
+ * under `wrangler dev` (no EMAIL binding at all) is the normal case—and the
  * reason the magic-link flow is still workable locally.
  */
 export declare function resolveMailerStatus(env: MailerEnv): Promise<MailerStatus>;
@@ -54,7 +54,7 @@ export declare function resolveMailer(env: MailerEnv, overrides?: Partial<Omit<M
 export interface OutgoingMail {
     to: string;
     content: MailContent;
-    /** Reply-To — for an inquiry notification, the visitor's own address, so the
+    /** Reply-To—for an inquiry notification, the visitor's own address, so the
      *  owner can just hit reply. */
     replyTo?: string;
 }
@@ -64,7 +64,7 @@ export interface DeliveryResult {
     subject: string;
     delivered: boolean;
     messageId?: string;
-    /** Why it wasn't delivered — `"not-configured"`, `"log-only"`, or the error. */
+    /** Why it wasn't delivered—`"not-configured"`, `"log-only"`, or the error. */
     reason?: string;
 }
 export interface MailerOptions {

package/dist/email/send.js

@@ -5,11 +5,11 @@
 // Transactional mail in this stack is always store-and-forward: the inquiry row
 // is already in D1, the account already exists. Mail is the *notification* of
 // something that happened, so a mail failure must never fail the request that
-// caused it — and never throw into a `waitUntil` where it becomes an unhandled
+// caused it—and never throw into a `waitUntil` where it becomes an unhandled
 // rejection. Every path here resolves.
 //
 // The second job is the dev story. There is no EMAIL binding under `wrangler
-// dev`, and the single most common local task is "click the magic link" — so an
+// dev`, and the single most common local task is "click the magic link"—so an
 // unconfigured mailer LOGS the message instead of silently dropping it, and it
 // logs the plaintext body, which is where the link is. That is the whole reason
 // every template renders a text alternative.
@@ -32,7 +32,7 @@ export const EMAIL_SECRET_NAMES = ["MAIL_FROM"];
  * Both halves are required, and for the same reason: a binding with no sender
  * address can't build an envelope, and a sender address with no binding has
  * nothing to send through. Either one missing means log-and-continue, which
- * under `wrangler dev` (no EMAIL binding at all) is the normal case — and the
+ * under `wrangler dev` (no EMAIL binding at all) is the normal case—and the
  * reason the magic-link flow is still workable locally.
  */
 export async function resolveMailerStatus(env) {
@@ -67,11 +67,11 @@ export async function resolveMailer(env, overrides = {}) {
 /**
  * The console rendering of an unsent message.
  *
- * The body is the whole point in dev — that's where a sign-in link actually is,
+ * The body is the whole point in dev—that's where a sign-in link actually is,
  * and printing it is what lets you sign in with no mail provider configured.
  *
  * It is also a credential. `logOnly` turns on whenever `MAIL_FROM` is unset, and
- * that can happen in PRODUCTION — a secret that didn't get set, or a Secrets
+ * that can happen in PRODUCTION—a secret that didn't get set, or a Secrets
  * Store read that failed. The body then went to `console.info`, which means
  * `wrangler tail` and every Logpush sink, carrying live single-use magic links
  * and password-reset URLs. Anyone with read access to observability could take
@@ -105,7 +105,7 @@ function describe(mail, reason, includeBody) {
 /**
  * Best-effort "are we in development?".
  *
- * Deliberately conservative — it decides whether a credential is printed, so an
+ * Deliberately conservative—it decides whether a credential is printed, so an
  * unknown environment must read as production. Workers has no `NODE_ENV`, so we
  * look at the signals that do exist and let a caller override explicitly.
  */
@@ -176,7 +176,7 @@ export async function sendTransactional(options, mails) {
         // A genuine delivery failure is LOGGED, not just returned.
         //
         // The result array was the only record of it, and the one caller that
-        // matters — the generated inquiry handler — discards it by design (the row
+        // matters—the generated inquiry handler—discards it by design (the row
         // is already durable, and the visitor must not see a 500 because the owner's
         // notification bounced). So a dead Email Sending domain or an exhausted
         // quota produced silence everywhere: a success page for the visitor, nothing

package/dist/email/templates.js

@@ -4,7 +4,7 @@
 // inquiry pair (notify the owner, confirm to the sender).
 //
 // All three consuming sites wrote these four, with the same structure and
-// near-identical copy — only the brand name differed, which is exactly what
+// near-identical copy—only the brand name differed, which is exactly what
 // makes them first-party rather than site-side. The brand-agnostic *frame*
 // (card, colour band, CTA button, paste-this-link fallback) already lives in
 // `louise-toolkit/email`; this file owns the wording and the layout inside it.
@@ -24,7 +24,7 @@ const label = (theme, text, margin = "0 0 10px") => `<p style="font-family:${the
 /** A quoted block for user-authored text (a message body). */
 const quote = (theme, text) => `<div style="font-family:${theme.fonts.sans};font-size:15px;line-height:1.65;color:${theme.palette.ink};padding:16px 18px;background:${theme.palette.bgSoft};border:1px solid ${theme.palette.rule};border-radius:6px;">${escapeMultiline(text)}</div>`;
 /**
- * A one-time link email — the shared shape behind sign-in and password reset.
+ * A one-time link email—the shared shape behind sign-in and password reset.
  * Both are "here is a URL, it expires, ignore this if it wasn't you", and the
  * only differences are the words.
  */
@@ -146,7 +146,7 @@ ${i.regarding?.trim() ? row("Regarding", escapeHtml(i.regarding.trim())) : ""}
 /** Confirmation back to whoever submitted the contact form. */
 export function inquiryConfirmationEmail(theme, i) {
     const brand = theme.brand.name;
-    // Only the given name — "Hi Jane Smith" reads like a form letter, which is
+    // Only the given name—"Hi Jane Smith" reads like a form letter, which is
     // precisely what this is trying not to.
     const first = i.name.trim().split(/\s+/)[0] || "there";
     const bodyHtml = [

package/dist/email/theme.d.ts

@@ -19,6 +19,6 @@ export interface MailThemeOverrides {
  * ```
  *
  * An invalid or missing brand colour falls back to the ink neutral rather than
- * throwing — a malformed hex in settings should not take out password reset.
+ * throwing—a malformed hex in settings should not take out password reset.
  */
 export declare function astroidMailTheme(config: AstroidConfig, overrides?: MailThemeOverrides): MailTheme;

package/dist/email/theme.js

@@ -2,7 +2,7 @@
 //
 // Deriving a `MailTheme` from the project's brand.
 //
-// The toolkit's email shell takes a fully-specified theme — ten palette slots, a
+// The toolkit's email shell takes a fully-specified theme—ten palette slots, a
 // colour band, three font stacks. Every site hand-picked all of it, which is
 // exactly the kind of work a config should absorb: an Astroid project already
 // declares `theme.colors`, and that is enough to produce a mail theme that looks
@@ -11,7 +11,7 @@
 // Two decisions here are load-bearing:
 //
 //   1. **Neutrals are fixed, brand colours are derived.** Page background, ink,
-//      rules — those are typography choices, not brand ones, and a site that
+//      rules—those are typography choices, not brand ones, and a site that
 //      wants different ones passes an override. What varies per brand is the
 //      accent and the colour band, and both come from `theme.colors`.
 //   2. **The accent is contrast-corrected.** A pale brand colour used verbatim
@@ -60,7 +60,7 @@ function contrast(a, b) {
 /**
  * Darken `color` until it clears `minRatio` against `bg`. A brand colour is
  * chosen to look good on a website, and plenty of good ones (yellows, pale
- * teals) are illegible as 11px uppercase text on a near-white email card — mail
+ * teals) are illegible as 11px uppercase text on a near-white email card—mail
  * clients offer no dark-mode escape hatch, so this is corrected up front.
  */
 function readableOn(color, bg, minRatio = 4.5) {
@@ -118,7 +118,7 @@ function buildFonts(font) {
  * ```
  *
  * An invalid or missing brand colour falls back to the ink neutral rather than
- * throwing — a malformed hex in settings should not take out password reset.
+ * throwing—a malformed hex in settings should not take out password reset.
  */
 export function astroidMailTheme(config, overrides = {}) {
     const cardBg = hexToRgb(NEUTRALS.bg) ?? WHITE;

package/dist/errors.d.ts

@@ -10,7 +10,7 @@ export declare class AstroidConfigError extends Error {
  * Distinct from {@link AstroidConfigError}, which is a build-time contract: this
  * one fires on a live request, so it must be something a handler can catch and
  * turn into a 5xx rather than something that reads like a misconfigured project.
- * Reserved for cases where carrying on would be worse than failing — a checkout
+ * Reserved for cases where carrying on would be worse than failing—a checkout
  * whose idempotency key collides with another customer's, say, where the damage
  * (a buyer who is never charged) is invisible at the call site.
  */

package/dist/errors.js

@@ -18,7 +18,7 @@ export class AstroidConfigError extends Error {
  * Distinct from {@link AstroidConfigError}, which is a build-time contract: this
  * one fires on a live request, so it must be something a handler can catch and
  * turn into a 5xx rather than something that reads like a misconfigured project.
- * Reserved for cases where carrying on would be worse than failing — a checkout
+ * Reserved for cases where carrying on would be worse than failing—a checkout
  * whose idempotency key collides with another customer's, say, where the damage
  * (a buyer who is never charged) is invisible at the call site.
  */

package/dist/index.js

@@ -1,6 +1,6 @@
 // Copyright (c) 2026 BowenLabs. Astroid is MIT licensed.
 //
-// astroidjs — the opinionated meta-framework over Louise Toolkit + Astro.
+// astroidjs—the opinionated meta-framework over Louise Toolkit + Astro.
 // Public entry. The configuration surface (`defineAstroid`) is the first
 // inhabitant; the generator, theme system, and section library follow.
 export * from "./analytics/index.js";

package/dist/map/pmtiles.d.ts

@@ -14,7 +14,7 @@ export type RangeSpec = {
 /**
  * How the archive is read. A function rather than a bucket interface, and
  * deliberately so: `R2Bucket.get` is overloaded, and its first overload
- * *requires* an options argument — which means no structural interface with an
+ * *requires* an options argument—which means no structural interface with an
  * optional second parameter can accept a real `R2Bucket`. Taking a reader lets
  * the call site use R2's own types and resolves the mismatch at the source, and
  * incidentally makes this work over any storage rather than only R2.
@@ -29,7 +29,7 @@ export interface RangeObject {
     body?: ReadableStream | null;
     /** Size of the WHOLE object, not the returned slice. */
     size: number;
-    /** What R2 actually returned — it clamps a range that runs past the end. */
+    /** What R2 actually returned—it clamps a range that runs past the end. */
     range?: {
         offset?: number;
         length?: number;
@@ -58,7 +58,7 @@ export type ParsedRange = {
  * Handles the three forms that matter:
  *   `bytes=0-1023`   a bounded window
  *   `bytes=1024-`    open-ended, to the end
- *   `bytes=-20000`   the LAST n bytes — the one the reference dropped
+ *   `bytes=-20000`   the LAST n bytes—the one the reference dropped
  *
  * Multi-range (`bytes=0-99,200-299`) returns null: it requires a multipart
  * response no PMTiles client asks for, and serving the whole object is the
@@ -69,8 +69,8 @@ export interface PmtilesHandlerOptions {
     /** Reads the archive, whole or by range. See {@link RangeReader}. */
     read: RangeReader;
     /**
-     * `Cache-Control` for the response. An archive is immutable — a re-clip
-     * overwrites the object wholesale — so the byte ranges cache hard at the
+     * `Cache-Control` for the response. An archive is immutable—a re-clip
+     * overwrites the object wholesale—so the byte ranges cache hard at the
      * edge. Default one day.
      */
     cacheControl?: string;

package/dist/map/pmtiles.js

@@ -1,6 +1,6 @@
 // Copyright (c) 2026 BowenLabs. Astroid is MIT licensed.
 //
-// Byte-range serving from R2 — the plumbing under the self-hosted basemap.
+// Byte-range serving from R2—the plumbing under the self-hosted basemap.
 //
 // A PMTiles archive is one immutable blob, often hundreds of megabytes, and the
 // client reads a few kilobytes at a time: a header, then directory pages, then
@@ -13,7 +13,7 @@
 //
 // The range parsing is deliberately complete. The implementation this
 // generalizes matched only `bytes=<start>-<end?>`, so a SUFFIX range
-// (`bytes=-20000`, "the last 20 KB" — how a client reads a footer without
+// (`bytes=-20000`, "the last 20 KB"—how a client reads a footer without
 // knowing the length) fell through to serving the ENTIRE archive. That is a
 // correct-looking response and a catastrophic one.
 /**
@@ -22,7 +22,7 @@
  * Handles the three forms that matter:
  *   `bytes=0-1023`   a bounded window
  *   `bytes=1024-`    open-ended, to the end
- *   `bytes=-20000`   the LAST n bytes — the one the reference dropped
+ *   `bytes=-20000`   the LAST n bytes—the one the reference dropped
  *
  * Multi-range (`bytes=0-99,200-299`) returns null: it requires a multipart
  * response no PMTiles client asks for, and serving the whole object is the
@@ -57,7 +57,7 @@ export function parseRangeHeader(header, size) {
     const end = Number(bounded[2]);
     if (end < start)
         return { kind: "unsatisfiable" };
-    // An end past the object is clamped, not an error — a client asking for more
+    // An end past the object is clamped, not an error—a client asking for more
     // than exists gets what exists.
     return { kind: "range", offset: start, length: Math.min(end, size - 1) - start + 1 };
 }
@@ -107,7 +107,7 @@ export async function servePmtiles(request, options) {
             : { offset: parsed.offset, ...(parsed.length ? { length: parsed.length } : {}) });
         if (!object)
             return new Response("Basemap not found", { status: 404 });
-        // Trust what R2 says it returned rather than what was asked for — it clamps
+        // Trust what R2 says it returned rather than what was asked for—it clamps
         // ranges, and a Content-Range that disagrees with the body corrupts the
         // client's view of the archive.
         const got = object.range ?? {};

package/dist/map/scaffold.d.ts

@@ -6,7 +6,7 @@ export declare const ASTROID_PMTILES_PATH = "/map/basemap.pmtiles";
 /** True when this project switched the map module on. */
 export declare const usesMap: (config: AstroidConfig) => boolean;
 /**
- * `src/pages/map/basemap.pmtiles.ts` — the range-serving tile route.
+ * `src/pages/map/basemap.pmtiles.ts`—the range-serving tile route.
  *
  * Thin: `servePmtiles` owns range parsing, the 206/416 contract, and trusting
  * R2's clamped range over the requested one. What's here is which bucket and
@@ -14,7 +14,7 @@ export declare const usesMap: (config: AstroidConfig) => boolean;
  */
 export declare function generateMapTileRoute(config: AstroidConfig): string | null;
 /**
- * `src/components/MapEmbed.astro` — the map itself.
+ * `src/components/MapEmbed.astro`—the map itself.
  *
  * The lazy load is not an optimisation detail, it's the reason this is usable:
  * MapLibre is ~1 MB, and a location map is almost always below the fold. The

package/dist/map/scaffold.js

@@ -5,8 +5,8 @@
 // GENERATED rather than shipped as a component, for a concrete reason. MapLibre
 // GL is ~1 MB and `pmtiles` is its companion; a `MapEmbed.astro` living in
 // astroid's own `src/components/` would make both a hard requirement of the
-// package — every project installing them, and the CI probe that type-checks
-// the component library needing them too — for a feature most sites never turn
+// package—every project installing them, and the CI probe that type-checks
+// the component library needing them too—for a feature most sites never turn
 // on. Generating the component into the projects that enable the module keeps
 // the dependency where the decision was made.
 //
@@ -19,7 +19,7 @@ export const ASTROID_PMTILES_PATH = "/map/basemap.pmtiles";
 /** True when this project switched the map module on. */
 export const usesMap = (config) => (config.modules ?? []).includes("map");
 /**
- * `src/pages/map/basemap.pmtiles.ts` — the range-serving tile route.
+ * `src/pages/map/basemap.pmtiles.ts`—the range-serving tile route.
  *
  * Thin: `servePmtiles` owns range parsing, the 206/416 contract, and trusting
  * R2's clamped range over the requested one. What's here is which bucket and
@@ -30,7 +30,7 @@ export function generateMapTileRoute(config) {
         return null;
     return [
         "// Serves the self-hosted Protomaps basemap (one PMTiles archive) from R2,",
-        "// same-origin, with HTTP range support — the client reads only the byte",
+        "// same-origin, with HTTP range support—the client reads only the byte",
         "// ranges it needs per tile.",
         "//",
         "// Same-origin is the point: no external tile host and no API key means the",
@@ -38,7 +38,7 @@ export function generateMapTileRoute(config) {
         "// irrelevant.",
         "//",
         "// Upload an archive to this key before the map draws anything (until then",
-        "// the canvas shows its background and pin — the module is dormant, not",
+        "// the canvas shows its background and pin—the module is dormant, not",
         "// broken):",
         `//   wrangler r2 object put ${config.key}-media/${ASTROID_PMTILES_KEY} \\`,
         "//     --file=extract.pmtiles --content-type=application/octet-stream --remote",
@@ -68,7 +68,7 @@ export function generateMapTileRoute(config) {
     ].join("\n");
 }
 /**
- * `src/components/MapEmbed.astro` — the map itself.
+ * `src/components/MapEmbed.astro`—the map itself.
  *
  * The lazy load is not an optimisation detail, it's the reason this is usable:
  * MapLibre is ~1 MB, and a location map is almost always below the fold. The
@@ -82,7 +82,7 @@ export function generateMapEmbedComponent(config) {
     return [
         "---",
         "// A MapLibre map over the self-hosted PMTiles basemap, centred on exact",
-        "// coordinates. Scaffolded once; yours to edit — the pin, the gestures, and",
+        "// coordinates. Scaffolded once; yours to edit—the pin, the gestures, and",
         "// the placeholder are brand decisions.",
         "//",
         "// Coordinates, never a geocoded address string: geocoding at render time is",
@@ -195,7 +195,7 @@ export function generateMapEmbedComponent(config) {
         "          if (!entry.isIntersecting) continue;",
         "          obs.unobserve(entry.target);",
         "          // `init` is async and nothing awaits it, so without this catch a",
-        "          // failed chunk fetch — a page load racing a deploy is enough — is a",
+        "          // failed chunk fetch—a page load racing a deploy is enough—is a",
         "          // silent unhandled rejection: the container just stays an empty",
         "          // tinted box with nothing in the console to explain it.",
         "          init(entry.target as HTMLElement).catch((err) => {",

package/dist/map/style.d.ts

@@ -27,18 +27,18 @@ export interface MapStyleOptions {
     pmtilesUrl: string;
     colors?: MapColors;
     /**
-     * SDF glyph URL template (e.g. `"/map/fonts/{fontstack}/{range}.pbf"`).
-     * Omit for an unlabelled map — which is the honest default, since labels
+     * SDF glyph URL template (for example, `"/map/fonts/{fontstack}/{range}.pbf"`).
+     * Omit for an unlabelled map—which is the honest default, since labels
      * without self-hosted glyphs mean an external font host and a looser CSP.
      */
     glyphs?: string;
     /** Font stack for labels. Only used when `glyphs` is set. */
     fontstack?: string;
     /** Attribution shown in the corner. Protomaps basemaps derive from OSM, and
-     *  the licence requires the credit — so it defaults to present, not absent. */
+     *  the licence requires the credit—so it defaults to present, not absent. */
     attribution?: string;
 }
-/** A MapLibre style. Typed loosely on purpose — see the header. */
+/** A MapLibre style. Typed loosely on purpose—see the header. */
 export interface MapStyle {
     version: 8;
     glyphs?: string;

package/dist/map/style.js

@@ -6,7 +6,7 @@
 // rather than importing `maplibre-gl` (a megabyte) or `protomaps-themes-base`
 // for its types. astroidjs stays installable by a project that will never draw
 // a map, and a project that wants Protomaps' full maintained theme can swap
-// this out — the only contract is "an object MapLibre accepts".
+// this out—the only contract is "an object MapLibre accepts".
 //
 // The layer set is the quiet-basemap subset: land, water, green space, a road
 // ramp with casings, buildings, and admin boundaries. Labels are opt-in and

package/dist/portal/config.d.ts

@@ -3,8 +3,8 @@ import type { PortalGuardConfig, PortalRoute } from "./guard.js";
 /** Cookie prefix for the portal instance. Distinct from the studio's default
  *  (`better-auth`) so the two sessions can coexist on one origin. */
 export declare const ASTROID_PORTAL_COOKIE_PREFIX = "portal";
-/** Table-name prefix for the portal's Better Auth tables — `portal_user`,
- *  `portal_session`, … The studio owns the unprefixed names. */
+/** Table-name prefix for the portal's Better Auth tables—`portal_user`,
+ *  `portal_session`, … The studio's tables carry the `louise_` prefix. */
 export declare const ASTROID_PORTAL_TABLE_PREFIX = "portal_";
 /** Everything the generated portal wiring needs, defaults applied. */
 export interface ResolvedPortal {
@@ -13,7 +13,7 @@ export interface ResolvedPortal {
     cookiePrefix: string;
     tablePrefix: string;
     roles: string[];
-    /** First role in `roles` — what a newly created account gets. */
+    /** First role in `roles`—what a newly created account gets. */
     defaultRole: string;
     routes: PortalRoute[];
     home: Record<string, string>;

package/dist/portal/config.js

@@ -1,20 +1,21 @@
 // Copyright (c) 2026 BowenLabs. Astroid is MIT licensed.
 //
-// Portal defaults derived from the project config — the single place that knows
+// Portal defaults derived from the project config—the single place that knows
 // the portal's mount, cookie prefix, table prefix, and guard table.
 //
-// The isolation constants are fixed rather than configurable, and that's the
-// point: the studio instance MUST keep Better Auth's defaults (`/api/auth`, the
-// unprefixed tables) because the Louise editor client hardcodes them, so the
-// portal is the one that moves. Leaving that to a project invites the one
-// mistake that matters — two instances sharing a cookie prefix, where signing
-// into one silently signs you out of the other, intermittently, in production.
+// The studio instance keeps `/api/auth` because the Louise editor client
+// hardcodes it, so the portal is the one that moves: its own mount, cookie
+// prefix, and table prefix. The defaults are safe distinct values, and
+// `defineAstroid` rejects any override that collides with the editor. That guards
+// the one mistake that matters—two instances sharing a cookie prefix, where
+// signing into one silently signs you out of the other, intermittently, in
+// production.
 import { ASTROID_PORTAL_BASE_PATH } from "../security/rate-rules.js";
 /** Cookie prefix for the portal instance. Distinct from the studio's default
  *  (`better-auth`) so the two sessions can coexist on one origin. */
 export const ASTROID_PORTAL_COOKIE_PREFIX = "portal";
-/** Table-name prefix for the portal's Better Auth tables — `portal_user`,
- *  `portal_session`, … The studio owns the unprefixed names. */
+/** Table-name prefix for the portal's Better Auth tables—`portal_user`,
+ *  `portal_session`, … The studio's tables carry the `louise_` prefix. */
 export const ASTROID_PORTAL_TABLE_PREFIX = "portal_";
 /** Default guard table: the account area, for any signed-in portal user. */
 const DEFAULT_ROUTES = [{ prefix: "/portal" }, { prefix: "/api/portal" }];
@@ -27,7 +28,7 @@ export function astroidPortal(config) {
     return {
         enabled: true,
         // Isolation is configurable so a site with an existing second instance
-        // (coracle's shop account at /api/shop-auth, cookie `coracle_shop`, the
+        // (for example, a shop account at /api/shop-auth with its own cookie and the
         // unprefixed `user` tables) keeps its live mount + cookies unchanged. The
         // defaults stay the safe distinct-from-editor values; `defineAstroid`'s
         // `assertAuthIsolation` rejects a resolved value that collides with the

package/dist/portal/guard.d.ts

@@ -11,7 +11,7 @@ export interface PortalUser {
 }
 /** One rule: everything under `prefix` requires one of `roles`. */
 export interface PortalRoute {
-    /** Path prefix, e.g. `/portal` — matches the prefix itself and everything
+    /** Path prefix, for example, `/portal`—matches the prefix itself and everything
      *  beneath it, but NOT `/portalling`. */
     prefix: string;
     /** Roles allowed through. Empty means "any signed-in user". */
@@ -22,7 +22,7 @@ export interface PortalGuardConfig {
     routes: PortalRoute[];
     /** Where to send a signed-out visitor. Default `/login`. */
     loginPath?: string;
-    /** Landing page for a signed-in user, by role — used to bounce someone who
+    /** Landing page for a signed-in user, by role—used to bounce someone who
      *  reached an area they don't belong in. Default `/portal` for everyone. */
     home?: (role: string) => string;
 }
@@ -38,13 +38,13 @@ export type GuardDecision = null | {
         error: string;
     };
 };
-/** Prefix match on a path SEGMENT boundary — `/portal` covers `/portal` and
+/** Prefix match on a path SEGMENT boundary—`/portal` covers `/portal` and
  *  `/portal/orders`, but never `/portalling`. */
 export declare function matchesPrefix(path: string, prefix: string): boolean;
 /**
  * Decide whether a request may proceed.
  *
- * Pure — it returns a decision rather than a `Response`, so it's testable
+ * Pure—it returns a decision rather than a `Response`, so it's testable
  * without an Astro context and the middleware stays responsible for turning a
  * decision into a redirect or a body.
  */

package/dist/portal/guard.js

@@ -5,7 +5,7 @@
 // coracle and ghostfire independently built the same thing: a declarative table
 // of `prefix → roles`, walked once per request. Declarative rather than a guard
 // call inside each page, because a guard you have to remember to write is a
-// guard someone eventually forgets — and the page that forgets it is the one
+// guard someone eventually forgets—and the page that forgets it is the one
 // that leaks.
 //
 // Three answers, and which one you give matters:
@@ -14,9 +14,9 @@
 //   not signed in, API    → 401 JSON (a redirect to an HTML login page is
 //                           useless to fetch(); it looks like success)
 //   signed in, wrong role → 403 for API, and for HTML a redirect to the area
-//                           this user DOES have — not back to login, which
+//                           this user DOES have—not back to login, which
 //                           reads as "your password failed" when it didn't
-/** Prefix match on a path SEGMENT boundary — `/portal` covers `/portal` and
+/** Prefix match on a path SEGMENT boundary—`/portal` covers `/portal` and
  *  `/portal/orders`, but never `/portalling`. */
 export function matchesPrefix(path, prefix) {
     return path === prefix || path.startsWith(`${prefix}/`);
@@ -24,7 +24,7 @@ export function matchesPrefix(path, prefix) {
 /**
  * Decide whether a request may proceed.
  *
- * Pure — it returns a decision rather than a `Response`, so it's testable
+ * Pure—it returns a decision rather than a `Response`, so it's testable
  * without an Astro context and the middleware stays responsible for turning a
  * decision into a redirect or a body.
  */

package/dist/portal/nav.js

@@ -3,7 +3,7 @@
 // The portal's navigation, as data.
 //
 // Two things fall out of declaring it rather than writing markup per page.
-// Items can be filtered by the viewer's role in one place — so an item a user
+// Items can be filtered by the viewer's role in one place—so an item a user
 // can't reach is never rendered, instead of rendered-then-403'd, which reads as
 // a broken link. And "which item is active" is computed the same way the guard
 // matches prefixes, so the highlight can't disagree with the routing.
@@ -26,7 +26,7 @@ export function definePortalNav(items) {
         },
         activeFor(path) {
             // Longest href first, so `/portal/orders` wins over `/portal` on a page
-            // both would match — otherwise the parent item is always the active one.
+            // both would match—otherwise the parent item is always the active one.
             return ([...items]
                 .sort((a, b) => b.href.length - a.href.length)
                 .find((item) => matchesPrefix(path, item.href)) ?? null);

package/dist/portal/scaffold.d.ts

@@ -1,20 +1,20 @@
 import type { AstroidConfig } from "../config.js";
 /**
- * `src/portal-auth.ts` — the portal Better Auth instance and its session
+ * `src/portal-auth.ts`—the portal Better Auth instance and its session
  * resolver.
  *
  * Returns null when the project has no portal.
  */
 export declare function generateAstroidPortalAuth(config: AstroidConfig): string | null;
 /**
- * `src/pages/api/portal-auth/[...all].ts` — the portal's Better Auth catch-all,
+ * `src/pages/api/portal-auth/[...all].ts`—the portal's Better Auth catch-all,
  * mounted at its own basePath so it never collides with the studio's
  * `/api/auth`.
  *
  * Lives here rather than as a literal in `create-astroid` for the same reason
  * the archetype sections moved (#277): the scaffolder is plain JS, so a drifted
  * import path there is invisible until a user's build fails. It is also the half
- * `generateAstroidPortalAuth` is useless without — `src/portal-auth.ts` exports
+ * `generateAstroidPortalAuth` is useless without—`src/portal-auth.ts` exports
  * `handlePortalAuth`, and nothing calls it unless this route exists.
  *
  * Returns null when the project has no portal.
@@ -22,7 +22,7 @@ export declare function generateAstroidPortalAuth(config: AstroidConfig): string
 export declare function generateAstroidPortalAuthRoute(config: AstroidConfig): string | null;
 /**
  * The `App.Locals` member the portal adds, as a block `create-astroid`
- * substitutes into `src/env.d.ts`. Empty without a portal — a project that
+ * substitutes into `src/env.d.ts`. Empty without a portal—a project that
  * types `portalUser` it never sets is inviting a null-check nobody needs.
  */
 export declare function generateAstroidPortalLocals(config: AstroidConfig): string;