import type { ConfiguredOutlets, FeatureManifest, ModuleConfig, ModuleFeatureManifest, ModuleMeta, OverpanelConfig } from './config';
/**
 * Input shape for module metadata as authored in Antilles or q2 config files.
 * featureName and moduleName are omitted — adaptConfig injects them from the
 * feature/module key names at runtime.
 *
 * @see adaptConfig - Populates featureName and moduleName before platform use
 */
export type ModuleMetaInput = Omit<ModuleMeta, 'featureName' | 'moduleName'> & {
    featureName?: string;
    moduleName?: string;
};
/**
 * Input shape for an overpanel config entry as authored in Antilles or q2 config files.
 * featureName and configuredOutlets are omitted — adaptConfig injects featureName from the
 * feature key name, and configuredOutlets defaults to {}.
 *
 * @see adaptConfig - Populates featureName before platform use
 */
export type OverpanelConfigInput = Omit<OverpanelConfig, 'featureName' | 'configuredOutlets'> & {
    featureName?: string;
    configuredOutlets?: ConfiguredOutlets;
};
/**
 * Dynamic content configuration for a module. Tecton passes this through opaquely —
 * it is consumed by DCM, not by the platform.
 *
 * @see q2-dcm-engine DynamicContentConfig for the authoritative definition
 */
export interface DynamicContentConfigInput {
    type: string;
    name: string;
    description: string;
    height: string;
    [key: string]: unknown;
}
/**
 * Input shape for a module manifest entry as authored in Antilles or q2 config files.
 * routeConfig is omitted — adaptConfig synthesizes it from the feature/module key names.
 * meta uses ModuleMetaInput to reflect the same partial state.
 *
 * @see adaptConfig - Populates routeConfig, meta.featureName, meta.moduleName before platform use
 */
export type ModuleFeatureManifestInput = Omit<ModuleFeatureManifest, 'routeConfig' | 'meta'> & {
    routeConfig?: ModuleConfig;
    meta: ModuleMetaInput;
    dynamicContent?: DynamicContentConfigInput;
};
/**
 * Input shape for a feature manifest as authored in Antilles or q2 config files.
 * Uses input types so that adaptConfig-injected fields are optional.
 *
 * @see adaptConfig - Normalizes this to a full FeatureManifest before platform use
 * @see TectonRuntimeConfig - The fully-adapted runtime shape
 */
export type FeatureManifestInput = Omit<FeatureManifest, 'modules' | 'configuredOverpanels'> & {
    modules: Record<string, ModuleFeatureManifestInput>;
    configuredOverpanels?: Record<string, OverpanelConfigInput>;
};
//# sourceMappingURL=input.d.ts.map