/**
 * Integration tests — "grandeur nature"
 *
 * These tests use content derived from the `_tmp_split_scenario` sub-repo
 * (a tiny calculator module with a linear commit history) to produce
 * realistic 3-way merge conflicts and run the full `resolveAsync` pipeline
 * including the structural merge engine (tree-sitter / WASM).
 *
 * Source versions used (from _tmp_split_scenario git history):
 *   - test-branch-from-ctx : add()
 *   - split-base           : add() + subtract()
 *   - main                 : add/subtract/multiply/divide/modulo
 *
 * Four scenarios:
 *   S1 — two-branches-grow-independently : both sides add different functions
 *        → structural merge should resolve cleanly
 *   S2 — ours-only-change                : ours modifies + adds, theirs unchanged
 *        → structural merge should resolve cleanly
 *   S3 — body-conflict                   : both sides change the same function body
 *        → structural merge returns null, hunk-based resolver takes over
 *   S4 — delete-vs-modify                : ours deletes a function, theirs modifies it
 *        → structural merge returns null, hunk-based resolver cannot resolve either
 *
 * The tests are designed to be non-flaky:
 *   • If web-tree-sitter / tree-sitter-wasms are available (devDeps in this
 *     package), the structural path is exercised and assertions are strict.
 *   • If WASM loading fails (CI without optional deps), `resolveAsync` falls
 *     back transparently and the tests still verify the hunk-based fallback.
 */
export {};
//# sourceMappingURL=grandeur-nature.test.d.ts.map