zitejs 0.9.108 → 0.9.110

package/dist/cjs/runtime/filterConditionTypes.test-d.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/cjs/runtime/filterConditionTypes.test-d.js

@@ -0,0 +1,40 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+const vitest_1 = require("vitest");
+(0, vitest_1.describe)("FilterCondition in/notIn", () => {
+    // The idiom that regressed. `.filter(Boolean)` does not narrow in TypeScript,
+    // so this is `(string | undefined)[]` — compiling at all is the assertion.
+    (0, vitest_1.it)("accepts .map(…).filter(Boolean) over a nullable column", () => {
+        const keys = routes.map((r) => r.compositeRouteKey).filter(Boolean);
+        (0, vitest_1.expectTypeOf)(keys).toEqualTypeOf();
+        (0, vitest_1.expectTypeOf)().toMatchTypeOf();
+        (0, vitest_1.expectTypeOf)().toMatchTypeOf();
+    });
+    // One array of a union, not a union of arrays.
+    (0, vitest_1.it)("collapses a nullable column to a single array type", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+    // The unwrapping that the conditional exists for: an array-valued column is
+    // filtered by its ELEMENT type, not by arrays of arrays.
+    (0, vitest_1.it)("still unwraps an array-valued column to its element type", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+    (0, vitest_1.it)("leaves a plain scalar column alone", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+});
+(0, vitest_1.describe)("RecordFilters", () => {
+    // Through the keyed wrapper, which is how app code actually reaches it.
+    (0, vitest_1.it)("accepts the idiom on a nullable key", () => {
+        const filters = {
+            compositeRouteKey: {
+                in: routes.map((r) => r.compositeRouteKey).filter(Boolean),
+            },
+        };
+        (0, vitest_1.expectTypeOf)(filters).toMatchTypeOf();
+    });
+    (0, vitest_1.it)("accepts an element-typed `in` on an array column", () => {
+        const filters = { tags: { in: ["urgent"] } };
+        (0, vitest_1.expectTypeOf)(filters).toMatchTypeOf();
+    });
+});

package/dist/cjs/runtime/index.d.ts

@@ -1,4 +1,3 @@
-import type { NotificationsCreateParams, NotificationsCreateResult } from "../notifications/index.js";
 /**
  * A comparison against one field. Mirrors base-runner's operator set
  * (`LegacyWhereConditionOperators`); anything else in the object is ignored.
@@ -9,6 +8,11 @@ import type { NotificationsCreateParams, NotificationsCreateResult } from "../no
  * the operands buys little while breaking real migrated code: dates are ISO
  * strings here but 1.0 accepted `number | Date` on every comparison, and
  * `contains` was `any`.
+ *
+ * On `in`/`notIn` the `[]` sits OUTSIDE the conditional. A naked `V`
+ * distributes, so a nullable column produced `string[] | undefined[]` — two
+ * separate array types, neither of which accepts the `(string | undefined)[]`
+ * that `.map(…).filter(Boolean)` yields.
  */
 export type FilterCondition<V> = {
     /** Substring match (text fields) or "has any of these" (linked records). */
@@ -16,9 +20,9 @@ export type FilterCondition<V> = {
     /** Not equal, or — against `null` — "is set". */
     not?: V | null;
     /** An empty array matches NOTHING — the SDK's filters convert to the nested format, where `in: []` is "is one of nothing". */
-    in?: V extends Array<infer E> ? E[] : V[];
+    in?: (V extends Array<infer E> ? E : V)[];
     /** An empty array applies no filter at all — "is not one of nothing" is always true. */
-    notIn?: V extends Array<infer E> ? E[] : V[];
+    notIn?: (V extends Array<infer E> ? E : V)[];
     lt?: V | number | Date;
     lte?: V | number | Date;
     gt?: V | number | Date;
@@ -328,9 +332,6 @@ export interface EmailClient {
  * app's connected email integration key.
  */
 export declare function createEmailClient(integrationId: string): EmailClient;
-export declare function createNotificationsClient(): {
-    create(params: NotificationsCreateParams): Promise<NotificationsCreateResult>;
-};
 export type { NotificationLink, NotificationsCreateParams, NotificationsCreateResult, } from "../notifications/index.js";
 export { createCaller } from "../caller/index.js";
 export type { EndpointConfig } from "../caller/index.js";

package/dist/cjs/runtime/index.js

@@ -6,7 +6,6 @@ exports.createSqlClient = createSqlClient;
 exports.createAuthClient = createAuthClient;
 exports.createAirtableClient = createAirtableClient;
 exports.createEmailClient = createEmailClient;
-exports.createNotificationsClient = createNotificationsClient;
 const sdkCall_js_1 = require("../internal/sdkCall.js");
 const DB_INTEGRATION_ID = "databases";
 function getBaseId() {
@@ -126,11 +125,5 @@ function createEmailClient(integrationId) {
         send: (params) => (0, sdkCall_js_1.getSdkCall)()(integrationId, "Email", "send", params),
     };
 }
-const NOTIFICATIONS_SDK_INTEGRATION_ID = "__notifications__";
-function createNotificationsClient() {
-    return {
-        create: (params) => (0, sdkCall_js_1.getSdkCall)()(NOTIFICATIONS_SDK_INTEGRATION_ID, "ZiteNotifications", "create", params),
-    };
-}
 var index_js_1 = require("../caller/index.js");
 Object.defineProperty(exports, "createCaller", { enumerable: true, get: function () { return index_js_1.createCaller; } });

package/dist/cjs/sync/lib.js

@@ -174,10 +174,7 @@ const tsSingleQuoted = (value) => `'${JSON.stringify(value).slice(1, -1).replace
  * Applied where the comment is written rather than at each contributor, so
  * anything added to one later is covered by default.
  */
-const commentSafe = (value) => value
-    .replace(/\*\//g, "* /")
-    .replace(/\s+/g, " ")
-    .trim();
+const commentSafe = (value) => value.replace(/\*\//g, "* /").replace(/\s+/g, " ").trim();
 const NUMBER_FORMAT_EXAMPLES = {
     local: "1,000,000.50",
     comma_period: "1,000,000.50",
@@ -563,7 +560,7 @@ function generateDbTs(inputSchema) {
     lines.push("//   - SELECT only — use .create/.update/.delete for writes");
     lines.push('//   - Load the "zite:sql" skill for full SQL reference (formulas, lookups, etc.)');
     lines.push(...buildLinkTableComments(schema));
-    lines.push("import { createTableClient, createSqlClient, createNotificationsClient, createAuthClient } from 'zitejs/runtime';");
+    lines.push("import { createTableClient, createSqlClient, createAuthClient } from 'zitejs/runtime';");
     lines.push("");
     lines.push(...ATTACHMENT_TYPES);
     for (const table of tables) {
@@ -608,7 +605,10 @@ function generateDbTs(inputSchema) {
         lines.push(`  ${table.sdkName}: createTableClient<${className}RecordType, ${className}RecordInput>('${className}'),`);
     }
     lines.push(`  sql: createSqlClient(),`);
-    lines.push(`  notifications: createNotificationsClient(),`);
+    // No `notifications` here: it is a platform primitive, not something backed
+    // by the project database, so it lives at `zitejs/notifications` alongside
+    // `zitejs/pdf` and `zitejs/schedules`. Keeping it on `zite` cost a table
+    // named "Notifications" its accessor — see RESERVED_TABLE_ACCESSORS.
     lines.push(`  auth: createAuthClient<ZiteAuthUser>(),`);
     lines.push("};");
     lines.push("");
@@ -902,7 +902,14 @@ const AIRTABLE_FIELD_INPUT_TYPE_MAP = {
     singleCollaborator: "{ id: string } | { email: string }",
     multipleCollaborators: "Array<{ id: string } | { email: string }>",
 };
-/** Mirrors `airtable/lib/attachment.d.ts`. Every property but `thumbnails` is present on a read. */
+/**
+ * Airtable's attachment object as the REST API really returns it.
+ *
+ * Not quite `airtable/lib/attachment.d.ts`: that declaration omits `width` and
+ * `height`, which the API does return for image attachments. 1.0 exposed them
+ * and apps read them, so leaving them out turns a working `photo.width` into a
+ * migration type error. Optional, because a non-image attachment has neither.
+ */
 const AIRTABLE_ATTACHMENT_TYPE = [
     "export type AirtableAttachment = {",
     "  id: string;",
@@ -912,6 +919,10 @@ const AIRTABLE_ATTACHMENT_TYPE = [
     "  size: number;",
     "  /** MIME type. */",
     "  type: string;",
+    "  /** Pixel width — images only. */",
+    "  width?: number;",
+    "  /** Pixel height — images only. */",
+    "  height?: number;",
     "  thumbnails?: {",
     "    small: { url: string; width: number; height: number };",
     "    large: { url: string; width: number; height: number };",

package/dist/cjs/sync/lib.test.js

@@ -51,6 +51,39 @@ const schemaWithSelectOption = (label) => ({
         (0, vitest_1.expect)(out).toContain('"The \\"Premium\\" tier"');
     });
 });
+(0, vitest_1.describe)('generateAirtableTs attachment type', () => {
+    const lockWithAttachment = {
+        integrationId: 'airtable',
+        tables: [
+            {
+                id: 'tbl1',
+                sdkName: 'Speakers',
+                primaryFieldId: 'fld1',
+                fields: [
+                    { id: 'fld1', sdkName: 'name', type: 'singleLineText', name: 'Name' },
+                    {
+                        id: 'fld2',
+                        sdkName: 'headshot',
+                        type: 'multipleAttachments',
+                        name: 'Headshot',
+                    },
+                ],
+            },
+        ],
+    };
+    // Reported from a migrated app reading `photo.width` to lay out an image
+    // grid. Airtable returns width/height on image attachments and 1.0 exposed
+    // them; `airtable/lib/attachment.d.ts`, which this type was copied from,
+    // omits both — so the read became a TS2339 the app could not edit away.
+    vitest_1.it.each(['width', 'height'])('exposes %s, which Airtable returns for images', prop => {
+        const out = (0, lib_js_1.generateAirtableTs)(lockWithAttachment);
+        (0, vitest_1.expect)(out).not.toBeNull();
+        (0, vitest_1.expect)(out).toContain(`  ${prop}?: number;`);
+    });
+    (0, vitest_1.it)('emits parseable TypeScript', () => {
+        (0, vitest_1.expect)(syntaxErrorsIn((0, lib_js_1.generateAirtableTs)(lockWithAttachment) ?? '')).toEqual([]);
+    });
+});
 (0, vitest_1.describe)('generateDbTs field names in comments', () => {
     // A field's display name is user text and reaches a one-line JSDoc. A
     // comment-close sequence in it would end the comment early and leave the

package/dist/cjs/sync/sdkNames.d.ts

@@ -36,8 +36,15 @@ export declare function toSdkName(name: string): string;
 /**
  * Accessors `generateDbTs` puts on the `zite` object itself, after the tables.
  * A table that allocates one of these produces a duplicate key.
+ *
+ * `notifications` used to be here and no longer is: it was a platform
+ * primitive hanging off `zite`, so a table named "Notifications" collided with
+ * it and — because the sentinel was written last — lost its client entirely.
+ * Moving it to `zitejs/notifications` removes the collision rather than
+ * managing it, and frees the name for the table that wants it. Everything left
+ * is genuinely backed by the project database.
  */
-export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "notifications", "auth"];
+export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "auth"];
 /**
  * Never safe as a generated key, in any namespace. Assigning `__proto__` in an
  * object literal sets the prototype rather than defining a property, and

package/dist/cjs/sync/sdkNames.js

@@ -66,12 +66,15 @@ function toSdkName(name) {
 /**
  * Accessors `generateDbTs` puts on the `zite` object itself, after the tables.
  * A table that allocates one of these produces a duplicate key.
+ *
+ * `notifications` used to be here and no longer is: it was a platform
+ * primitive hanging off `zite`, so a table named "Notifications" collided with
+ * it and — because the sentinel was written last — lost its client entirely.
+ * Moving it to `zitejs/notifications` removes the collision rather than
+ * managing it, and frees the name for the table that wants it. Everything left
+ * is genuinely backed by the project database.
  */
-exports.RESERVED_TABLE_ACCESSORS = [
-    "sql",
-    "notifications",
-    "auth",
-];
+exports.RESERVED_TABLE_ACCESSORS = ["sql", "auth"];
 /**
  * Never safe as a generated key, in any namespace. Assigning `__proto__` in an
  * object literal sets the prototype rather than defining a property, and

package/dist/cjs/sync/sdkNames.test.js

@@ -33,17 +33,18 @@ const recordTypeKeys = (source, typeName) => {
 };
 (0, vitest_1.describe)("reserved platform accessors", () => {
     // Sudzy Dashboard: a table named "Notifications" emitted a second
-    // `notifications:` key, and the platform client — written last — won. The
+    // `notifications:` key and the platform client — written last — won, so the
     // table lost findAll and typed as `{ create(NotificationsCreateParams) }`.
-    (0, vitest_1.it)("moves a table off the notifications accessor", () => {
+    // The platform client has since moved to `zitejs/notifications`, so the name
+    // belongs to the table again and there is nothing left to collide with.
+    (0, vitest_1.it)("lets a table keep the notifications accessor", () => {
         const schema = (0, lib_js_1.generateSchema)(database([{ id: "tbl_1", name: "Notifications", fields: [] }]));
-        (0, vitest_1.expect)(schema.tables[0].sdkName).toBe("notifications2");
+        (0, vitest_1.expect)(schema.tables[0].sdkName).toBe("notifications");
         const keys = ziteKeys((0, lib_js_1.generateDbTs)(schema));
-        (0, vitest_1.expect)(keys).toContain("notifications2");
         (0, vitest_1.expect)(keys.filter((k) => k === "notifications")).toHaveLength(1);
         (0, vitest_1.expect)(new Set(keys).size).toBe(keys.length);
     });
-    vitest_1.it.each(["sql", "auth", "notifications"])("keeps the platform %s accessor for the platform", (reserved) => {
+    vitest_1.it.each(["sql", "auth"])("keeps the platform %s accessor for the platform", (reserved) => {
         const schema = (0, lib_js_1.generateSchema)(database([{ id: "tbl_1", name: reserved, fields: [] }]));
         (0, vitest_1.expect)(schema.tables[0].sdkName).toBe(`${reserved}2`);
         const keys = ziteKeys((0, lib_js_1.generateDbTs)(schema));
@@ -192,14 +193,17 @@ const recordTypeKeys = (source, typeName) => {
     // `zitejs generate` reads it with no generateSchema pass in front, so this is
     // the only thing standing between it and a TS1117 it cannot build past.
     (0, vitest_1.it)("repairs a committed schema that already holds the collision", () => {
+        // `sql`, not `notifications` — the latter stopped being a platform
+        // accessor when the client moved to `zitejs/notifications`, so a schema
+        // holding it is no longer a collision to repair.
         const source = (0, lib_js_1.generateDbTs)({
             tables: [
-                { id: "tbl_1", sdkName: "notifications", fields: [] },
+                { id: "tbl_1", sdkName: "sql", fields: [] },
                 { id: "tbl_2", sdkName: "orders", fields: [] },
             ],
         });
         const keys = ziteKeys(source);
         (0, vitest_1.expect)(new Set(keys).size).toBe(keys.length);
-        (0, vitest_1.expect)(keys).toContain("notifications2");
+        (0, vitest_1.expect)(keys).toContain("sql2");
     });
 });

package/dist/esm/runtime/filterConditionTypes.test-d.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/esm/runtime/filterConditionTypes.test-d.js

@@ -0,0 +1,38 @@
+import { describe, it, expectTypeOf } from "vitest";
+describe("FilterCondition in/notIn", () => {
+    // The idiom that regressed. `.filter(Boolean)` does not narrow in TypeScript,
+    // so this is `(string | undefined)[]` — compiling at all is the assertion.
+    it("accepts .map(…).filter(Boolean) over a nullable column", () => {
+        const keys = routes.map((r) => r.compositeRouteKey).filter(Boolean);
+        expectTypeOf(keys).toEqualTypeOf();
+        expectTypeOf().toMatchTypeOf();
+        expectTypeOf().toMatchTypeOf();
+    });
+    // One array of a union, not a union of arrays.
+    it("collapses a nullable column to a single array type", () => {
+        expectTypeOf().toEqualTypeOf();
+    });
+    // The unwrapping that the conditional exists for: an array-valued column is
+    // filtered by its ELEMENT type, not by arrays of arrays.
+    it("still unwraps an array-valued column to its element type", () => {
+        expectTypeOf().toEqualTypeOf();
+    });
+    it("leaves a plain scalar column alone", () => {
+        expectTypeOf().toEqualTypeOf();
+    });
+});
+describe("RecordFilters", () => {
+    // Through the keyed wrapper, which is how app code actually reaches it.
+    it("accepts the idiom on a nullable key", () => {
+        const filters = {
+            compositeRouteKey: {
+                in: routes.map((r) => r.compositeRouteKey).filter(Boolean),
+            },
+        };
+        expectTypeOf(filters).toMatchTypeOf();
+    });
+    it("accepts an element-typed `in` on an array column", () => {
+        const filters = { tags: { in: ["urgent"] } };
+        expectTypeOf(filters).toMatchTypeOf();
+    });
+});

package/dist/esm/runtime/index.d.ts

@@ -1,4 +1,3 @@
-import type { NotificationsCreateParams, NotificationsCreateResult } from "../notifications/index.js";
 /**
  * A comparison against one field. Mirrors base-runner's operator set
  * (`LegacyWhereConditionOperators`); anything else in the object is ignored.
@@ -9,6 +8,11 @@ import type { NotificationsCreateParams, NotificationsCreateResult } from "../no
  * the operands buys little while breaking real migrated code: dates are ISO
  * strings here but 1.0 accepted `number | Date` on every comparison, and
  * `contains` was `any`.
+ *
+ * On `in`/`notIn` the `[]` sits OUTSIDE the conditional. A naked `V`
+ * distributes, so a nullable column produced `string[] | undefined[]` — two
+ * separate array types, neither of which accepts the `(string | undefined)[]`
+ * that `.map(…).filter(Boolean)` yields.
  */
 export type FilterCondition<V> = {
     /** Substring match (text fields) or "has any of these" (linked records). */
@@ -16,9 +20,9 @@ export type FilterCondition<V> = {
     /** Not equal, or — against `null` — "is set". */
     not?: V | null;
     /** An empty array matches NOTHING — the SDK's filters convert to the nested format, where `in: []` is "is one of nothing". */
-    in?: V extends Array<infer E> ? E[] : V[];
+    in?: (V extends Array<infer E> ? E : V)[];
     /** An empty array applies no filter at all — "is not one of nothing" is always true. */
-    notIn?: V extends Array<infer E> ? E[] : V[];
+    notIn?: (V extends Array<infer E> ? E : V)[];
     lt?: V | number | Date;
     lte?: V | number | Date;
     gt?: V | number | Date;
@@ -328,9 +332,6 @@ export interface EmailClient {
  * app's connected email integration key.
  */
 export declare function createEmailClient(integrationId: string): EmailClient;
-export declare function createNotificationsClient(): {
-    create(params: NotificationsCreateParams): Promise<NotificationsCreateResult>;
-};
 export type { NotificationLink, NotificationsCreateParams, NotificationsCreateResult, } from "../notifications/index.js";
 export { createCaller } from "../caller/index.js";
 export type { EndpointConfig } from "../caller/index.js";

package/dist/esm/runtime/index.js

@@ -117,10 +117,4 @@ export function createEmailClient(integrationId) {
         send: (params) => getSdkCall()(integrationId, "Email", "send", params),
     };
 }
-const NOTIFICATIONS_SDK_INTEGRATION_ID = "__notifications__";
-export function createNotificationsClient() {
-    return {
-        create: (params) => getSdkCall()(NOTIFICATIONS_SDK_INTEGRATION_ID, "ZiteNotifications", "create", params),
-    };
-}
 export { createCaller } from "../caller/index.js";

package/dist/esm/sync/lib.js

@@ -165,10 +165,7 @@ const tsSingleQuoted = (value) => `'${JSON.stringify(value).slice(1, -1).replace
  * Applied where the comment is written rather than at each contributor, so
  * anything added to one later is covered by default.
  */
-const commentSafe = (value) => value
-    .replace(/\*\//g, "* /")
-    .replace(/\s+/g, " ")
-    .trim();
+const commentSafe = (value) => value.replace(/\*\//g, "* /").replace(/\s+/g, " ").trim();
 const NUMBER_FORMAT_EXAMPLES = {
     local: "1,000,000.50",
     comma_period: "1,000,000.50",
@@ -551,7 +548,7 @@ export function generateDbTs(inputSchema) {
     lines.push("//   - SELECT only — use .create/.update/.delete for writes");
     lines.push('//   - Load the "zite:sql" skill for full SQL reference (formulas, lookups, etc.)');
     lines.push(...buildLinkTableComments(schema));
-    lines.push("import { createTableClient, createSqlClient, createNotificationsClient, createAuthClient } from 'zitejs/runtime';");
+    lines.push("import { createTableClient, createSqlClient, createAuthClient } from 'zitejs/runtime';");
     lines.push("");
     lines.push(...ATTACHMENT_TYPES);
     for (const table of tables) {
@@ -596,7 +593,10 @@ export function generateDbTs(inputSchema) {
         lines.push(`  ${table.sdkName}: createTableClient<${className}RecordType, ${className}RecordInput>('${className}'),`);
     }
     lines.push(`  sql: createSqlClient(),`);
-    lines.push(`  notifications: createNotificationsClient(),`);
+    // No `notifications` here: it is a platform primitive, not something backed
+    // by the project database, so it lives at `zitejs/notifications` alongside
+    // `zitejs/pdf` and `zitejs/schedules`. Keeping it on `zite` cost a table
+    // named "Notifications" its accessor — see RESERVED_TABLE_ACCESSORS.
     lines.push(`  auth: createAuthClient<ZiteAuthUser>(),`);
     lines.push("};");
     lines.push("");
@@ -890,7 +890,14 @@ const AIRTABLE_FIELD_INPUT_TYPE_MAP = {
     singleCollaborator: "{ id: string } | { email: string }",
     multipleCollaborators: "Array<{ id: string } | { email: string }>",
 };
-/** Mirrors `airtable/lib/attachment.d.ts`. Every property but `thumbnails` is present on a read. */
+/**
+ * Airtable's attachment object as the REST API really returns it.
+ *
+ * Not quite `airtable/lib/attachment.d.ts`: that declaration omits `width` and
+ * `height`, which the API does return for image attachments. 1.0 exposed them
+ * and apps read them, so leaving them out turns a working `photo.width` into a
+ * migration type error. Optional, because a non-image attachment has neither.
+ */
 const AIRTABLE_ATTACHMENT_TYPE = [
     "export type AirtableAttachment = {",
     "  id: string;",
@@ -900,6 +907,10 @@ const AIRTABLE_ATTACHMENT_TYPE = [
     "  size: number;",
     "  /** MIME type. */",
     "  type: string;",
+    "  /** Pixel width — images only. */",
+    "  width?: number;",
+    "  /** Pixel height — images only. */",
+    "  height?: number;",
     "  thumbnails?: {",
     "    small: { url: string; width: number; height: number };",
     "    large: { url: string; width: number; height: number };",

package/dist/esm/sync/lib.test.js

@@ -1,6 +1,6 @@
 import { describe, it, expect } from 'vitest';
 import ts from 'typescript';
-import { generateApiTs, generateBackendWrapperTs, generateDbTs, generateEmailSdk, } from './lib.js';
+import { generateAirtableTs, generateApiTs, generateBackendWrapperTs, generateDbTs, generateEmailSdk, } from './lib.js';
 /**
  * Syntax errors in the emitted source. `.zite/db.ts` sits at the repo root and
  * every app imports it, so anything unparseable here fails typecheck for the
@@ -46,6 +46,39 @@ describe('generateDbTs select option literals', () => {
         expect(out).toContain('"The \\"Premium\\" tier"');
     });
 });
+describe('generateAirtableTs attachment type', () => {
+    const lockWithAttachment = {
+        integrationId: 'airtable',
+        tables: [
+            {
+                id: 'tbl1',
+                sdkName: 'Speakers',
+                primaryFieldId: 'fld1',
+                fields: [
+                    { id: 'fld1', sdkName: 'name', type: 'singleLineText', name: 'Name' },
+                    {
+                        id: 'fld2',
+                        sdkName: 'headshot',
+                        type: 'multipleAttachments',
+                        name: 'Headshot',
+                    },
+                ],
+            },
+        ],
+    };
+    // Reported from a migrated app reading `photo.width` to lay out an image
+    // grid. Airtable returns width/height on image attachments and 1.0 exposed
+    // them; `airtable/lib/attachment.d.ts`, which this type was copied from,
+    // omits both — so the read became a TS2339 the app could not edit away.
+    it.each(['width', 'height'])('exposes %s, which Airtable returns for images', prop => {
+        const out = generateAirtableTs(lockWithAttachment);
+        expect(out).not.toBeNull();
+        expect(out).toContain(`  ${prop}?: number;`);
+    });
+    it('emits parseable TypeScript', () => {
+        expect(syntaxErrorsIn(generateAirtableTs(lockWithAttachment) ?? '')).toEqual([]);
+    });
+});
 describe('generateDbTs field names in comments', () => {
     // A field's display name is user text and reaches a one-line JSDoc. A
     // comment-close sequence in it would end the comment early and leave the

package/dist/esm/sync/sdkNames.d.ts

@@ -36,8 +36,15 @@ export declare function toSdkName(name: string): string;
 /**
  * Accessors `generateDbTs` puts on the `zite` object itself, after the tables.
  * A table that allocates one of these produces a duplicate key.
+ *
+ * `notifications` used to be here and no longer is: it was a platform
+ * primitive hanging off `zite`, so a table named "Notifications" collided with
+ * it and — because the sentinel was written last — lost its client entirely.
+ * Moving it to `zitejs/notifications` removes the collision rather than
+ * managing it, and frees the name for the table that wants it. Everything left
+ * is genuinely backed by the project database.
  */
-export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "notifications", "auth"];
+export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "auth"];
 /**
  * Never safe as a generated key, in any namespace. Assigning `__proto__` in an
  * object literal sets the prototype rather than defining a property, and

package/dist/esm/sync/sdkNames.js

@@ -56,12 +56,15 @@ export function toSdkName(name) {
 /**
  * Accessors `generateDbTs` puts on the `zite` object itself, after the tables.
  * A table that allocates one of these produces a duplicate key.
+ *
+ * `notifications` used to be here and no longer is: it was a platform
+ * primitive hanging off `zite`, so a table named "Notifications" collided with
+ * it and — because the sentinel was written last — lost its client entirely.
+ * Moving it to `zitejs/notifications` removes the collision rather than
+ * managing it, and frees the name for the table that wants it. Everything left
+ * is genuinely backed by the project database.
  */
-export const RESERVED_TABLE_ACCESSORS = [
-    "sql",
-    "notifications",
-    "auth",
-];
+export const RESERVED_TABLE_ACCESSORS = ["sql", "auth"];
 /**
  * Never safe as a generated key, in any namespace. Assigning `__proto__` in an
  * object literal sets the prototype rather than defining a property, and

package/dist/esm/sync/sdkNames.test.js

@@ -31,17 +31,18 @@ const recordTypeKeys = (source, typeName) => {
 };
 describe("reserved platform accessors", () => {
     // Sudzy Dashboard: a table named "Notifications" emitted a second
-    // `notifications:` key, and the platform client — written last — won. The
+    // `notifications:` key and the platform client — written last — won, so the
     // table lost findAll and typed as `{ create(NotificationsCreateParams) }`.
-    it("moves a table off the notifications accessor", () => {
+    // The platform client has since moved to `zitejs/notifications`, so the name
+    // belongs to the table again and there is nothing left to collide with.
+    it("lets a table keep the notifications accessor", () => {
         const schema = generateSchema(database([{ id: "tbl_1", name: "Notifications", fields: [] }]));
-        expect(schema.tables[0].sdkName).toBe("notifications2");
+        expect(schema.tables[0].sdkName).toBe("notifications");
         const keys = ziteKeys(generateDbTs(schema));
-        expect(keys).toContain("notifications2");
         expect(keys.filter((k) => k === "notifications")).toHaveLength(1);
         expect(new Set(keys).size).toBe(keys.length);
     });
-    it.each(["sql", "auth", "notifications"])("keeps the platform %s accessor for the platform", (reserved) => {
+    it.each(["sql", "auth"])("keeps the platform %s accessor for the platform", (reserved) => {
         const schema = generateSchema(database([{ id: "tbl_1", name: reserved, fields: [] }]));
         expect(schema.tables[0].sdkName).toBe(`${reserved}2`);
         const keys = ziteKeys(generateDbTs(schema));
@@ -190,14 +191,17 @@ describe("normalizeSchemaNames", () => {
     // `zitejs generate` reads it with no generateSchema pass in front, so this is
     // the only thing standing between it and a TS1117 it cannot build past.
     it("repairs a committed schema that already holds the collision", () => {
+        // `sql`, not `notifications` — the latter stopped being a platform
+        // accessor when the client moved to `zitejs/notifications`, so a schema
+        // holding it is no longer a collision to repair.
         const source = generateDbTs({
             tables: [
-                { id: "tbl_1", sdkName: "notifications", fields: [] },
+                { id: "tbl_1", sdkName: "sql", fields: [] },
                 { id: "tbl_2", sdkName: "orders", fields: [] },
             ],
         });
         const keys = ziteKeys(source);
         expect(new Set(keys).size).toBe(keys.length);
-        expect(keys).toContain("notifications2");
+        expect(keys).toContain("sql2");
     });
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zitejs",
-  "version": "0.9.108",
+  "version": "0.9.110",
   "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",