/**
 * The `flow(journal_*)` actions: writing and reading the workflow journal.
 *
 * Why these live on the flow tool rather than in a category of their own: a
 * flow is the forward half of a repeatable operation and the journal is the
 * record it leaves, so the two are one subject. `flow(action="run")` opens and
 * closes a journal run by itself, and these actions are what an agent uses for
 * the work it did NOT wrap in a flow, plus the reading half for both.
 *
 * The storage rules and the reasons for them are in `src/journal.ts`. What is
 * decided here is the shape of the surface:
 *
 *   - Every mutating action takes an optional `runId`. Omitted, it means the
 *     most recently started run that has not ended, and the response says
 *     which run it chose, because a journal that silently wrote to the wrong
 *     run is worse than one that refused.
 *   - Every mutating action is idempotent and says whether it changed
 *     anything, and every one names the call that undoes it.
 *   - Deletion granularity is the run, deliberately. Notes and artifacts
 *     accumulate; an audit trail whose individual entries can be edited away
 *     is not an audit trail. A correction is another note.
 */
import type { ActionSpec } from "../types.js";
export declare const journalActions: Record<string, ActionSpec>;