/**
 * Cross-cut constants for the external task-registration error model.
 *
 * Registration (mirroring an external repo's task suite into Content Lake) can
 * be refused for a handful of caller-actionable reasons. When it is, two server
 * surfaces report the same structured error: the API gateway pre-flight
 * (synchronous, HTTP 422) and the pipeline mirror step (defense-in-depth, a
 * fail-fast abort). Both build that error from the same remediation prose and
 * the same destinations, so the caller sees identical wording wherever the
 * refusal originates.
 *
 * These live in `@sanity/ailf-shared` rather than the dashboard's
 * `sanity-config.ts` because the API gateway must reach them and the gateway
 * depends only on `@sanity/ailf-core` / `@sanity/ailf-shared` (the api-gateway
 * rule). Per the type-architecture rule, cross-cut value constants belong here;
 * per the barrel rule (D0045) they are added with a named re-export, never
 * `export *`.
 *
 * @see packages/core/src/services/resolve-active-team.ts — the error builder
 * @see docs/superpowers/specs/2026-06-15-external-task-registration-design.md (§6)
 * @see docs/decisions/D0055-team-entity-ownership-subscription-split.md
 */
/**
 * The AILF project Slack channel, as a display reference (the `#`-prefixed
 * name). The {@link REGISTRATION_REMEDIATION} prose embeds this literal; a
 * consumer that wants a clickable link uses {@link PRJ_AILF_SLACK_URL}.
 */
export declare const PRJ_AILF_SLACK_CHANNEL = "#prj-ailf";
/**
 * Stable permalink to the {@link PRJ_AILF_SLACK_CHANNEL} archive. The same URL
 * the docs and the `ailf init` next-steps point at, centralized so the
 * registration remediation links to the identical place.
 */
export declare const PRJ_AILF_SLACK_URL = "https://sanity-io.slack.com/archives/C0B0HCVR1T3";
/**
 * Where in the AILF dashboard a caller goes to register or activate their team.
 *
 * A relative destination (the dashboard SPA selects its view from the `view`
 * query param). Consumers compose it with the dashboard origin — which is built
 * at runtime from the org + app id, so it cannot be a literal here. Team
 * affiliation lives in the dashboard's settings view today; team *creation /
 * activation* is presently a Studio operation (D0055), so the actionable path
 * for an external caller is usually {@link PRJ_AILF_SLACK_CHANNEL}. Retarget
 * this single constant if a dedicated dashboard teams view lands.
 */
export declare const DASHBOARD_TEAMS_VIEW_PATH = "?view=settings";
/**
 * Caller-facing remediation for a refused task registration. Fixed prose (the
 * spec's resolved wording): it names the dashboard ({@link
 * DASHBOARD_TEAMS_VIEW_PATH}) and the support channel ({@link
 * PRJ_AILF_SLACK_CHANNEL}). The single source of truth both server surfaces
 * embed, so the gateway 422 and the pipeline abort never diverge.
 */
export declare const REGISTRATION_REMEDIATION = "Register or activate this team in the AILF dashboard, then re-run. Need help? Ask in #prj-ailf.";
