/**
 * Whether Settings should expose **product authoring** (Add product, remove
 * custom products, hide built-ins from the switcher).
 *
 * ## Three personas
 *
 * | Persona | Who | Settings Add product |
 * |---------|-----|----------------------|
 * | **Platform creator** | Exxat DS team | DS repo + `exxat-ui add-product` CLI; optional `VITE_EXXAT_PLATFORM_CREATOR=true` in apps/web |
 * | **Builder** | Tenant app author | `<ProductProvider authoring={session.canAuthorProducts}>` in production |
 * | **End user** | Coordinators, students, etc. | `authoring={false}` — see products only |
 *
 * **Resolution order:**
 * 1. **Explicit runtime gate** — `ProductProvider` / `ProductAuthoringProvider` `authoring`
 *    prop, when provided by the caller. This always wins, even in production, so customer
 *    apps can enable "Add product" for their workspace builders by wiring the prop to
 *    real session auth (e.g. `authoring={session.canAuthorProducts}`).
 * 2. **Hard prod floor** — when **no explicit prop** is set: if neither
 *    `import.meta.env.DEV` nor `NODE_ENV=development`, authoring is OFF. This guarantees
 *    the DS Cloudflare / V0 demo deploy keeps the Add product UI hidden even if a CI
 *    build mistakenly sets `VITE_EXXAT_BUILDER_SESSION=true` or similar env vars.
 * 3. Platform creator workspace flag (`VITE_EXXAT_PLATFORM_CREATOR=true`)
 * 4. Build-time override: `VITE_EXXAT_PRODUCT_AUTHORING` / `NEXT_PUBLIC_EXXAT_PRODUCT_AUTHORING`
 * 5. Default: enabled in `pnpm dev`, disabled in production builds
 *
 * In React, prefer {@link useProductAuthoringEnabled} from `@exxatdesignux/ui/components/shell`.
 */
declare function isProductAuthoringEnabled(): boolean;
/**
 * Floor that gates **env-var-driven** product-authoring to development runtimes.
 *
 * Returns `true` only when the bundle is running under `vite` dev
 * (`import.meta.env.DEV === true`) or Node with `NODE_ENV=development`.
 *
 * This floor is intentionally **not** applied when an explicit `authoring` prop is
 * provided via `<ProductProvider>` / `<ProductAuthoringProvider>` — those callers
 * supply the real session decision and must be respected in production.
 *
 * The floor only affects the fallback path (no explicit prop), where the DS demo
 * app on Cloudflare / V0 must not expose authoring UI even if a CI build accidentally
 * includes `VITE_EXXAT_BUILDER_SESSION=true` or similar env vars at build time.
 */
declare function isProductAuthoringRuntimeAllowed(): boolean;

export { isProductAuthoringEnabled, isProductAuthoringRuntimeAllowed };
