/**
 * `claude-settings-template-merge.ts` — the comparison and the merge that decide
 * whether an on-disk settings file still declares what the template declares, and
 * that carry every entry the template does not declare across untouched.
 *
 * Split out of `claude-settings-template.ts` (475 raw lines against the 300 cap)
 * when the two layer-B feedback hook entries had to be added to the template: that
 * file now holds the template's own shape, and this one holds the merge machinery.
 * The bodies moved verbatim; the three non-null assertions became the explicit
 * `undefined` checks they already were in effect, so this module is clean at birth.
 * `claude-settings-template.ts` re-exports every symbol below, so it stays the
 * single public entry point for this concern.
 */
import { isRetiredTemplateEntry } from './claude-settings-retirements.js';
/**
 * Compare two serialized template strings: does the on-disk file already
 * declare every entry the generated tree declares?
 *
 * This comparator answers "is each entry the GENERATED tree declares present
 * on disk?", NOT "are the two `hooks` trees identical". Extra on-disk entries
 * are IGNORED, so an entry another writer put in this file never makes it look
 * drifted.
 *
 * That is the deliberate other half of the entry-level merge in
 * `mergeTemplateOwnedHooks` / `workspace-claude-settings-materializer.ts`.
 * `.claude/settings.local.json` has a SECOND writer of `hooks.PreToolUse`:
 * `installAutoCompactHook` appends a `Bash|Task` entry. Under the previous
 * exact-tree rule the merged file carried 4 entries against a 3-entry
 * generated tree, so every `peaks workspace init` answered "drifted",
 * rewrote, and reported `refreshed` forever — precisely the state whole-key
 * ownership existed to prevent, and the reason the merge could not ship alone.
 *
 * Matching is order-insensitive AND multiset-aware: the template declares TWO
 * `Bash` entries — a MEASUREMENT, not a memory, so it is pinned to a predicate
 * rather than restated in prose: `buildClaudeSettingsLocalJson().hooks.
 * PreToolUse` filtered on `matcher === 'Bash'` has length 2 (the Step 0.8 gate
 * and `gate enforce`). Each must have its own counterpart on disk, so a file
 * carrying only one of them is still reported as drifted (the previous
 * index-by-index loop had the same property; it is load-bearing, not a
 * detail). The live count was 4 from TEMPLATE_VERSION 1.9.0 until 1.10.0 retired
 * the two layer-B feedback hooks from the template, which is exactly how a
 * prose count goes stale.
 *
 * Returns `true` iff both strings parse to objects whose `hooks.PreToolUse`
 * arrays satisfy that containment, the on-disk file carries NO entry this
 * template has retired (`isRetiredTemplateEntry`), AND the on-disk `env`
 * already carries every exemption the template declares (extra on-disk keys
 * and extra globs are allowed — a user may exempt other trees, and a
 * requirement the file already exceeds must not re-trigger a write).
 *
 * Returns `false` on any `JSON.parse` error, shape mismatch, or
 * missing `hooks.PreToolUse`. Whitespace and key order do NOT affect
 * the result — the comparison is on the parsed AST, not on bytes.
 *
 * This is the comparator `initWorkspace` uses to decide whether to
 * refresh a stale `.peaks/.claude-settings-template.json` on disk.
 */
export declare function templateContentMatches(generated: string, onDisk: string): boolean;
/**
 * Merge the on-disk `hooks.PreToolUse` list with the template's.
 *
 * the entries IT DECLARES — and nothing else. Every other on-disk entry is
 * carried across verbatim, whatever its matcher, because the template has no
 * opinion about it:
 *
 *   - a `matcher` the template does not declare (`Bash|Task`, the auto-compact
 *     hook `installAutoCompactHook` appends) is never touched;
 *   - surplus entries BEYOND the template's count for a declared matcher (a
 *     user's own `Bash` hook) are surplus too, and survive;
 *   - an on-disk entry that fills a declared slot is REPLACED by the template's
 *     entry for it. That is what makes a hand-edited (or older-release) entry
 *     self-heal instead of lingering next to a correct copy of itself.
 *
 * Slot counting is per `matcher` and positional within it: the template
 * declares TWO `Bash` entries — `buildClaudeSettingsLocalJson()` filtered on
 * `matcher === 'Bash'` is the measurement, and it is 2 — so the first two
 * on-disk `Bash` entries are theirs and a third is the user's. (It was 4 while
 * TEMPLATE_VERSION 1.9.0 also declared the two layer-B feedback hooks; 1.10.0
 * retired those, and because the retirement is tested BEFORE slot counting they
 * never occupy a slot on their way out.) The template's entries are emitted
 * first, in template order, then the preserved ones in their on-disk order —
 * which is a fixed point: re-merging the result yields the result (the
 * template's own entries are encountered first and refill their own slots).
 *
 * Non-conforming entries (no string `matcher`, no `hooks` array) are preserved
 * rather than dropped: guessing at their shape is how a user's entry gets
 * deleted.
 *
 * ONE exception to "preserve what I do not declare": an entry this template
 * used to declare and RETIRED is dropped rather than preserved — TEMPLATE_
 * VERSION 1.8.0's `Write|Edit|MultiEdit` gate, and 1.10.0's two layer-B feedback
 * hooks (see `isRetiredTemplateEntry`). Declaring less cannot retire an entry on
 * its own, because preserving undeclared entries is exactly what this function
 * does; without the drop, a pre-1.8.0 install would keep the no-op handler and
 * its version-pinned script path forever, and a pre-1.10.0 consumer would keep
 * two `Bash` entries whose command points into an `src/` tree it never
 * received. Each predicate is narrow enough that only the exact command this
 * template emitted matches.
 */
export declare function mergeTemplateOwnedHooks(onDisk: ReadonlyArray<unknown>, template: ReadonlyArray<unknown>): unknown[];
/**
 * The retirement vocabulary — the entries this template used to declare and has
 * since RETIRED, and the shape predicate that says so — lives in
 * `claude-settings-retirements.ts`. It was extracted when the second retirement
 * pushed this module past the 300-line cap. Re-exported here so
 * `claude-settings-template.ts`, the single public entry point for the template
 * concern, still reaches it through the module it always did.
 */
export { isRetiredTemplateEntry };