/**
 * NewRecruit "wtc-compact" and "wtc-full" text adapters.
 *
 * Both formats open with a `++++++++` summary header carrying FACTION KEYWORD,
 * DETACHMENT, TOTAL ARMY POINTS, WARLORD, ENHANCEMENT(s), NUMBER OF UNITS, and
 * SECONDARY tournament-objective shorthand. The body diverges:
 *
 * - **wtc-compact** — one unit per line:
 *   `[CharN: ]Nx <Unit> (P pts): <comma-separated wargear>`
 *   followed optionally by `Enhancement: <Name> (+P pts)` on the next line.
 *
 * - **wtc-full** — uppercase section headers (`BATTLELINE`, `ALLIED UNITS`),
 *   two-line unit blocks (`[CharN: ]Nx <Unit> (P pts)` then `N with <wargear>`),
 *   `Enhancement: <Name> (+P pts)` on its own line, and per-model-type
 *   breakdowns with `• Nx <ModelType>` + indented `N with <wargear>` lines.
 *
 * The {@link Roster} pivot stores units at unit granularity — per-model-type
 * wargear breakdowns and `CharN:` slot numbers aren't modelled, so this adapter
 * collapses them: the parsed unit's `model_count` is summed from the breakdown
 * and its `wargear` is the union of every loadout under it. The `WARLORD` /
 * `Houndpack Lance Character` tokens are stripped from the wargear list (and
 * set `is_warlord`/`is_character` instead) so resolution doesn't try to look
 * them up as weapons. Round-trips are at Roster level, not byte-for-byte.
 *
 * Enhancement points (`+15 pts`) are subtracted from the displayed unit total
 * so `ParsedUnit.points` is the *base* unit cost — matching the ListForge
 * convention where the unit's own cost line is base and the enhancement is a
 * sibling cost line. `total_computed` walks every cost line just like ListForge
 * (base unit pts + each enhancement pts).
 *
 * @packageDocumentation
 */
import type { FormatAdapter } from "./adapter.js";
export declare const newRecruitWtcCompactAdapter: FormatAdapter;
export declare const newRecruitWtcFullAdapter: FormatAdapter;
//# sourceMappingURL=newrecruit-wtc.d.ts.map