/**
 * Fill this app's branding from the first-party template table.
 *
 * Runs after the schema parses, over already-resolved values — it is a pure
 * lookup, not a layer. Reading package.json from disk here is what the earlier
 * version did, and it put a synchronous `fs.readFileSync` inside `getAppConfig()`,
 * which every request path calls. The repo already treats a package.json read as
 * a development-only fallback (`server/cookie-namespace.ts` uses one solely in
 * its non-production branch), so the input here is the declared `packageName`
 * field and its `npm_package_name` alias.
 *
 * Only fills what is still unset, so an explicit `APP_NAME` or a
 * `defineAppConfig()` value always wins.
 *
 * `slug` selects the per-app transactional email sender on agent-native.com, so
 * it is only ever a name the template table already contains — an arbitrary
 * package name cannot mint a mailbox there.
 */
import type { AppConfig } from "./schema.js";
export declare function deriveAppIdentity(app: AppConfig["app"]): AppConfig["app"];
export declare function isFirstPartyApp(app: AppConfig["app"]): boolean;
export declare function resolveAppHomePath(app: AppConfig["app"], workspace?: AppConfig["workspace"]): string;