@wtfalch/foundry 0.3.0 → 0.4.0

package/dist/plan/diff.js

@@ -34,10 +34,14 @@ function resourceKey(system, kind, key) {
  * rest: the org's owner, invited by ZITADEL email, idempotent on the
  * *recorded* resource id (`recordedIds`, sourced from
  * `AppliedState.serviceIds`) rather than a live resource, since a human user
- * is never something `live` can contain. Everything else in `live` that none
- * of these twelve singletons and however many declared issuer apps claim is
- * unmanaged. The full field-by-field provisioning surface (SSO, guests,
- * calls, adopted/bespoke apps, the actual
+ * is never something `live` can contain. #128 adds one more singleton, off
+ * by default unlike chat's own: {@link planCalls}, the org's own calls
+ * Matrix stack (`org.ts`'s `CallsConfig.enabled`). #145 adds one more,
+ * planned right after it and gated on the same flag: {@link planCallsService},
+ * the calls service itself (`wtfalch/calls`'s `packages/service`). Everything
+ * else in `live` that none of these fifteen singletons and however many
+ * declared issuer apps claim is unmanaged. The full field-by-field provisioning surface (SSO,
+ * guests, calls on the org's own domain, adopted/bespoke apps, the actual
  * Zitadel/Coolify/Cloudflare/Files/AI/cms shapes) is #20's "provision
  * Company Factory end to end", which wires real readers and executors
  * against this seam.
@@ -58,6 +62,16 @@ export function computePlanDetail(org, live, recordedIds = {}) {
     const chat = planChat(org, byKey, claimed);
     if (chat)
         plannedSteps.push(chat);
+    const calls = planCalls(org, byKey, claimed);
+    if (calls)
+        plannedSteps.push(calls);
+    // Right after the Matrix stack (#145): its own executor
+    // (`executor.ts`'s `coolifyCallsService`) reads the Synapse/MAS addresses
+    // and MAS client credentials `coolifyCalls` just recorded, the same
+    // ordering `planOwner` relies on for `zitadel:issuer`.
+    const callsService = planCallsService(org, byKey, claimed);
+    if (callsService)
+        plannedSteps.push(callsService);
     const filesOrganisation = planFilesOrganisation(org, byKey, claimed);
     if (filesOrganisation)
         plannedSteps.push(filesOrganisation);
@@ -70,6 +84,12 @@ export function computePlanDetail(org, live, recordedIds = {}) {
     const aiBudget = planAiBudget(org, byKey, claimed);
     if (aiBudget)
         plannedSteps.push(aiBudget);
+    // Before `planSite`'s own step (#139): `cmsSite`'s executor reads this
+    // step's recorded client id, the same way `coolifyApp` runs after the
+    // hosted app's own `zitadel:app` steps.
+    const cmsClient = planCmsClient(org, byKey, claimed);
+    if (cmsClient)
+        plannedSteps.push(cmsClient);
     const site = planSite(org, byKey, claimed);
     if (site)
         plannedSteps.push(site);
@@ -335,6 +355,34 @@ function planChat(org, byKey, claimed) {
         },
     };
 }
+/**
+ * The org's own calls Matrix stack (#128) -- a dedicated Synapse and
+ * matrix-authentication-service, entirely separate from chat's
+ * (`plan/calls-matrix.ts`'s own top doc comment: a call guest must never gain
+ * chat membership). Unlike chat, off by default: `org.ts`'s
+ * `CallsConfig.enabled` doc comment. Same on/off, park-not-delete shape as
+ * {@link planApp}/{@link planDatabase}/{@link planTunnel} below
+ * (`planHostingToggle`, #7 corrections 1) -- turning it off parks Synapse and
+ * MAS, never either database (`executor.ts`'s `coolifyCalls`).
+ */
+function planCalls(org, byKey, claimed) {
+    return planHostingToggle('coolify', 'calls', org.calls.enabled, org, byKey, claimed, () => `provision ${org.slug}'s calls Matrix stack (Synapse + matrix-authentication-service)`, () => `park ${org.slug}'s calls Matrix stack (stops serving; data is retained, not deleted -- #7 corrections 1)`);
+}
+/**
+ * The org's own calls service (#145, part 2 of #128) -- `wtfalch/calls`'s
+ * `packages/service`, deployed alongside the calls Matrix stack {@link planCalls}
+ * provisions and wired to it and to the shared LiveKit SFU (foundry#122/#127).
+ * Gated on the same `org.calls.enabled` flag as the Matrix stack, not a flag
+ * of its own: a calls service with no Matrix stack behind it has nothing to
+ * authenticate a guest against, and a Matrix stack alone answers no browser,
+ * so the two are declared as one on/off switch even though they are two
+ * planner steps. Same on/off, park-not-delete shape as {@link planCalls}
+ * (`planHostingToggle`, #7 corrections 1) -- turning it off parks the app,
+ * never its database (`executor.ts`'s `coolifyCallsService`).
+ */
+function planCallsService(org, byKey, claimed) {
+    return planHostingToggle('coolify', 'calls-service', org.calls.enabled, org, byKey, claimed, () => `provision ${org.slug}'s calls service`, () => `park ${org.slug}'s calls service (stops serving; data is retained, not deleted -- #7 corrections 1)`);
+}
 /**
  * Deduped `ai.*` permissions offered to every organisation by default
  * (Decision, this campaign's report): the minimum set that lets an org
@@ -473,6 +521,46 @@ function planAiBudget(org, byKey, claimed) {
         },
     };
 }
+/**
+ * https://github.com/wtfalch/foundry/issues/139 (parent decision:
+ * https://github.com/wtfalch/foundry/issues/99): every site-enabled org gets
+ * one fixed ZITADEL web client named `cms`, so its studio
+ * (`@wtfalch/cms`'s `apps/host`) can sign anyone in -- automatically, with no
+ * new field on `DeclaredOrg`. Modeled on {@link planIssuerApps}'s single-app
+ * shape: provision when missing, recreate when the live `appType` differs,
+ * nothing otherwise. There is no park for this client either, for the same
+ * reason `planIssuerApps`'s own doc comment gives -- ZITADEL has no notion of
+ * a disabled-but-retained OIDC client.
+ */
+function planCmsClient(org, byKey, claimed) {
+    if (!org.site.enabled)
+        return null;
+    const key = resourceKey('zitadel', 'app', 'cms');
+    const live = byKey.get(key);
+    if (live)
+        claimed.add(key);
+    const desired = { appType: 'web' };
+    if (!live) {
+        return {
+            action: { system: 'zitadel', kind: 'app', key: 'cms', desired },
+            step: {
+                description: `provision the web ZITADEL app 'cms' for ${org.slug}'s cms studio sign-in`,
+                destroys: false,
+                migrates: false,
+            },
+        };
+    }
+    if (live.config.appType === 'web')
+        return null;
+    return {
+        action: { system: 'zitadel', kind: 'app', key: 'cms', desired },
+        step: {
+            description: `recreate ZITADEL app 'cms' for ${org.slug} as web (was ${String(live.config.appType)})`,
+            destroys: true,
+            migrates: false,
+        },
+    };
+}
 /**
  * The org's cms site (`org.ts`'s `SiteConfig`), a per-org singleton
  * resource modeled on {@link planMail}. Disabling a live site parks it,
@@ -643,10 +731,16 @@ function planDatabase(org, byKey, claimed) {
  * (`executor.ts`'s `tunnelIngressHostnames`) -- there is no separate
  * `site.tunnel` toggle to gate on the way `hosting.tunnel` does, since a site
  * has no meaning without one.
+ *
+ * #145: an own-domain calls service (`org.ts`'s `CallsConfig.usesDomain`)
+ * needs a tunnel too, for the same reason a site does -- an org that wants
+ * `calls.<domain>` but declares no other own-domain feature must still get
+ * one provisioned, not silently have nowhere for that hostname to route.
  */
 function planTunnel(org, byKey, claimed) {
     const desired = (org.hosting.tunnel && org.hosting.usesDomain && Boolean(org.domain)) ||
-        (org.site.enabled && Boolean(org.domain));
+        (org.site.enabled && Boolean(org.domain)) ||
+        (org.calls.enabled && org.calls.usesDomain && Boolean(org.domain));
     return planHostingToggle('cloudflare', 'tunnel', desired, org, byKey, claimed, () => `provision a Cloudflare tunnel for ${org.slug}'s app`, () => `park ${org.slug}'s Cloudflare tunnel (configuration is retained, not deleted -- #7 corrections 1)`);
 }
 /**
@@ -664,9 +758,14 @@ function planTunnel(org, byKey, claimed) {
  * though it can never have `hosting` on at the same time (`validateSite`) --
  * `org.site.enabled` already guarantees both `domain` and `site.usesDomain`
  * are set, so the `org.domain` check below still covers it.
+ *
+ * #145: an own-domain calls service (`org.ts`'s `CallsConfig.usesDomain`)
+ * needs a zone for the same reason, whether or not the org also has hosting
+ * or a site on its domain.
  */
 function planZone(org, byKey, claimed) {
-    if (!(org.hosting.usesDomain || org.site.enabled) || !org.domain)
+    const usesDomain = org.hosting.usesDomain || org.site.enabled || (org.calls.enabled && org.calls.usesDomain);
+    if (!usesDomain || !org.domain)
         return null;
     const key = resourceKey('cloudflare', 'zone', org.domain);
     const live = byKey.get(key);

package/dist/plan/executor.d.ts

@@ -1,5 +1,6 @@
 import type { OrgMailOptions, OrgMailOrg, OrgMailResult } from '@wtfalch/email/postmaster';
 import type { DeclaredOrg, HostingBuildPack, OrgId } from '../org.js';
+import type { DeclaredOrgStore } from '../store.js';
 import type { StepAction } from './diff.js';
 import type { DestroyTarget, StepDestroyer, StepExecutionContext, StepExecutor } from './plan-apply.js';
 /**
@@ -104,6 +105,7 @@ export interface CoolifyPort {
         name: string;
         postgres_db: string;
         postgres_user: string;
+        postgres_initdb_args?: string;
     }): Promise<{
         uuid: string;
         internal_db_url: string;
@@ -199,6 +201,74 @@ export interface CoolifyPort {
     deleteApplication(uuid: string): Promise<unknown>;
     /** `FoundryPlanApply.destroy`'s teardown of the org's own database. */
     deleteDatabase(uuid: string): Promise<unknown>;
+    /**
+     * An application that runs a published image as-is (#128, `coolifyCalls`'s
+     * own Postgres) — matches `@wtfalch/providers`' `CoolifyClient.
+     * createDockerImageApplication` method-for-method.
+     */
+    createDockerImageApplication(input: {
+        project_uuid: string;
+        server_uuid: string;
+        environment_name: string;
+        environment_uuid: string;
+        docker_registry_image_name: string;
+        docker_registry_image_tag: string;
+        ports_exposes: string;
+        name?: string;
+        description?: string;
+        instant_deploy?: boolean;
+    }): Promise<{
+        uuid: string;
+    }>;
+    /**
+     * An application built from an inline Dockerfile (#128, `coolifyCalls`'s own
+     * Synapse and MAS — neither's published image takes the module/command this
+     * stack needs from a plain image application) — matches `CoolifyClient.
+     * createDockerfileApplication` method-for-method.
+     */
+    createDockerfileApplication(input: {
+        project_uuid: string;
+        server_uuid: string;
+        environment_name: string;
+        environment_uuid: string;
+        dockerfile: string;
+        name?: string;
+        description?: string;
+        instant_deploy?: boolean;
+    }): Promise<{
+        uuid: string;
+    }>;
+    /**
+     * A single file mounted into the container (#128) — how `homeserver.yaml`
+     * and MAS's `config.yaml` reach a Docker-image application with no git
+     * repository of its own to carry them. Matches `CoolifyClient.
+     * createFileStorage` method-for-method.
+     */
+    createFileStorage(applicationUuid: string, input: {
+        mount_path: string;
+        content: string;
+    }): Promise<unknown>;
+    /** Updates an existing file storage's content in place. Matches `CoolifyClient.updateFileStorage`. */
+    updateFileStorage(applicationUuid: string, storageUuid: string, content: string): Promise<unknown>;
+    /**
+     * A generic application PATCH (#128) — `coolifyCalls` uses this to give
+     * Postgres/Synapse/MAS a fixed `custom_internal_name` so the other two can
+     * address each other by a name that never changes across a re-run, instead
+     * of guessing at Coolify's own container-naming scheme. Matches
+     * `CoolifyClient.updateApplication` method-for-method.
+     */
+    updateApplication(uuid: string, patch: Record<string, unknown>): Promise<unknown>;
+    /**
+     * Queues a deployment (#128) — `coolifyCalls` calls this after writing a
+     * fresh Synapse/MAS config file, since a file-storage write alone does not
+     * reach the running container until its next deploy (issue #128's "a
+     * running app is redeployed when its config changed"). Fire-and-forget,
+     * like `restart` above: this executor does not poll a deployment to
+     * completion anywhere else, and `coolifyCalls` only calls this when the
+     * config it just wrote was actually freshly minted. Matches `CoolifyClient.
+     * deploy` method-for-method.
+     */
+    deploy(uuid: string, force?: boolean): Promise<unknown>;
 }
 /**
  * The Cloudflare calls this executor makes, shaped to match
@@ -300,6 +370,85 @@ export interface CloudflarePort {
      */
     request<T>(method: string, path: string, body?: unknown, missingOkay?: boolean): Promise<T>;
 }
+/**
+ * One DNS record a Resend domain's own response names it must publish --
+ * `record` is Resend's own label (`SPF`, `DKIM`, `DMARC`, `MX`), which
+ * {@link ResendPort.createDomain}/{@link ResendPort.getDomain} return
+ * alongside `type`/`name`/`value` for `coolifyMail` to act on, the same shape
+ * https://resend.com/docs/api-reference/domains/create-domain documents.
+ */
+export interface ResendDnsRecordSpec {
+    readonly record: 'SPF' | 'DKIM' | 'DMARC' | 'MX' | string;
+    readonly name: string;
+    readonly type: 'TXT' | 'CNAME' | 'MX';
+    readonly value: string;
+    readonly priority?: number;
+}
+export interface ResendDomain {
+    readonly id: string;
+    readonly name: string;
+    readonly status: string;
+    readonly records?: readonly ResendDnsRecordSpec[];
+}
+/**
+ * The Resend calls this executor makes to verify an org's mail domain (#138)
+ * and mint its app's sending key (#140 rework) -- the shared Stalwart relays
+ * every outbound message through Resend
+ * (https://github.com/wtfalch/email/blob/main/packages/email/src/postmaster/objects.ts#L149-L168),
+ * which refuses mail from a domain Resend has not verified. `@wtfalch/providers`
+ * has no Resend client yet, unlike Coolify/Cloudflare/ZITADEL above, so this
+ * port names Resend's own REST shapes directly
+ * (https://resend.com/docs/api-reference/domains/create-domain,
+ * https://resend.com/docs/api-reference/api-keys/create-api-key,
+ * https://resend.com/docs/api-reference/api-keys/list-api-keys,
+ * https://resend.com/docs/api-reference/api-keys/delete-api-key) -- the same
+ * prior art `wtfalch/app-template`'s `bootstrap/steps/resend-email.ts` already
+ * proved against a live account. The relay's own `<slug>-relay` key
+ * (`.plans/2026-09-27-org-mail-resend-design.md`) is a separate change, filed
+ * as https://github.com/wtfalch/foundry/issues/149 and out of scope here.
+ */
+export interface ResendPort {
+    /** An exact name match, never a listing scan `coolifyMail` has to page itself. */
+    findDomain(name: string): Promise<{
+        id: string;
+        name: string;
+        status: string;
+    } | undefined>;
+    createDomain(name: string): Promise<ResendDomain>;
+    /** Re-reads a domain already found by {@link findDomain}, for its current status and DNS records. */
+    getDomain(id: string): Promise<ResendDomain>;
+    /**
+     * Asks Resend to re-check DNS now. `coolifyMail` never polls or waits on
+     * this -- the task brief: "do not block the plan on DNS propagation:
+     * record the status, and let the next apply re-check it (idempotent, like
+     * `applyOrgMail`)".
+     */
+    verifyDomain(id: string): Promise<{
+        status: string;
+    }>;
+    /**
+     * Every key in the account, `id`+`name` only -- Resend never returns a
+     * key's token except at creation, so this is how the mint rule
+     * (`.plans/2026-09-27-org-mail-resend-design.md` "One rule for minting")
+     * tells whether the app's key is healthy before deciding to mint. `ensureAppResendKey`'s own doc comment below
+     * spells the rule out.
+     */
+    listApiKeys(): Promise<Array<{
+        id: string;
+        name: string;
+    }>>;
+    /** Sending-only, scoped to one domain -- the app step's `<slug>-app@<domainId>` (`ensureAppResendKey`), minted under the mint rule. */
+    createApiKey(input: {
+        name: string;
+        permission: 'sending_access';
+        domainId: string;
+    }): Promise<{
+        id: string;
+        token: string;
+    }>;
+    /** Deletes one key by id -- the mint rule's own cleanup of an orphan, a duplicate, or a key for a mail domain the org no longer uses. */
+    deleteApiKey(id: string): Promise<void>;
+}
 /**
  * The Stalwart calls this executor makes for one org's mail, shaped to match
  * `@wtfalch/email/postmaster`'s `applyOrgMail`/`parkOrgMail` method-for-method
@@ -310,6 +459,24 @@ export interface MailPort {
     applyOrgMail(org: OrgMailOrg, options: OrgMailOptions): Promise<OrgMailResult>;
     parkOrgMail(org: OrgMailOrg, options: OrgMailOptions): Promise<void>;
 }
+/**
+ * The shared calls SFU's own LiveKit API credentials (#122, #127), resolved
+ * by the host from wherever `scripts/calls-sfu-deploy.mjs`'s own
+ * `CallsSfuConfig` delivered them (#145) -- this package never mints or
+ * invents a LiveKit key/secret pair itself, the same "the executor is
+ * constructed with narrow ports ... a host [archon] supplies real clients"
+ * rule this file's own top doc comment states for every provider credential.
+ * `resolveCredentials` returns `null` when the SFU has not been configured
+ * yet, the same "nothing recorded" signal a bare `CoolifyPort.listEnvs` gives
+ * `ensureCallsMatrixSecrets` -- just for a secret this package never held in
+ * the first place, so there is nowhere here to read it back from itself.
+ */
+export interface CallsSfuPort {
+    resolveCredentials(): Promise<{
+        apiKey: string;
+        apiSecret: string;
+    } | null>;
+}
 /**
  * The ZITADEL calls this executor makes. `findOrCreateOrg`/`findOrCreateProject`
  * already exist on `@wtfalch/providers/zitadel`'s `ZitadelClient` (returning
@@ -359,6 +526,23 @@ export interface ZitadelPort {
         clientSecret: string;
     }>;
     deleteApp(orgId: string, projectId: string, appId: string): Promise<void>;
+    /**
+     * `zitadelApp`'s kind-change path reads this to find an app a prior,
+     * lost-response create already made under the new name, before calling
+     * `createOidcApp`/`createApiApp` again and orphaning that one under the
+     * same name. Matches `@wtfalch/providers/zitadel`'s `ZitadelClient.
+     * listApps` return shape exactly, so that client satisfies this port with
+     * no adapter -- it does not carry `clientId`/`clientSecret` (that provider
+     * method never parses either, and a secret is minted once, on creation,
+     * never handed back again), which is why the reuse path below cannot
+     * re-deliver either one.
+     */
+    listApps(orgId: string, projectId: string): Promise<Array<{
+        id: string;
+        name: string;
+        appType: 'web' | 'native' | 'api';
+        state: string;
+    }>>;
     /**
      * The org-owner flow (goal line): find-or-create the human user by email in
      * the org, then have ZITADEL email them an invite to set up a passkey.
@@ -486,6 +670,9 @@ export interface FoundryStepExecutorPorts {
     cloudflare: CloudflarePort;
     zitadel: ZitadelPort;
     mail: MailPort;
+    resend: ResendPort;
+    /** The shared calls SFU's own LiveKit credentials (#145) -- see {@link CallsSfuPort}'s own doc comment. */
+    callsSfu: CallsSfuPort;
     /** A factory, not a flat client: Files/AI are org-scoped credentials the host resolves per org. */
     filesLimitsFor: (orgId: OrgId) => FilesOrgLimits;
     aiLimitsFor: (orgId: OrgId) => AiOrgLimits;
@@ -506,6 +693,14 @@ export interface FoundryStepExecutorPorts {
      * themselves.
      */
     deliverSecret(ref: string, secret: string): Promise<void>;
+    /**
+     * Read access to the declared-org store, narrowed to the one query
+     * `cloudflareZone` needs for its cross-org refusal check (#131) -- see that
+     * method's own doc comment for why a zone needs this where
+     * `cloudflareAccess` reads Cloudflare's own live state instead. A real host
+     * passes the same store instance it constructs `FoundryPlanApply` with.
+     */
+    declaredOrgStore: Pick<DeclaredOrgStore, 'findOrgIdForZone'>;
 }
 /**
  * Thrown by name for a step this executor deliberately does not implement:
@@ -581,6 +776,16 @@ export declare class FoundryStepExecutor implements StepExecutor, StepDestroyer
      */
     private zitadelCustomers;
     private zitadelApp;
+    /**
+     * The app an earlier attempt's recreate already made under the same
+     * name, whose response this executor never saw -- deleted before the
+     * create so no duplicate is left behind. Matches on name and the
+     * desired kind, and skips a removed app -- ZITADEL's
+     * search can return one that has since been deleted (`isNotFoundError`'s
+     * own doc comment covers why a delete can be retried into a 404), and
+     * that is not the survivor this is looking for.
+     */
+    private findRecreatedApp;
     private ensureZitadelProject;
     private ensureCoolifyProject;
     private resolveServer;
@@ -657,6 +862,41 @@ export declare class FoundryStepExecutor implements StepExecutor, StepDestroyer
      * upsert a fresh value over it.
      */
     private ensureAuthCookieSecret;
+    /**
+     * #140 rework: the hosted app's own Resend sending key, pushed as
+     * `RESEND_API_KEY` straight into the app's env, the one place its token
+     * ever lives (Resend shows a key's token once, at creation). A no-op until
+     * `coolify:mail` has recorded a {@link RESEND_DOMAIN_ID_SCOPE_KEY} for this
+     * org; the next apply fills it in once `coolify:mail` runs first
+     * (`diff.ts`'s `computePlanDetail` order).
+     *
+     * The key is named `<slug>-app@<resendDomainId>`, so a key limited to a
+     * mail domain the org no longer uses (a `usesDomain` flip moves it between
+     * `org.domain` and `<slug>.<apex>`) never passes for the current one.
+     * `RESEND_API_KEY_ID` sits beside the token in the env -- an id, not a
+     * secret -- so the env can say which key its token belongs to.
+     *
+     * The mint rule (`.plans/2026-09-27-org-mail-resend-design.md` "One rule
+     * for minting"): healthy when the env holds a token and its
+     * `RESEND_API_KEY_ID` is the one key Resend lists under the current name.
+     * Otherwise one fresh key is minted and written to the env first, and only
+     * then is every other `<slug>-app@` key deleted -- a lost mint response, a
+     * duplicate, a hand-made key, and a previous domain's key all end the same
+     * way. An app that was already running is restarted before that delete,
+     * since a container reads its env only at start (`running`, the same
+     * reason {@link ensureLogVolume} restarts one). The restart is not
+     * awaited to completion, so the old container can briefly outlive its key.
+     *
+     * `MAIL_FROM` is upserted every time: it depends only on the mail domain
+     * `coolify:mail` resolved (`RESEND_MAIL_DOMAIN_SCOPE_KEY`).
+     *
+     * The token goes straight to `bulkUpsertEnvs` and nowhere else: never
+     * returned, never recorded in `serviceIds` (`recordScopeId`'s own doc
+     * comment), never logged, never interpolated into a thrown error -- the
+     * same discipline `pushDatabaseUrl`'s doc comment states for a database's
+     * own connection string.
+     */
+    private ensureAppResendKey;
     /**
      * `plan/diff.ts`'s `planSite` (#116, slicing #99's "provision the cms app,
      * database and site app per org"): the 2026-09-25 decision
@@ -774,13 +1014,118 @@ export declare class FoundryStepExecutor implements StepExecutor, StepDestroyer
      * this method is `cmsSite`'s only caller.
      */
     private findOrCreateCmsApp;
+    /**
+     * `plan/diff.ts`'s `planCalls`: the org's own calls Matrix stack, entirely
+     * separate from chat's (`calls-matrix.ts`'s own top doc comment) -- two
+     * Coolify-managed Postgres databases, a Synapse app and an MAS app, no
+     * public hostname of its own (neither app is reachable from outside
+     * Coolify's own Docker network) -- `coolifyCallsService` below (#145, part 2
+     * of #128) is the one that gets a public hostname, since it is the one a
+     * browser actually talks to. Park stops Synapse and MAS only, the same
+     * park-not-delete rule `coolifyApp`/`cmsSite` already follow (#7
+     * corrections 1) -- their databases are never touched from that branch, the
+     * same way `cmsSite`'s own database never is.
+     */
+    private coolifyCalls;
+    /**
+     * `coolifyCalls`'s own find-or-create for Synapse/MAS, restarting a
+     * found-but-stopped app (#116 review round 3, Finding 1's same fix). Reused
+     * by `coolifyCallsService` (#145) for the calls service app itself -- the
+     * same find-by-name-then-start-or-create shape applies unchanged.
+     */
+    private findOrCreateCallsApp;
+    /**
+     * `coolifyCalls`'s own database find-or-create, modeled on
+     * `ensureCmsDatabase`: `context.recordedIds()` is checked first since
+     * neither database has a `system:kind:key` slot of its own (this step's one
+     * auto-recorded `resourceId` is the MAS app, not either database --
+     * {@link CALLS_SYNAPSE_SCOPE_KEY}'s own doc comment), then `listDatabases`
+     * finds one already created by name before `createPostgresDatabase` makes
+     * one. Reused by `coolifyCallsService` (#145) for the calls service's own
+     * database, whose {@link CALLS_SERVICE_DB_SCOPE_KEY} has no
+     * `system:kind:key` slot of its own for the same reason.
+     */
+    private ensureCallsDatabase;
+    /**
+     * Reads back {@link CALLS_SECRET_ENV_KEYS} from the MAS app's own envs
+     * before minting fresh ones -- this stack's only memory across a re-run
+     * (`calls-matrix.ts`'s `CallsMatrixSecrets` doc comment). `changed: true`
+     * only when nothing usable was found: a partial set (a crash mid-mint) is
+     * still treated as "mint fresh", since MAS's shared secret and Synapse's
+     * copy of it must always agree.
+     */
+    private ensureCallsMatrixSecrets;
+    /**
+     * Upserts a file storage's content, creating it if the application has none
+     * at that mount path yet -- there is no way to read a file storage's
+     * current content back from Coolify to diff it, the same limit
+     * `archon/bootstrap/steps/chat-instance.ts`'s own `ensureFileStorage` notes,
+     * so an existing one is always re-written.
+     */
+    private ensureCallsFileStorage;
+    /**
+     * `plan/diff.ts`'s `planCallsService`: the org's own calls service --
+     * `wtfalch/calls`'s `packages/service`, wired to the calls Matrix stack
+     * {@link coolifyCalls} provisions and the shared LiveKit SFU (#122/#127).
+     * Static config checks run first, before any Coolify call (#128's own
+     * carried-over PR 344 review fix, restated in #145's own issue body): the
+     * calls Matrix stack must already be recorded, its MAS app must already
+     * carry its client id/secret, and the shared SFU's LiveKit credentials must
+     * already be resolvable -- none of the three is minted or guessed here.
+     * Park stops the app only, the same park-not-delete rule
+     * {@link coolifyCalls}/{@link coolifyApp} already follow (#7 corrections
+     * 1); its own database is never touched from that branch.
+     */
+    private coolifyCallsService;
+    /**
+     * Reads back the calls Matrix stack's MAS client id/secret from the MAS
+     * app's own envs ({@link CALLS_SECRET_ENV_KEYS}) -- never mints: minting
+     * either is {@link ensureCallsMatrixSecrets}'s own job, and a missing value
+     * here means that stack has not finished provisioning yet, not something
+     * this step can fix on its own.
+     */
+    private readCallsMasClientCredentials;
+    /**
+     * `null` once the calls service app already has a `CALLS_BINDING_SECRET` --
+     * never rotated, the same rule {@link ensureAuthCookieSecret} follows for
+     * `AUTH_COOKIE_SECRET`: it wraps the provider-token ciphertext already
+     * stored under any binding minted so far
+     * (`calls/packages/service/src/config.mjs`'s own doc comment on
+     * `CALLS_BINDING_SECRET`), so overwriting it would strand every binding
+     * minted under the old value. 32 raw bytes, hex-encoded -- the exact shape
+     * `config.mjs`'s own regex requires.
+     */
+    private ensureCallsBindingSecret;
     private cloudflareTunnel;
+    /**
+     * `plan/diff.ts`'s `planZone`: finds or creates the Cloudflare zone for the
+     * org's own domain. Refuses to adopt a zone the store already records
+     * under a *different* org's applied state (#131), the same
+     * do-not-adopt-a-foreign-resource rule `cloudflareAccess` above enforces --
+     * but where that method tells "foundry's own" from "foreign" by reading
+     * Cloudflare's own Access-app name live, a Cloudflare zone carries no
+     * org-identifying field of its own, so this asks the store instead. That
+     * matters because two different, DB-unique `domain` values (`org.ts`'s
+     * `validateDomain` plus its unique index) can still resolve to the same
+     * Cloudflare zone -- a zone is keyed by apex, and one org's domain can be a
+     * subdomain of another org's -- which is exactly the shared-zone,
+     * shared-hostname collision this ticket exists to refuse. An org re-running
+     * its own already-recorded zone is unaffected: the store then names this
+     * same org as the owner.
+     */
     private cloudflareZone;
     /**
      * `plan/diff.ts`'s `planMail`: gives an org mail, moves it between modes,
      * or parks it on the one shared Stalwart instance (`this.ports.mail`,
      * `@wtfalch/email/postmaster`'s `applyOrgMail`/`parkOrgMail` bound), then
-     * publishes whatever DNS records the call returns.
+     * publishes whatever DNS records the call returns, then registers the same
+     * mail domain with Resend (#138) -- the shared Stalwart relays every
+     * outbound message through Resend, and Resend refuses mail from a domain
+     * it has not verified. No step here ever deletes the app's Resend key:
+     * `diff.ts`'s `planMail` plans nothing for mode `'off'`, so turning mail
+     * off leaves the key live, like every other resource foundry stops
+     * managing (#10). Switching the mail domain replaces the key instead
+     * (`ensureAppResendKey`).
      */
     private coolifyMail;
     /**
@@ -788,9 +1133,52 @@ export declare class FoundryStepExecutor implements StepExecutor, StepDestroyer
      * by an exact name+type match (`CloudflarePort.findDnsRecord`'s own doc
      * comment) so update never mistakes a stale record of a different type for
      * a match. A `DKIM` record can be absent on the first call, since Stalwart
-     * mints the key on a background task; the next apply publishes it.
+     * mints the key on a background task; the next apply publishes it. Returns
+     * the zone id so `registerResendDomain` publishes Resend's own records on
+     * the same zone without a second lookup.
      */
     private publishMailDnsRecords;
+    /**
+     * #138: registers `domain` with Resend -- the custom domain, or
+     * `<slug>.<apex>` for a level-1 org, exactly what `publishMailDnsRecords`
+     * just published the Stalwart records for. Idempotent by name, the same way
+     * `applyOrgMail` itself is: found by `findDomain` rather than any id this
+     * class recorded, so a crash between here and the next apply just repeats
+     * the same find-or-create. Never blocks on DNS propagation (task brief):
+     * `verifyDomain` asks Resend to re-check once, and its returned status is
+     * neither polled nor awaited -- an unverified domain here is exactly what
+     * the next apply corrects.
+     *
+     * #140 rework: mints no key of its own any more. It records the domain's
+     * own id and the resolved mail domain as scope ids so `ensureAppResendKey`
+     * (`coolifyApp`) can mint the app's own `<slug>-app@<domainId>` key once the app
+     * exists, without this step or the app step calling Resend to look the
+     * domain back up.
+     */
+    private registerResendDomain;
+    /**
+     * Upserts each DNS record Resend's domain names, the same find-then-upsert
+     * `publishMailDnsRecords` above uses for Stalwart's own records -- except
+     * SPF is merged into whatever record that call just published rather than
+     * created a second time (RFC 7208 treats two `v=spf1` TXT records on one
+     * name as a permerror and silently breaks SPF for every sender on the
+     * domain), and an existing `_dmarc` record is never overwritten. Prior art:
+     * `wtfalch/app-template`'s `bootstrap/steps/resend-email.ts`.
+     */
+    private publishResendDnsRecords;
+    /**
+     * Inserts Resend's `include:` token into whatever SPF record
+     * `publishMailDnsRecords` already published for this name, instead of
+     * creating a second `v=spf1` TXT record -- the classic foot-gun that makes
+     * every receiver treat SPF as a permerror and skip it entirely.
+     */
+    private mergeResendSpfRecord;
+    /**
+     * Never overwrites an existing `_dmarc` record -- a stricter policy an org
+     * already set (`p=quarantine`/`p=reject`) should not be relaxed back to
+     * Resend's own `p=none` default.
+     */
+    private ensureResendDmarcRecord;
     /**
      * #80: provisions the org's own organisation on Files, before
      * {@link filesStorage} can set its spend limit. `provisionOrganisation` is