/**
 * dsh-ui-tweaks — server half.
 *
 * Owns the `ui-tweaks` settings namespace so users can tune the conversation
 * UI either from the Settings panel or by editing the profile patch
 * (`cordis.patch.yml` `ui-tweaks` entry; settings.yaml was retired in DSH
 * 0.1.7, which migrated its sections there). Since 0.1.7 the Settings panel
 * derives each form from the plugin's exported `Config` schema — there is no
 * explicit `settings.register()` anymore — so this module re-exports
 * `Config` and opts out of the auto-generated form page (the browser half
 * owns its sections through the `settings.section` slot). All rendering work
 * happens in the browser bundle (`src/client`), which reads and writes this
 * namespace through the same-origin route mounted here — the Web settings RPC
 * only exposes a fixed allowlist of namespaces since rc.6, so a custom route
 * is the supported way for a plugin to own a configuration page.
 * @module dsh-ui-tweaks
 */
import type { Context } from '@deepseek-ai/cordis';
import { Config } from './config.ts';
export declare const name = "dsh-ui-tweaks";
/**
 * Re-export the Config schema so the Cordis loader attaches it to this
 * plugin's runtime: since DSH 0.1.7 `SettingsForms` reads
 * `entry.fiber.runtime.Config` to derive the settings form (the old
 * `ctx.settings.register()` call no longer exists).
 */
export { Config };
/** Required services: the settings seam is the whole server-side surface. */
export declare const inject: string[];
export declare function apply(ctx: Context): void;
//# sourceMappingURL=index.d.ts.map