import type { JsonApiResource, JsonApiResponse } from "../../types.js";
/**
 * The canonical shape of a single entity as this server hands it to the model:
 * the JSON:API resource minus the envelope noise (`links`, `meta`).
 *
 * Extracted from `formatDetailResponse` so the entity resource templates
 * (`boond://candidate/{id}`) aggregate the *same* projection instead of
 * defining a second, drifting idea of what an entity looks like. They cannot
 * reuse `formatDetailResponse` itself: it renders one entity and truncates
 * mid-string at `CHARACTER_LIMIT`, which on pretty-printed JSON yields an
 * unparseable body — acceptable for a tool's text content, not for a resource
 * whose whole point is to be read as JSON.
 */
export declare function projectEntity(entity: JsonApiResource): Pick<JsonApiResource, "id" | "type" | "attributes" | "relationships">;
export declare function formatDetailResponse(response: JsonApiResponse): string;
//# sourceMappingURL=detail.d.ts.map