/**
 * REST handlers for the local secret store.
 *
 * Contract (shared with the landing frontend):
 *  - `GET  /api/secrets`        → `{ secrets: SecretMeta[] }` — metadata only,
 *                                 values are NEVER returned by anything.
 *  - `POST /api/secrets`        → `{ secret: SecretMeta }` — body
 *                                 `{ name, value }`.
 *  - `DELETE /api/secrets/:name` → `{ ok: true }`.
 *
 * Name normalization/validation and the 64 KiB value cap live in
 * `src/secrets/store.ts`. Errors follow the existing handler error shape
 * (`BadRequestError`/`NotFoundError` → 400/404 in the relay rest loop).
 *
 * SECURITY: no handler here (or anywhere in the relay loop) logs a request or
 * response value. Only names appear in error messages, and only after they
 * have passed `normalizeSecretName` (letters/digits/underscores).
 */
import { type SecretMeta } from "../../secrets/index.js";
/**
 * `GET /api/secrets` — list secrets as metadata only.
 */
export declare function handleListSecrets(): {
    secrets: SecretMeta[];
};
/**
 * `POST /api/secrets` — create or update a secret. Body: `{ name, value }`.
 * Returns the metadata-only view; the stored value is never echoed back.
 */
export declare function handleSetSecret(body: Record<string, unknown>): {
    secret: SecretMeta;
};
/**
 * `DELETE /api/secrets/:name` — delete a secret. Throws `NotFoundError` (404)
 * when the name is not stored.
 */
export declare function handleDeleteSecret(rawName: string): {
    ok: true;
};
//# sourceMappingURL=secrets.d.ts.map