/**
 * The package-smoke roster (relocated from `scripts/package-smoke.ts`, CUT A5).
 * Pure data — no Node edge — so it can be projected by the meta-test
 * (`tests/unit/devops/package-smoke-roster.test.ts`) AND consumed by the CLI-only
 * smoke engine (`runPackageSmokeScan` in `@czap/cli`) without either reaching into
 * a self-executing script.
 *
 * `PACKAGES` mirrors every publishable `@czap/*` scope under `packages/*` (see
 * `pnpm-workspace.yaml`); `imports` is the set of module specifiers the
 * import-smoke resolves for that package. `PEER_INSTALLS` is the external peer
 * set the consumer fixture installs alongside the packed tarballs. The B6a guard
 * derives the publishable set from the manifests on disk and asserts this roster
 * covers exactly that set — so the release gate can never silently skip a
 * newly-published package.
 *
 * @module
 */
/** One publishable scope: its `packages/<dir>`, its package name, and the module specifiers the import-smoke resolves. */
export interface PackageSmokeSpec {
    readonly dir: string;
    readonly name: string;
    readonly imports: readonly string[];
}
/** Mirrors every publishable `@czap/*` scope under `packages/*` (see `pnpm-workspace.yaml`). */
export declare const PACKAGES: readonly PackageSmokeSpec[];
/** External peer set the consumer fixture installs alongside the packed `@czap/*` tarballs. */
export declare const PEER_INSTALLS: readonly string[];
//# sourceMappingURL=package-smoke-registry.d.ts.map