/**
 * `shieldcortex memory <subcommand>` (v4.25.0)
 *
 * Local-only operator commands that read and adjust a single memory row.
 * The plural `memories` namespace at src/index.ts:700 is for the legacy
 * migrate flow — `memory` (singular) is the new operator surface.
 *
 * Subcommands:
 *   shieldcortex memory show <id>
 *   shieldcortex memory downvote <id> [--reason <text>]
 *   shieldcortex memory list [--purpose <X>] [--category <X>] [--limit N]
 *   shieldcortex memory revert-backfill
 *
 * Effective salience is computed via scripts/lib/salience.mjs so this CLI
 * shows the same numbers the recall hook actually ranks by.
 */
import type Database from 'better-sqlite3';
/**
 * Undo the v4.29.0 salience-wall clamp (Task 5).
 *
 * The backfill (src/database/migrations.ts) clamped stale machine-generated
 * `salience > 0.6` rows down to a flat 0.6, after stashing the PRE-clamp
 * salience in the `memories_backfill_backup` table (columns: id, salience,
 * backed_up_at). It is clamp-only, so salience is the ONLY column to restore —
 * the backup carries no category / memory_purpose to put back.
 *
 * This is deliberately STICKY: we do NOT drop `memories_backfill_backup`.
 * That table's existence is also the migration's run-once guard, so keeping it
 * means the next process startup will NOT re-run the clamp and silently undo
 * this revert. To re-enable the backfill, the operator drops the table.
 *
 * Pure + testable: takes the DB handle, returns a summary. No process.exit,
 * no console output — the CLI wrapper owns the user-facing reporting.
 */
export declare function revertBackfill(db: Database.Database): {
    reverted: number;
    hadBackup: boolean;
};
export declare function handleMemoryCommand(args: string[]): Promise<void>;
