/**
 * The Bash tool's background-lifetime TEXT: the one sentence the tool description and every launch / adoption
 * receipt render about whether a `run_in_background` process outlives the task, and the three fragments it is
 * built from. Wording only — which rows the reaps take is the registry's (task-registry.ts); the retain answer is
 * handed in, judged by the tool mount through THE retain predicate (background-shell.ts).
 */
/**
 * Lifetime guidance AT THE DECISION MOMENT. The tool description alone does not steer the model:
 * delivered services get hosted via run_in_background and reaped at THEIR OWNING RUN'S teardown — see
 * {@link bgReapClause} for the session-scoped/session-less/isolated-owned-env split — where CC's models
 * habitually use `nohup … &` instead, and BOTH engines kill resident bg rows at teardown. Pure prompt
 * face: the kill semantics
 * (CC-aligned) are untouched. ONE construction point: a ctrl+b-adopted command is the SAME lifetime class
 * (its own leg says so in a comment), so the sentence it gets must be the same string, not a second copy.
 */
export declare function backgroundLifetimeNote(retained: boolean, sessionScoped: boolean, envIsolatedOwned: boolean, face?: "receipt" | "description"): string;