@teamscala/service-boot 0.23.345 → 0.23.346

package/src/fn-routers/tasks-router.d.ts

@@ -1,25 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * ORPC procedures for task creation with initial comment.
- * Extracted from @teamscala/orpc/fn-router — primitives tier must not
- * contain application-specific work_items logic.
- */
-import { type Context } from "./auth-router.ts";
-export declare const tasksRouter: {
-    createWithComment: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, import("@orpc/contract").Schema<unknown, unknown>, import("@orpc/contract").Schema<{
-        success: boolean;
-        data: any;
-    }, {
-        success: boolean;
-        data: any;
-    }>, Record<never, never>, Record<never, never>>;
-};

package/src/fn-routers/user-preferences-router.d.ts

@@ -1,77 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * ORPC procedures for a GENERIC per-user preference store backed by the
- * `user_preferences` table. The user is resolved from the ORPC session context
- * (`authed` middleware → `context.user.id`); the client supplies the org + key
- * + value. This is the DB-durable, user-scoped key/value surface any feature
- * can use — the AI browser-control focus (key `ai_ui_focus`) is the first
- * consumer; it is NOT scala-projects-bespoke.
- *
- * Why this exists (over the generated `user_preferences` CRUD): the generated
- * create/update do NOT resolve `user_id` server-side (only `organisation_id`
- * from ctx.orgId), so a client cannot correctly write a per-user row through
- * them. This proc stamps `user_id` from the authenticated caller, making the
- * write safe + per-user. It also emits the `data_change` notify so the
- * realtime surface (regions.watchDataChange) pushes updates to subscribed
- * clients — the cross-region channel for the AI focus (the AiChat panel writes
- * a focus here; the project-list-view in a different region subscribes +
- * reacts, no shared React-context ancestor needed).
- *
- * Ownership is user_id: a caller reads/writes ONLY their own preferences. The
- * org is part of the compound key (per-org isolation) but is client-supplied
- * (the session carries the user, not the active org).
- *
- * DECISION — host-scoping of `user_preferences`: the table is NOT yet a shared
- * `@teamscala/db` model (it lives in scala-projects's schema today), so this proc
- * is genuinely host-scoped: it runs correctly on services whose Prisma client
- * declares `user_preferences` (scala-projects is the first host) + is inert
- * elsewhere. `Context.prisma` is `any`-typed, so the proc COMPILES workspace-
- * wide (no type error on a model a host may not declare) — the `any` is the
- * deliberate seam that lets one generic proc serve hosts incrementally as they
- * adopt the table. Per-user preferences are platform-universal, so the tracked
- * follow-on is to promote `user_preferences` to a shared `@teamscala/db` model
- * (open-migration: `user_preferences→shared-model`, exit: every kind:ui host
- * can mount this proc with no schema precondition) — at which point the proc is
- * universally hostable + the `any` seam can tighten to the shared client. Until
- * then the proc is opt-in per host (declare the table → get the capability).
- */
-import * as v from "valibot";
-import { type Context } from "./auth-router.ts";
-export declare const userPreferencesRouter: {
-    upsert: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, v.ObjectSchema<{
-        readonly organisationId: v.StringSchema<undefined>;
-        /** The preference key (e.g. `ai_ui_focus`). Namespaced by feature. */
-        readonly key: v.StringSchema<undefined>;
-        /** The JSON value. Arbitrary per feature — typed by the caller. */
-        readonly value: v.AnySchema;
-    }, undefined>, import("@orpc/contract").Schema<{
-        success: boolean;
-    }, {
-        success: boolean;
-    }>, Record<never, never>, Record<never, never>>;
-    get: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, v.ObjectSchema<{
-        readonly organisationId: v.StringSchema<undefined>;
-        readonly key: v.StringSchema<undefined>;
-    }, undefined>, import("@orpc/contract").Schema<{
-        value: any;
-        updatedAt: any;
-    }, {
-        value: any;
-        updatedAt: any;
-    }>, Record<never, never>, Record<never, never>>;
-};

package/src/fn-routers/work-items-router.d.ts

@@ -1,102 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * ORPC procedure for safely deleting a work_item (initiative/project/task).
- * Refuses the delete when the row still has child rows (parent_id = id), so a
- * delete can NEVER orphan its descendants — the tree must be emptied bottom-up.
- *
- * Initiatives, projects and tasks are all rows of the ONE `work_items` table
- * discriminated by `kind`, and `parent_id` carries no DB-level foreign key, so
- * a plain `work_items.delete` leaves dangling children with no referential
- * integrity to stop it. This one guard covers every level (you may only delete
- * a leaf — a node with no children), which is exactly the "empty it first"
- * behaviour the board wants.
- */
-import { type Context } from "./auth-router.ts";
-export declare const workItemsRouter: {
-    /**
-     * Fired client-side right after a task's status is set to
-     * "pending_approval" (RaCI: the task's assignee is Responsible; the
-     * project's Accountable person is the approver). Walks parent_id up to
-     * the nearest project-kind ancestor, emails every accountable person on
-     * it. Never throws to the caller — a notification failure must not block
-     * the status change that already committed.
-     */
-    requestApproval: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, import("@orpc/contract").Schema<unknown, unknown>, import("@orpc/contract").Schema<{
-        notified: number;
-    }, {
-        notified: number;
-    }>, Record<never, never>, Record<never, never>>;
-    /**
-     * Fired client-side right after a comment is created, when the comment
-     * text contains an @mention the client already resolved to a team-member
-     * id (client does the name matching against the people list it already
-     * has loaded; this handler only sends). Never throws to the caller for
-     * same reason as requestApproval -- a notification failure must not
-     * surface as a failed comment post.
-     */
-    notifyMentions: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, import("@orpc/contract").Schema<unknown, unknown>, import("@orpc/contract").Schema<{
-        notified: number;
-    }, {
-        notified: number;
-    }>, Record<never, never>, Record<never, never>>;
-    /**
-     * Org-scoped member list for the task-comments panel — @mention matching AND
-     * comment-sender display (name + avatar). ChatPanel.tsx has no
-     * serverLoader/orgId prop (client-only overlay content), so it can't do the
-     * SSR raw-SQL org-scope join load-project-list-view.ts uses; this exposes
-     * the same result via a custom procedure instead of widening service_schema
-     * to the raw better_auth_member table.
-     *
-     * This is the SINGLE source of member display info for the comments panel:
-     * it coalesces BOTH name/email/avatar families on the user model into one
-     * shape (the `full_name`/`primary_email`/`avatar_url` family AND the
-     * better-auth `name`/`email`/`image` family). Returning avatar here lets the
-     * client resolve sender name+avatar from this one list and drop the separate
-     * `user.findMany` enrichment fetch it previously ran as a second waterfall
-     * hop after `comments.findMany` (loading-shape: one wave-parallel hit, not a
-     * dependent client-side round-trip chain).
-     */
-    orgMembers: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, import("@orpc/contract").Schema<unknown, unknown>, import("@orpc/contract").Schema<{
-        id: string;
-        name: string;
-        email: string;
-        avatar: string | null;
-    }[], {
-        id: string;
-        name: string;
-        email: string;
-        avatar: string | null;
-    }[]>, Record<never, never>, Record<never, never>>;
-    deleteEmpty: import("@orpc/server").DecoratedProcedure<import("@orpc/server").MergedInitialContext<Context & Record<never, never>, Context, Context>, import("@orpc/server").MergedCurrentContext<Context, {
-        headers: Headers;
-        resolveUser?: (headers: Headers, prisma: any) => Promise<import("./auth-router.ts").User | null>;
-        prisma: any;
-        user: import("./auth-router.ts").User;
-        orgId: string | null | undefined;
-    }>, import("@orpc/contract").Schema<unknown, unknown>, import("@orpc/contract").Schema<{
-        success: boolean;
-    }, {
-        success: boolean;
-    }>, Record<never, never>, Record<never, never>>;
-};

package/src/gate-ttls.d.ts

@@ -1,6 +0,0 @@
-/** Populate the TTL cache from the registry rows. Idempotent; keeps defaults on
- *  any miss so the gates ALWAYS render (protective-layers-fail-explicitly). */
-export declare function initGateTtls(): Promise<void>;
-export declare function agTtlMs(): number;
-export declare function propTtlMs(): number;
-export declare function gptTtlMs(): number;

package/src/gpt-gate.d.ts

@@ -1,25 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * The PUBLIC GPT identity gate, expressed as config for the content-gate
- * primitive (content-gate/). Unlike proposals/agreements this is NOT access
- * control — every email is a valid visitor (lead capture). Its whole job is to
- * make a returning visitor's identity known AT SSR so the GPT body renders the
- * real conversation on first paint instead of server-rendering the capture gate
- * and then swapping to the chat after hydration (the ssr-then-live-handoff +
- * "know the visitor at SSR first paint" violation: building-applications).
- *
- * Flow: the capture form POSTs {gptId, email} to /api/gpt-access (openCapture →
- * any email matches); the access endpoint sets a signed `gpt_token` cookie. On
- * the next request runContentGate verifies that cookie for this agent and seeds
- * resolved.initialVisitor — which the GPT body serverLoader (ssrGptSession) then
- * uses to SSR-restore the conversation, and GptBodyBlock uses to skip the gate.
- * onUnauthorized is a no-op: an un-gated (first-time) visitor sees the capture
- * form the block renders itself when no visitor is known — that is correct, not
- * a flash (they ARE anonymous), so there is nothing to withhold.
- */
-import type { AccessConfig, ContentGateConfig } from "./content-gate/config-types.ts";
-export declare const gptGateConfig: ContentGateConfig;
-export declare const gptAccessConfig: AccessConfig;

package/src/handlers/bun-stable-watch.d.ts

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

package/src/handlers/pane-outbox-drain.d.ts

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

package/src/handlers/projects-digest.d.ts

@@ -1,26 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * The `projects-daily-digest` / `projects-weekly-digest` pg-boss handlers for
- * scala-projects. Same fixed-query shape as prune-stale-data: no row-driven
- * SQL, every query is a literal Prisma call against work_items; the
- * scheduled_job row only carries the cron.
- *
- * Daily digest: per assignee, tasks assigned to them created in the last 24h.
- * Weekly digest: per assignee, their overdue tasks + tasks due in the next 7
- * days. Both group work_items by assignee_id so one org-wide query covers
- * every member, then send one email per assignee via the
- * projects-daily-digest / projects-weekly-digest email_template rows.
- *
- * Registered under `@teamscala/service-boot:projects-daily-digest` and
- * `@teamscala/service-boot:projects-weekly-digest`.
- */
-import type { ScheduledJobConfig } from "@teamscala/db-validation/registry-schemas/scheduled-job";
-export declare function sendDailyDigest(_ctx: {
-    config: ScheduledJobConfig;
-}): Promise<void>;
-export declare function sendWeeklyDigest(_ctx: {
-    config: ScheduledJobConfig;
-}): Promise<void>;

package/src/handlers/prune-stale-data.d.ts

@@ -1,30 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * The `db-prune-stale-data` pg-boss handler. Reads the `retention` map from the
- * `scheduled_job` row config and prunes stale rows per entry.
- *
- * Writes use Prisma ORM methods (deleteMany/updateMany) via the prisma-registry
- * client — NEVER raw SQL. The `@teamscala/db` client carries the `blockRawSqlWrites`
- * audit extension: `$executeRaw`/`$executeRawUnsafe` are blocked so every write
- * is audited; ORM methods are the canonical audited path.
- *
- * SAFETY — identifier allowlist: each retention key selects a FIXED, hardcoded
- * Prisma model + field (table/field names are literal in code, never derived
- * from the row); the row's value (a duration string) is parsed to a cutoff Date.
- * A row can therefore never inject arbitrary SQL or address an unvetted model.
- * Keys not in the allowlist are skipped + logged.
- *
- * `audit_trail.*` is INTENTIONALLY EXCLUDED: `audit-trail-permanent` (critical)
- * forbids any DELETE FROM audit_trail. The legacy row's
- * `audit_trail.sync_entities: "delete all"` entry is stale drift from before
- * the 2026-06-19 hardening — surfaced (skipped + warned), never executed.
- *
- * Registered under slug `@teamscala/service-boot:prune-stale-data`.
- */
-import type { ScheduledJobConfig } from "@teamscala/db-validation/registry-schemas/scheduled-job";
-export declare function pruneStaleData({ config, }: {
-    config: ScheduledJobConfig;
-}): Promise<void>;

package/src/handlers/registry-stale-inactive-sweep.d.ts

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

package/src/handlers/scala-tools-currency-watch.d.ts

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

package/src/handlers/singleton-tools-currency-watch.d.ts

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

package/src/handlers/sweep-event-log.d.ts

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

package/src/handlers/sweep-host-cache.d.ts

@@ -1,24 +0,0 @@
-/**
- * Expand a path pattern containing single-segment `*` wildcards into concrete
- * paths (files or dirs). Used by `retention_dirs` so a single config key like
-* a pattern like `${WORKSPACE}/<star>/target` reaches every repo's target dir.
-* Sync + bounded: the
- * pattern is shallow (3 segments), and this runs once
- * nightly. Non-existent segments yield no matches (the caller stats each result).
- */
-export declare function expandGlob(pattern: string): string[];
-/**
- * Is `dir` stale — i.e. NO file under it is newer than `cutoffMs`? Walks
- * recursively and SHORT-CIRCUITS the instant it finds a fresh file (so an
- * actively-built target dir returns fast without walking its full tree). On a
- * stale dir the walk is complete and returns the total size + file count, so
- * the caller can report bytes-freed before deleting the dir whole.
- */
-export declare function checkDirStale(dir: string, cutoffMs: number): Promise<{
-    stale: boolean;
-    bytes: number;
-    fileCount: number;
-}>;
-/** Parse the root-fs Use% from `df --output=pcent,target` output (pure, for tests).
- *  Returns null if no root-mount line is found. */
-export declare function parseRootDiskPct(out: string): number | null;

package/src/handlers/upstream-issue-sync.d.ts

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

package/src/handlers/whatsapp-liveness-logic.d.ts

@@ -1,34 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * Pure transition-detection logic for the WhatsApp linked-device liveness monitor
- * (`whatsapp-liveness` handler). Split out from the GOWA-coupled handler so the
- * logic is unit-testable with zero adapter dependencies, and the handler is a thin
- * poll→detect→emit shell. The connection signal is the GOWA device `state` field
- * (`"logged_in"` == connected) — see `whatsapp-remote-logout-monitor`.
- */
-/** GOWA device `state` value meaning the linked phone is connected + authenticated. */
-export declare const GOWA_CONNECTED_STATE = "logged_in";
-export interface WhatsAppDeviceState {
-    id: string;
-    state: string;
-    jid?: string;
-    display_name?: string;
-}
-export interface LivenessTransitions {
-    disconnected: WhatsAppDeviceState[];
-    reconnected: WhatsAppDeviceState[];
-}
-/**
- * Detect connected↔disconnected transitions between the last-known and the freshly
- * observed device states.
- *
- * `prev` is the last-known `state` per device id. A device ABSENT from `prev` is a
- * first sighting: it seeds the baseline and yields NO transition (so the monitor
- * never alerts on a state it never observed the device leave, and a process restart
- * re-baselines without false positives). A device present in `prev` is compared:
- * connected→not is `disconnected`; not→connected is `reconnected`.
- */
-export declare function detectLivenessTransitions(prev: Map<string, string>, curr: WhatsAppDeviceState[]): LivenessTransitions;

package/src/handlers/whatsapp-liveness.d.ts

@@ -1,4 +0,0 @@
-import type { ScheduledJobConfig } from "@teamscala/db-validation/registry-schemas/scheduled-job";
-export declare function pollWhatsAppLiveness({ config: _config, }: {
-    config: ScheduledJobConfig;
-}): Promise<void>;

package/src/hono-error-handler.d.ts

@@ -1,25 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * The single app.onError factory for every Hono app (UI + backend). Two error
- * classes, deliberately separate:
- *  - HTTPException: a DELIBERATE status-bearing throw (e.g. hono bodyLimit's
- *    413). Preserve its status + message verbatim — buildErrorReport only knows
- *    500/503 and would erase a deliberate 413/401/etc.
- *  - anything else: an UNEXPECTED error → buildErrorReport (errorId correlation,
- *    transient-vs-bug classification, 503 + Retry-After when retryable, else 500).
- *
- * Resolves the apparent tension between `hono-global-error-handler` (HTTPException
- * → status + JSON) and `error-responses-via-error-report` (every error response
- * via buildErrorReport): the latter governs UNEXPECTED errors; HTTPException is
- * the documented deliberate-status carve-out. The handler is a consumer of
- * buildErrorReport, never a second classifier for the unexpected branch.
- */
-import type { Context } from "hono";
-/**
- * Returns an `app.onError` handler tagged with `label` (used in the log line so
- * the boot site that surfaced the error is identifiable).
- */
-export declare function createRequestErrorHandler(label: string): (err: unknown, c: Context) => Response;

package/src/install-harness.d.ts

@@ -1,45 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- * @indivisible-unit
- *
- * Install harness — sandbox-mounts each declared package and captures
- * registry.require() calls via AsyncLocalStorage. Validates all required
- * rows exist before returning. Throws HarnessInstallError with full
- * context on failure. Per Constitution Rule 2 step 3.
- *
- * Marked @indivisible-unit: HarnessInstallError is the error class
- * validatePackageDependencies (might) throw — they form one canonical
- * "install harness validation" unit (the validator + the failure-mode
- * class it produces).
- */
-export interface PackageDescriptor {
-    name: string;
-    initPath: string;
-}
-export interface HarnessValidationResult {
-    valid: true;
-    dependencies: Array<{
-        slug: string;
-    }>;
-}
-export interface HarnessValidationError {
-    valid: false;
-    missing: Array<{
-        slug: string;
-        packageName: string;
-    }>;
-}
-export type HarnessOutcome = HarnessValidationResult | HarnessValidationError;
-export declare class HarnessInstallError extends Error {
-    readonly missing: Array<{
-        slug: string;
-        packageName: string;
-    }>;
-    constructor(missing: Array<{
-        slug: string;
-        packageName: string;
-    }>);
-}
-export declare function validatePackageDependencies(packages: PackageDescriptor[], mountFn: (pkg: PackageDescriptor) => Promise<void>): Promise<HarnessOutcome>;

package/src/install-logging.d.ts

@@ -1,34 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- * @indivisible-unit
- *
- * One-call install of the entire logging pipeline. After installLogging()
- * runs, every error in the service — process-level, HTTP middleware, Hono
- * handlers, Puck blocks, even third-party packages calling console.* — is
- * captured by @teamscala/logger and flows to Sentry/GlitchTip (prod) or
- * loga (dev) with full context. Application code never imports the logger
- * or wraps anything in try/catch for telemetry purposes.
- *
- * Marked @indivisible-unit: installLogging (early bootstrap, hardcoded
- * defaults) and applyLoggerConfig (late-stage, DB-driven) are the two
- * phases of the same one-call install — the service boot pipeline calls
- * them in sequence with the same serviceSlug.
- */
-import { attachRequestLogger } from "@teamscala/logger/install-logging";
-export { attachRequestLogger };
-export interface InstallLoggingOptions {
-    serviceSlug: string;
-}
-/** Initial bootstrap install — runs BEFORE DB/Registry are available.
- *  Uses hardcoded defaults (INFO level, /tmp/scala-logs). */
-export declare function installLogging(opts: InstallLoggingOptions): void;
-/** Late-stage configuration — runs AFTER Registry is loaded.
- *  Injects DB-driven settings into the logger primitive. */
-export declare function applyLoggerConfig(config: {
-    minLevel?: "debug" | "info" | "warn" | "error";
-    logDir?: string;
-    maxFileSize?: number;
-    maxFiles?: number;
-}): void;

package/src/load-service-install-row.d.ts

@@ -1,24 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * Loads the service_install registry row for a given service slug.
- * Uses registry.require() per Constitution Rule 11.
- * Schema is owned by @teamscala/db-validation (Rule 7).
- */
-import type { ServiceInstallConfig } from "@teamscala/db-validation/registry-schemas/service-install";
-export { ServiceInstallConfigSchema } from "@teamscala/db-validation/registry-schemas/service-install";
-export type { ServiceInstallConfig };
-export interface LoadServiceInstallRowResult {
-    success: true;
-    config: ServiceInstallConfig;
-}
-export interface LoadServiceInstallRowError {
-    success: false;
-    error: "row_not_found" | "validation_failed";
-    slug: string;
-    message: string;
-}
-export type LoadServiceInstallRowOutcome = LoadServiceInstallRowResult | LoadServiceInstallRowError;
-export declare function loadServiceInstallRow(serviceSlug: string): Promise<LoadServiceInstallRowOutcome>;

package/src/load-service-prisma-client.d.ts

@@ -1,18 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * Loads the service's own generated PrismaClient from
- * <cwd>/prisma/generated/prisma/client.ts. Each service repo generates its own
- * client from its own schema.prisma; resolving a static import would pick up
- * whichever @prisma/generated bun resolves first in a multi-service workspace,
- * which is wrong.
- *
- * No fallback: if the generated client is missing the deploy is broken — fail
- * loud with the remediation step.
- */
-export type ServicePrismaClientConstructor = new (args: {
-    adapter: unknown;
-}) => unknown;
-export declare function loadServicePrismaClient(serviceSlug: string): Promise<ServicePrismaClientConstructor>;

package/src/mount-orpc-router.d.ts

@@ -1,15 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * Mounts the composed ORPC app router (generated Prisma CRUD + custom fn routers)
- * at /api/rpc/* over HTTP via @orpc/server/fetch's RPCHandler.
- * Uses getAppRouter() from @teamscala/orpc/app-router which merges generated
- * routers with custom routers registered via registerCustomRouter().
- */
-import type { Hono } from "hono";
-export interface OrpcMountResult {
-    routeCount: number;
-}
-export declare function mountOrpcRouter(app: Hono, serviceSlug: string): Promise<OrpcMountResult | null>;

package/src/mount-server-packages.d.ts

@@ -1,29 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * Walks `service_install.server_packages[]`, dynamic-imports each, and calls
- * its `mount(ctx)` function. Server packages register handlers / boot hooks /
- * scheduled jobs / WS routes via the MountContext exposed in ctx; the
- * resulting MountRegistry is consumed by register-api-routes /
- * register-ws-routes / run-boot-hook-list / start-scheduled-jobs.
- */
-import type { ServiceInstallConfig } from "@teamscala/db/registry/loader/load-service-install-row";
-import { type MountRegistry } from "@teamscala/os/runtime-contracts/mount-context";
-import type { Hono } from "hono";
-/**
- * Speculatively import every server_package's mount module so Bun compiles
- * the module graphs into its cache NOW, overlapping the (CPU-bound)
- * compilation with whatever I/O the caller runs next. When mountServerPackages
- * later imports the same paths they hit the cache (instant).
- *
- * Same pattern as create-boot-pipeline's speculative preloads — the
- * cross-internet DB I/O in the gate chain (~3.4s) is dead time the compiler
- * can use. Best-effort + non-fatal: a failed import here (wrong candidate
- * path, transient resolution race) is silently swallowed because
- * mountServerPackages will re-attempt with full error surfacing; the preload
- * only warms the cache, never gates boot.
- */
-export declare function preloadServerPackages(packages: string[]): Promise<void>;
-export declare function mountServerPackages(app: Hono, config: ServiceInstallConfig, serviceSlug: string): Promise<MountRegistry>;

package/src/mount.d.ts

@@ -1,9 +0,0 @@
-/**
- * @system server-boot
- * @status handwritten
- * @edit edit directly
- *
- * Server-package mount for opt-in service-boot watchdogs.
- */
-import type { MountContext } from "@teamscala/os/runtime-contracts/mount-context";
-export declare function mount(ctx: MountContext): void;

package/src/mutable-app-ref.d.ts

@@ -1,44 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * Mutable app reference for two-phase boot. Allows swapping the Hono app
- * atomically after building the full app in the background. The initial app
- * is a minimal tool-only surface (ORPC, data routes) that starts serving
- * immediately; the full app (pages, hydration) is built off-to-the-side and
- * swapped in once complete.
- *
- * Thread-safety: Bun is single-threaded, so a simple module-level variable
- * is sufficient. Atomics are not needed.
- */
-import type { Hono } from "hono";
-/**
- * Create a new mutable app reference initialized with the provided app.
- * This should be called once at boot time.
- */
-export declare function initMutableAppRef(initialApp: Hono, label: string): void;
-/**
- * Get the current app. Throws if the ref hasn't been initialized.
- */
-export declare function getApp(): Hono;
-/**
- * Get the current app label for logging.
- */
-export declare function getAppLabel(): string;
-/**
- * Atomically swap the app to a new instance. This is called after the
- * full app is built in the background. Returns the previous label for logging.
- */
-export declare function swapApp(newApp: Hono, newLabel: string): string;
-/**
- * Fetch handler that routes through the mutable app reference.
- * This replaces the direct app.fetch call in the serve layer.
- *
- * Stamps transport-derived identity (x-caller-remote-address/-port + the
- * loopback local-caller comm) via the SAME stampTransportIdentity helper as
- * direct mode, so two-phase-boot (mutable-ref) UI services carry identical
- * identity on every request — closing the gap where the mutable-ref path
- * previously served requests with no transport headers stamped at all.
- */
-export declare function fetchWithMutableApp(req: Request, server: ReturnType<typeof Bun.serve>): Promise<Response>;