/**
 * `append` and `data.*` step implementations: deterministic text/data mutations on in-memory
 * bytes — append a line, set/merge/delete at a JSON or YAML path.
 *
 * @remarks
 * Internal sibling of the `@nhtio/adk/batteries/media` entry. Pure and cross-env: text ops
 * are string concatenation; structured ops parse (JSON natively, YAML via the `js-yaml`
 * dependency), mutate the value tree, and re-serialize **preserving the source format** —
 * `data.set` on a YAML file yields YAML, on a JSON file yields JSON. These are the verbs
 * that make the lossy text family first-class media: `empty:json | data set path=… value=…`
 * is a create-then-populate chain with no engine requirement at all.
 */
import type { StepImpl } from "../runtime";
/** `append` — append text to text-family media. */
export declare const appendStep: StepImpl;
/** `data.set` — set a value at a JSON/YAML path, creating intermediate containers. */
export declare const dataSetStep: StepImpl;
/** `data.merge` — merge a JSON fragment into the document (deep by default). */
export declare const dataMergeStep: StepImpl;
/** `data.delete` — remove a key/index at a JSON/YAML path. */
export declare const dataDeleteStep: StepImpl;
/** The data step registry fragment, keyed by canonical verb id. */
export declare const DATA_STEPS: ReadonlyArray<[
    string,
    StepImpl
]>;