import type { FastifyInstance } from "fastify";
/**
 * The Backstage catalog, served rather than generated into a file.
 *
 * `teamapi generate backstage` writes `catalog-info.yaml` files, which is the right answer for an
 * org that wants the catalog in git. It is the wrong answer for the org that already has one,
 * because a generated file is a snapshot: somebody re-runs the command, or they do not, and the
 * catalog is stale from the moment a team document changes until somebody remembers.
 *
 * This is the same generator behind an endpoint, so a Backstage entity provider can poll it and
 * the catalog is never further behind than one refresh interval. Same code, same tests, no second
 * mapping to keep in sync — which is the failure a "live" integration usually introduces.
 */
export declare function backstageRoutes(app: FastifyInstance): Promise<void>;
//# sourceMappingURL=backstage.d.ts.map