import { Context } from "@deepseek-ai/cordis"; //#region src/app/host/performance-host.d.ts /** Stable Cordis plugin name (the Loader row id in `cordis.patch.yml`). */ declare const name = "pi-tui-performance-host"; /** The projection registry is this plugin's whole purpose: without it the fiber stays pending. */ declare const inject: string[]; /** * The readiness gate this row publishes after the unit is registered. It * carries NO data — it is not a second performance authority, only the * ordering proof that the Host projection exists before the TUI mounts. * * The key is declared the way this repository declares its OWN Cordis * services (`src/startup.ts`'s `TUI_STARTUP_SERVICE`): an exported string * constant, consumed by the dependent row's `inject` list in * `cordis.patch.yml`. The gate is data-free, so there is no value shape to * declare and no `Context` augmentation to add; a consumer that needs to * narrow the read does it at its own call site, exactly as the `tuiStartup` * consumers do. */ declare const PI_TUI_PERFORMANCE_READY_SERVICE = "piTuiPerformanceReady"; /** * Register the `piTuiPerformance` unit and publish the readiness gate. * * The registry is resolved through the context's reflection layer, the * documented Host-plane idiom of this repository (`app/host/pi-tui-host-runtime.ts` * and `app/host/features/file-reference.ts` do the same): this module IS * the Host plane, so its Host-service read is not Client-side coupling and the * client-boundary inventory stays unchanged. `inject` above is what guarantees * the service is present and active here. * * @param ctx - the Host context that owns this row's fiber. */ declare function apply(ctx: Context): void; //#endregion export { PI_TUI_PERFORMANCE_READY_SERVICE, apply, inject, name };