@mohasinac/appkit 4.71.0 → 4.71.2

package/dist/features/parts/schemas/firestore.d.ts

@@ -1,925 +0,0 @@
-/**
- * E4/D12 — the PART GLOSSARY and MODEL COMPOSITION collections.
- *
- * Seeded from `docs/research/part-composition-2026-10/`, which is extracted
- * from the local corpus by two committed scripts. Nothing here is hand-typed.
- *
- * ── 🛑 KEYED ON (classification, code), NEVER ON THE CODE ALONE ────────────
- *
- * `105` is a Metal Fight spin-track height, a bare number in Burst is a disc,
- * and `1-60` is a Beyblade X ratchet. Code-alone would explain a Burst disc as
- * a spin track — the same namespacing argument as the feature `group` field,
- * and the reason the document id carries both halves.
- *
- * ── 🛑 WHY `modelComposition` IS A SIBLING, NOT A FIELD ON `categories` ────
- *
- * A named model IS a category leaf (section 4.4), so composition "belongs" to that
- * document — and putting it there is still wrong for two measured reasons.
- * `handleCategoryWrite` calls `notifyRevalidate` as its FIRST statement,
- * unconditionally, so any write to a category drops that page's ISR entry on a
- * project paused at 15.5× its ISR cap. And `CategoryDetailPageView` is already
- * at Rule #6's read ceiling with seven parallel reads. Same conclusion as
- * `categoryCounts` and `priceIndex`, for the same reasons.
- *
- * ── 🛑 THE SLOT SET IS DATA, KEYED ON `system` ─────────────────────────────
- *
- * Slots MERGE: the corpus contains `Spin Gear + Blade Base → RUNNING CORE`
- * (HMS) and `SPIN TRACK + TIP combined: F:D` (4D), 13 such lines extracted. So
- * a fixed field-set per generation cannot express the data, and a
- * `Record<Generation, Slot[]>` would be the hand-written enumeration of Root
- * Cause #61 with a merge case it structurally cannot hold.
- */
-import type { AdminEditableRecord } from "./admin-edit";
-import type { BaseDocument } from "../../../_internal/shared/types/base-document";
-export declare const PART_GLOSSARY_COLLECTION: "partGlossary";
-export declare const MODEL_COMPOSITION_COLLECTION: "modelComposition";
-/**
- * The canonical slot keys, as extracted. Mirrors `SLOT_VOCAB` in
- * `scripts/extract-part-composition.mjs` — the script is the source and this
- * is the type, so a slot that appears in one and not the other is a
- * compile-visible gap rather than a silent one.
- */
-export declare const PART_SLOT_VALUES: {
-    readonly BIT_CHIP: "bit-chip";
-    readonly ATTACK_RING: "attack-ring";
-    readonly WEIGHT_DISK: "weight-disk";
-    readonly SPIN_GEAR: "spin-gear";
-    readonly ENGINE_GEAR: "engine-gear";
-    readonly BLADE_BASE: "blade-base";
-    readonly RUNNING_CORE: "running-core";
-    readonly FACE_BOLT: "face-bolt";
-    readonly ENERGY_RING: "energy-ring";
-    readonly FUSION_WHEEL: "fusion-wheel";
-    readonly CHROME_WHEEL: "chrome-wheel";
-    readonly SPIN_TRACK: "spin-track";
-    readonly PERFORMANCE_TIP: "performance-tip";
-    readonly LAYER: "layer";
-    readonly DISC: "disc";
-    readonly DRIVER: "driver";
-    readonly ARMOUR: "armour";
-    readonly BLADE: "blade";
-    readonly RATCHET: "ratchet";
-    readonly BIT: "bit";
-    readonly GT_CHIP: "gt-chip";
-    readonly GATINKO_CHIP: "gatinko-chip";
-    readonly BASE: "base";
-    readonly SUPERKING_CHIP: "superking-chip";
-    readonly DB_CORE: "db-core";
-    readonly RING: "ring";
-    readonly ARMOR_TIP: "armor-tip";
-    readonly FRAME: "frame";
-    readonly CHASSIS: "chassis";
-    readonly BU_BLADE: "bu-blade";
-    readonly QS_BLADE: "qs-blade";
-    readonly DRIVE_CHIP: "drive-chip";
-    readonly STORM_CHIP: "storm-chip";
-    readonly STRIKE_CHIP: "strike-chip";
-    readonly GRAVITY_RING: "gravity-ring";
-    readonly SPIRIT_SHIELD: "spirit-shield";
-    readonly SPIRIT_AXLE: "spirit-axle";
-    readonly DISC_INTEGRATED_DRIVER: "disc-integrated-driver";
-    readonly LOCK_CHIP: "lock-chip";
-    readonly MAIN_BLADE: "main-blade";
-    readonly ASSIST_BLADE: "assist-blade";
-    readonly OVER_BLADE: "over-blade";
-    readonly METAL_BLADE: "metal-blade";
-    readonly RATCHET_INTEGRATED_BLADE: "ratchet-integrated-blade";
-    readonly RATCHET_INTEGRATED_BIT: "ratchet-integrated-bit";
-    readonly WARRIOR_WHEEL: "warrior-wheel";
-    readonly ELEMENT_WHEEL: "element-wheel";
-    readonly LIGHT_WHEEL: "light-wheel";
-    readonly WHEEL: "wheel";
-    readonly SHOGUN_FACE_BOLT: "shogun-face-bolt";
-    readonly DOME_SPIN_TRACK: "dome-spin-track";
-    readonly EVOLUTION_GEAR: "evolution-gear";
-    readonly BIT_PROTECTOR: "bit-protector";
-    readonly WEIGHT: "weight";
-    readonly CORE: "core";
-    readonly SUPPORT_PARTS: "support-parts";
-    readonly SUB_ATTACK_RING: "sub-attack-ring";
-    readonly CEW: "cew";
-    readonly GEAR_CHIP: "gear-chip";
-};
-export type PartSlot = (typeof PART_SLOT_VALUES)[keyof typeof PART_SLOT_VALUES];
-/**
- * Buyer-facing label per slot.
- *
- * 🛑 A `Record<PartSlot, string>`, so a 21st slot is a COMPILE ERROR rather
- * than a page heading that reads `performance-tip`. That is the whole reason
- * it is not derived by title-casing the key: "Armour" is not "armour"
- * title-cased in the corpus, and `bit-chip` is "Bit Chip" rather than
- * "Bit-chip".
- *
- * Every label here was read off the live documents' own `classification`
- * field, not invented — all 20 slots are populated (87 attack rings down to
- * 4 armour pieces), so none of these is a guess about an empty bucket.
- */
-export declare const PART_SLOT_LABEL: Record<PartSlot, string>;
-/**
- * Which CATEGORY node a part of this classification is filed under.
- *
- * ── 🛑 A PART IS A PLAIN CATEGORY LEAF, `categoryType` OMITTED ──────────────
- *
- * The user's instruction was *"treat parts as also categories, let admins
- * create or add more of them"*, and this map is how both halves are answered at
- * once: a part leaf under these nodes gets `deriveTaxonomy`'s ancestor chain,
- * `countersReconcile`'s tally, the sitemap, breadcrumbs, SEO, an OG image and
- * **the existing admin category editor** — create, edit and delete included —
- * for no new code.
- *
- * 🛑 `categoryType` is OMITTED rather than given a new `"part"` value, and that
- * is the decisive design point. 92 files read `categoryType`, and section 4.4
- * records that `categoryType: "sublisting"` carries SEVEN live defects
- * precisely because a new discriminator value opts out of every path that
- * works — `deriveTaxonomy` never reads it, `countersReconcile` leaves its count
- * permanently 0, and the sitemap excludes it by name. An omitted type changes
- * none of those 92 files and inherits every one of those paths.
- *
- * ── 🛑 KEYED ON THE SLOT ALONE, NOT ON (slot, generation) ───────────────────
- *
- * The first version derived a part's generation from its `usedBy` models, which
- * measured **681 of 753 placeable, 72 unplaceable and 1 spanning two
- * generations**. That was solving a problem that does not exist: each of the 20
- * classification names belongs to exactly ONE generation's vocabulary. A
- * "Performance Tip" is Metal-era by definition, a "Driver" is Burst, a "Bit" is
- * X and a "Bit Chip" is Plastic Gen — the words are not shared. Keying on the
- * slot places **all 753** and cannot be wrong about a part whose `usedBy` is
- * thin.
- *
- * A `Record<PartSlot, string>`, so a 21st classification cannot compile without
- * being given a home — and a part leaf with no parent is a tier-0 orphan, which
- * is the live defect the store sublisting POST still has.
- */
-export declare const PART_SLOT_CATEGORY: Record<PartSlot, string>;
-/** Every slot key, for an index page that must not hand-write the list. */
-export declare const ALL_PART_SLOTS: readonly PartSlot[];
-/**
- * A URL segment to a slot, or `null`.
- *
- * 🛑 Returns `null` rather than casting. A bare `as PartSlot` on a URL segment
- * is how `/parts/nonsense/x` becomes a doc read for `nonsense--x` that quietly
- * misses — the route must 404, which it can only do if the guard says so.
- */
-export declare function partSlotFromSegment(segment: string): PartSlot | null;
-/** One part. */
-/**
- * How much a given spec value is to be trusted, in the corpus's own
- * vocabulary so nothing is lost in translation.
- *
- * `confirmed` — `FACT(PDB)`, verified against PlasticsDB's own part page, or
- *               a `[CONFIRMED CSn Case m]` citation in the case study.
- * `fact`      — a bare `FACT` tag, or a wiki infobox value.
- * `inferred`  — the source flags it as an inference.
- * `estimated` — the source marks it approximate. 🛑 A `~` in a COLUMN HEADER
- *               marks the whole column, which is how gen3/gen4 write it; a
- *               per-cell check alone would publish 300+ estimates as facts.
- */
-export type PartSpecConfidence = "confirmed" | "fact" | "inferred" | "estimated";
-/** One labelled specification row. */
-export interface PartSpec {
-    /** "Weight", "Material", "Full width", "Stats", "WBO legality". */
-    label: string;
-    /** Verbatim from the source. Multi-valued cells are never resolved. */
-    value: string;
-    /** "g", "mm". Absent for a non-dimensional value. */
-    unit?: string;
-    /** Which extractor produced it, for the provenance footnote. */
-    source?: string;
-    confidence?: PartSpecConfidence;
-}
-/** One release of a part: which box, which bey, which vendor, which colour. */
-export interface PartRelease {
-    /** "Takara Tomy", "Hasbro", "Sonokong", "Youngtoys". */
-    vendor: string;
-    /** The box code. `BX-00` is the wiki's marker for "no retail number". */
-    code?: string;
-    /** The Beyblade it came in. */
-    bey: string;
-    /** The set or multipack, when the bey shipped inside one. */
-    set?: string;
-    colourway?: string;
-    /** "G1 Prize", "CoroCoro Exclusive" — the channel, not the colour. */
-    distribution?: string[];
-}
-/** A distinct colourway, deduped on (colour, channel). */
-export interface PartColourway {
-    /** "Red Ver.", "Bronze Ver.", "Supreme Dragon Ver.". */
-    colourway: string;
-    vendor: string;
-    code?: string;
-    distribution?: string;
-    /** The bey this colourway was released in. */
-    inBey: string;
-}
-/**
- * The infobox stat grid, as NUMBERS.
- *
- * 🛑 This is a deliberate second representation of the `Stats` row in
- * `specs[]`, not a mirror to keep in sync. The row is a RENDERING — one line,
- * because six rows of single digits crowd out every real specification on a
- * part page — and this is the VALUE, which is what a sort, a filter, a
- * side-by-side comparison and the simulation all need. Neither can do the
- * other's job, and both are produced by one parse in one pass, so there is no
- * second write path to forget (unlike Root Cause #42's shape).
- *
- * Every key is OPTIONAL because the source states them per part: a page that
- * gives Attack and Burst and nothing else yields exactly those two. A missing
- * key is "not stated", never zero — `weight: 0` is a real rating on a
- * featherweight disc and must stay distinguishable from silence.
- *
- * The scale is 0–6 and is the wiki's own editorial judgement, not a
- * measurement. It is useful for comparison between parts of the same slot and
- * should not be presented as a physical quantity.
- */
-export interface PartRatings {
-    attack?: number;
-    defense?: number;
-    stamina?: number;
-    weight?: number;
-    speed?: number;
-    burst?: number;
-    dash?: number;
-    burstResistance?: number;
-    power?: number;
-    height?: number;
-    runTime?: number;
-}
-/**
- * WBO tournament-format legality.
- *
- * 🛑 A format the source does not rule on is ABSENT, never `false`. Three
- * states exist — legal, banned, and not stated — and collapsing the third into
- * the second would publish "banned in Burst Classic" as a fact about every
- * part whose page simply never mentions Burst Classic.
- */
-export interface PartWboLegality {
-    burst?: boolean;
-    burstGt?: boolean;
-    burstLimited?: boolean;
-    burstClassic?: boolean;
-    xStandard?: boolean;
-    xMasters?: boolean;
-    xOpen?: boolean;
-    mfbStandard?: boolean;
-    mfbLimited?: boolean;
-    mfbZeroG?: boolean;
-    mfb4d?: boolean;
-}
-/**
- * OUR role vocabulary — 10 values covering all 59 slots.
- *
- * Mirrors `PART_ROLE` in `scripts/lib/part-slot-vocab.mjs`, which is the
- * source. A slot missing from that map yields no `role` rather than a guess.
- */
-export type PartRole = "chip" | "ring" | "wheel" | "weight" | "base" | "blade" | "track" | "tip" | "gear" | "support";
-export interface PartGlossaryDocument extends BaseDocument, AdminEditableRecord {
-    /** `${slot}--${codeOrSlug}` — both halves, because a code is not unique. */
-    id: string;
-    /** Buyer-facing label: "Performance Tip", "Fusion Wheel". */
-    classification: string;
-    /** The canonical slot key this classification maps to. */
-    slot: PartSlot;
-    /**
-     * The short code as printed on the part. `null` for a part the corpus knows
-     * only by name.
-     *
-     * 🛑 `null`, not `""`. An empty string reads as a declared empty code; 736
-     * of 759 parts genuinely have no code in any source we hold, and that is a
-     * fact about the sources rather than missing data.
-     */
-    code: string | null;
-    /** The spoken name — what a buyer types. */
-    name: string;
-    /** Grams, when a source confirmed one. 97 of 759 do. */
-    weightG?: number;
-    /**
-     * Model ids that use this part — the single most useful thing a part page
-     * says, and the reason the glossary is worth having as a collection rather
-     * than a lookup table.
-     */
-    usedBy?: string[];
-    /** Code, name and the spoken form of the code. */
-    aliases?: string[];
-    /** Which extractor source contributed the row. */
-    source?: string;
-    /**
-     * Labelled specification rows, ready to render.
-     *
-     * 🛑 ONE array rather than a dozen typed fields. Material, dimensions, spin
-     * direction, JP name, romaji, product code, release date, WBO legality and
-     * the 0–6 stat grid all render as "a labelled row" and none has a query, a
-     * sort, a filter or a format of its own. Twelve typed fields would be twelve
-     * projection-triage entries for zero behaviour; promote one the day a reader
-     * is named for it.
-     *
-     * 🛑 NEVER carries a `Weight` row when `weightG` is set. The page renders
-     * the weight as a badge, so a row too would show it twice and the two could
-     * disagree the moment either is edited. The generator enforces this and
-     * `verify-part-specs` asserts it.
-     */
-    specs?: PartSpec[];
-    /**
-     * One sentence per part, generated from the facts above.
-     *
-     * 🛑 GENERATED, NEVER COPIED. Every source page has an `== Description ==`
-     * section and lifting it is both a CC-BY-SA problem and the precise
-     * anti-pattern the competitor crawl recorded of a rival store — wiki bodies
-     * lifted verbatim, one shipping with the literal UI string "Add to
-     * Wishlist". What this replaces is worse than nothing SEO-wise: a template
-     * reading "{name} is a Beyblade {label}. See which models use it", identical
-     * across 752 pages, which made them compete with each other.
-     */
-    seoDescription?: string;
-    /**
-     * Which Beyblades and sets this part shipped in, first-seen order.
-     *
-     * Distinct from `usedBy`, and both are worth having: `usedBy` holds
-     * `modelComposition` IDS that resolve to our own category leaves, while this
-     * holds the wiki's PRODUCT names including sets and multipacks we have no
-     * leaf for. 10,723 references extracted across 2,008 pages.
-     */
-    shippedIn?: string[];
-    /** The per-release rows `shippedIn` and `colourways` are derived from. */
-    releases?: PartRelease[];
-    /**
-     * Colourways, with the channel each was released through.
-     *
-     * 🛑 Absent and empty mean different things. Absent = "we have not looked";
-     * `[]` with `colourwaysDocumented: true` = "a source asserts there are
-     * none". Without that distinction a part with one release and a part we
-     * never checked render identically, which is Root Cause #57's exact symptom.
-     */
-    colourways?: PartColourway[];
-    colourwaysDocumented?: boolean;
-    /**
-     * A mould revision changes the physical part — weight, burst resistance — so
-     * it is a DIFFERENT axis from colour and must not be folded into it.
-     */
-    hasMoldVariations?: boolean;
-    /**
-     * The 0–6 stat grid as numbers. Present on 1,149 of 2,490 rows — the source
-     * states it per part, so absence is "not stated", not zero.
-     */
-    ratings?: PartRatings;
-    /**
-     * The ceiling `ratings` are out of — 6, 8 or 100.
-     *
-     * 🛑 LOAD-BEARING, because each generation rates on its own scale and they
-     * share these fields. Measured: Beyblade X rates 0-100 (237 rows) while
-     * Burst rates 0-6 or 0-8 (945 rows), so mean `attack` by slot reads
-     * `blade 31.8` beside `driver 1.78`. Anything that sorts, compares or
-     * simulates on a rating MUST divide by this first; without it a Beyblade X
-     * blade outranks every Burst layer five times over.
-     *
-     * Derived per system from the highest rating observed for it, rounded up to
-     * a standard step — not from a hand-written table, which was wrong within
-     * one run (`warrior-wheel--dragoon` carries attack 7 against a declared 6).
-     */
-    ratingScale?: number;
-    /**
-     * The same axes rescaled to 0-100, so a part can be compared ACROSS
-     * generations — which the game needs, since it has cross-gen battles.
-     *
-     * 🛑 This equalises the EDITORIAL JUDGEMENT, not the capability. A Burst
-     * layer at 6/6 and a Beyblade X blade at 100/100 both land on 100 and are
-     * not equally strong — that blade is 30 g against the layer's 13 g. So it
-     * answers "how good is this part for its generation", which is the right
-     * basis for a balanced roster and the wrong basis for claiming physical
-     * equivalence. `weightG` carries the latter, in grams, unnormalised.
-     *
-     * `ratings` stays raw beside it: a normalised value can be recomputed from
-     * the raw pair, a discarded raw value cannot.
-     *
-     * 🛑 FOR COMPARING OPPONENTS, NEVER FOR SUGGESTING A BUILD. A bey can only
-     * be ASSEMBLED within one generation — a Burst layer does not fit a Beyblade
-     * X ratchet — while battles are cross-generation. So this field belongs in a
-     * matchup, a leaderboard or a side-by-side, and a "build your own" picker
-     * must constrain to a single system's stack regardless of what it says.
-     */
-    ratingsNormalised?: PartRatings;
-    /** WBO format legality across 11 formats; an unstated format is absent. */
-    wboLegality?: PartWboLegality;
-    /**
-     * Other names for this exact part — the community abbreviation (`Armor Tip
-     * - Adventure` is `Ad`) and the other vendor's name. On 1,072 of 2,490 rows.
-     * Feeds search, so a buyer can find a part by the code printed on it.
-     */
-    aka?: string[];
-    /**
-     * Hasbro's own product code, a SEPARATE field from `productCodes`. On 309
-     * rows, and it is the Hasbro <-> Takara-Tomy equivalence stated outright.
-     */
-    hasbroCode?: string;
-    /** Attack / Defense / Stamina / Balance, per part. 793 rows. */
-    partType?: string;
-    /** Right-Spin / Left-Spin / Dual. 756 rows. */
-    spinDirection?: string;
-    /** Beyblade X's attribute label — "Sky" and siblings. 29 rows. */
-    element?: string;
-    /**
-     * The character this part belongs to in the story — `Bit Chip - Black
-     * Dranzer` is Kai Hiwatari's. Only 27 rows, but it is the sole place a PART
-     * is tied to a character.
-     */
-    owner?: string;
-    /** The episode this part appeared in. 22 rows. */
-    appearAnime?: string;
-    /**
-     * OUR OWN classification — what the part DOES, across generations.
-     *
-     * 🛑 `slot` cannot carry this. It mirrors the source's `Classification=`
-     * spelling and it is half of every document id (`${slot}--${code}`), and
-     * those ids are LIVE URLS (`/parts/{classification}/{code}`). Renaming a
-     * slot re-keys 2,490 rows and breaks every inbound link — a slug is the one
-     * field that cannot be quietly corrected later. So this is additive.
-     *
-     * It collapses the source's line-specific names onto one role:
-     * `bu-blade` / `qs-blade` / `blade` are all `blade`; the six Burst chip
-     * variants are all `chip`. Derived in `scripts/lib/part-slot-vocab.mjs`,
-     * which covers all 59 slots with 10 roles.
-     */
-    /**
-     * The part SYSTEM — "Dynamite Battle Layer System", "4D System", "Basic
-     * Line". Stated on 1,961 of 2,087 source pages (94%).
-     *
-     * 🛑 This is the generation key, and it is load-bearing rather than
-     * decorative:
-     *
-     * 1. ASSEMBLY IS WITHIN-GENERATION ONLY. No bey can be built across
-     *    generations, and Plastic and HMS do not interchange either, so a build
-     *    validator needs each part's system. Nothing else on the row answers it.
-     *
-     * 2. ONE SLOT CAN HOLD TWO DIFFERENT PARTS. `blade` is the measured case:
-     *    Beyblade X blades are metal at a ~32 g median while Burst QuadDrive and
-     *    Dynamite Battle blades are plastic at ~7-11 g. A per-slot mass band
-     *    cannot be correct for both, and without this field nothing downstream
-     *    could tell them apart.
-     */
-    system?: string;
-    /** The retail series — "Beyblade Burst QuadStrike", "Beyblade: Metal Fury". */
-    series?: string;
-    role?: PartRole;
-    /**
-     * Every stack role one moulding fills, listed TOP-TO-BOTTOM. A part that
-     * covers a single position does not carry this field at all.
-     *
-     * Integration is real and spans generations: HMS merges spin gear and blade
-     * base into a Running Core, a 4D Bottom (`D:D`, `X:D`) is a spin track and
-     * a performance tip in one piece, a Burst `disc-integrated-driver` is a disc
-     * and a driver, and `fusion-wheel--variares` is an energy ring and a fusion
-     * wheel. A Plastic-era base can integrate its Sub Attack Ring.
-     *
-     * 🛑 Load-bearing for any stack validation. `role` files an integrated part
-     * under its PRIMARY function, so a validator reading only that believes the
-     * other position is still empty and offers a part that cannot physically go
-     * there — it will refuse a legal build, and an exploded 3D view will show a
-     * gap where a solid piece is.
-     *
-     * 🛑 PER PART, NOT PER SLOT — that is the whole reason this is a field and
-     * not a lookup. `fusion-wheel--variares` integrates the ring and
-     * `fusion-wheel--jade` does not; same slot, different moulding. Jade is
-     * multi-PIECE, which is a different fact (see `pieceCount` when it lands).
-     *
-     * 🛑 Do NOT re-spell this as "fused". "Fusion Wheel" is a literal MFB slot
-     * name, so `fusedRoles` reads as *the roles of the fusion wheel* — the
-     * opposite of the meaning. The source's own slot names already use the
-     * right word: `disc-integrated-driver`, `ratchet-integrated-bit`.
-     *
-     * Populated by `scripts/derive-part-integration.mjs`, which reads it off the
-     * compositions each part actually appears in — the source states a 4D
-     * Bottom's `Classification` as plain "Performance Tip", so this cannot be
-     * copied from an infobox and is not guessed either.
-     */
-    integratedRoles?: PartRole[];
-    /**
-     * An owner-uploaded 3D model. Empty by default and deliberately so — the
-     * models are supplied by the owner, not ingested from anywhere.
-     *
-     * 🛑 NEVER served through `/api/media/[...slug]`. That route applies NO
-     * authentication, raw-pipes non-images with a 30-day immutable cache, and
-     * sits over a bucket whose storage rule is `allow read: if true` — so a GLB
-     * there is a public download. A mesh is the asset someone could build a
-     * competing game from, so it needs a signed, short-lived URL and an
-     * authenticated route of its own.
-     *
-     * 🛑 And a browser viewer cannot make a mesh unextractable — WebGL buffers
-     * can be dumped from any page that renders them. The honest mitigation is to
-     * publish a DECIMATED preview and keep the full-resolution mesh server-side;
-     * "protected" here means inconvenient, never impossible.
-     */
-    model3d?: {
-        url: string;
-        format: "glb";
-        sizeBytes: number;
-        /** A low-poly public preview, when the full mesh is held back. */
-        previewUrl?: string;
-        credit?: string;
-        creditUrl?: string;
-    };
-    /**
-     * An owner-uploaded sound, with its waveform for display.
-     *
-     * Renders through the existing `<MediaAudio>` primitive, so this needs no
-     * new UI primitive. `waveform` is a coarse amplitude array for drawing the
-     * trace without decoding the audio client-side.
-     */
-    sound?: {
-        url: string;
-        durationMs?: number;
-        waveform?: number[];
-        label?: string;
-    };
-    /**
-     * The Japanese name, the romanisation, and the kanji where the source gives
-     * one.
-     *
-     * 🛑 Top-level fields AS WELL AS `specs[]` rows, which is not duplication for
-     * its own sake: a `<title>`, an `og:title`, an hreflang alternate and a
-     * JSON-LD `alternateName` all need a FIELD. None of them can scan an array
-     * of label/value pairs for one whose label happens to read "Japanese name",
-     * and that is where these 1,068 values previously lived and died.
-     */
-    jpName?: string;
-    romaji?: string;
-    kanjiName?: string;
-    /** `/media/<slug>`. 🛑 Never a raw Storage host URL. */
-    image?: string;
-    /** The wiki page the photo came from — the CC-BY-SA attribution target. */
-    imageSourceUrl?: string;
-    /** "Read more on the Beyblade Wiki". Facts taken, prose theirs, link out. */
-    sourceUrl?: string;
-    /**
-     * Hand-written analysis, read from the sources one page at a time.
-     *
-     * 🛑 ONE NESTED OBJECT, not twenty top-level fields, and the reason is the
-     * merge rather than tidiness. Everything else on this document is EXTRACTED
-     * and is regenerated wholesale by `generate-parts-seed.mjs`; this is
-     * AUTHORED and must survive that regeneration. Keeping it under one key
-     * makes the overlay merge a single assignment the generator cannot
-     * accidentally clobber field-by-field, and makes "is this ours or the
-     * wiki's?" answerable by position rather than by memory.
-     *
-     * 🛑 It also keeps `adminEditedFields` honest: an admin editing
-     * `authored.verdict` records one path, where twenty flattened fields would
-     * need twenty entries and the first missed one would be silently
-     * re-generated over.
-     */
-    authored?: PartAuthoredAnalysis;
-}
-/**
- * What a human wrote about one part after reading its sources.
- *
- * ── 🛑 WHY THESE FIELDS AND NOT A FREE-TEXT BLOB ───────────────────────────
- *
- * Each one is a question a buyer or a game implementation actually asks, and
- * each was being answered in passing inside prose where nothing could filter,
- * sort or require it. `availability` is the worked example: 93 records carried
- * "one bey, Takara Tomy only" and "widely shipped across six products" inside
- * their competitive reasoning, so the single most commercially useful fact on
- * the record was unqueryable until it became a field.
- */
-export interface PartAuthoredAnalysis {
-    /** My own account of the shape, in my words, from the sources' facts. */
-    geometryNote: string;
-    /** 2-3 sentences. The thing a buyer reads first. */
-    verdict: string;
-    competitive: {
-        /** essential | useful | collector | outclassed. */
-        tier: PartCompetitiveTier;
-        /** 0-100 WITHIN its slot, so parts are comparable where they compete. */
-        score: number;
-        /** Where the judgement came from, so a reader can discount it. */
-        basis: "source-overall" | "ratings" | "mass" | "legality" | "combo-list" | "inference";
-        /**
-         * Per format or per role, because one part is often two parts.
-         *
-         * 🛑 Not decoration: `attack-ring--circle-upper` produces monstrous Smash
-         * ONLY in left spin and mingles all three attack types in right spin, from
-         * one fixed shape. A single tier for that part is a lie in one direction.
-         */
-        byFormat?: Record<string, string> | null;
-        reasoning: string;
-    };
-    designDifficulty: {
-        /** 0-100. How hard this part is to reproduce faithfully in a game. */
-        score: number;
-        /** From the CLOSED driver set in `terms.json`. */
-        drivers: string[];
-        reasoning: string;
-        /** The detail a naive implementation gets wrong. */
-        note?: string;
-    };
-    /**
-     * Which products it came in, and in what colour.
-     *
-     * 🛑 `beys` is what a RELEASE LIST says shipped it — a purchasing fact with
-     * codes and colourways attached. `beysFromOtherSources` is "a document
-     * describes this part inside this bey", LABELLED BY ORIGIN
-     * (`corpus:gen1-plastic-dranzer-v2`). Merging the two would make a corpus
-     * mention indistinguishable from a box you can buy, which is the one
-     * distinction a shopper needs. 306 parts have the second and not the first.
-     */
-    availability: {
-        beys: string[];
-        beysFromOtherSources?: string[];
-        usedByIds?: string[];
-        colourways: Array<{
-            colourway: string;
-            vendor?: string;
-            code?: string;
-            distribution?: string;
-            inBey?: string;
-        }>;
-        codes?: string[];
-        hasbroCode?: string;
-        moulds?: boolean;
-        /** Why `beys` is empty, when it is. An empty list is a finding, not a blank. */
-        note?: string | null;
-    };
-    /**
-     * The character who used it in the story.
-     *
-     * 🛑 The single biggest collector hook, and it does NOT live on the part
-     * pages: measured, the `Owner` infobox key is filled on 3 of 2,248 part
-     * pages. It comes from the bey and character pages. Nobody searches "Attack
-     * Ring MA-04"; they search "Tyson's Dragoon".
-     */
-    owner?: string;
-    /** "Bladebreakers", "Blitz Team" — a collecting set in its own right. */
-    team?: string;
-    /** Series plus episode of first appearance, as the source words it. */
-    animeDebut?: string;
-    /** How hard it is to get. A closed enum so it can be faceted. */
-    rarity?: PartRarity;
-    /** The vendor or region that gated it — "SH-03/04 Chinese exclusive". */
-    exclusiveTo?: string;
-    /**
-     * How to tell which copy you are buying.
-     *
-     * 🛑 The most actionable buying guidance in the whole corpus and it was
-     * buried in prose. Circle Upper's first mould has a 2.9 mm metal frame and
-     * weighs mid-19 g; its second has 3.6 mm and weighs upper-20 g, and they
-     * perform differently. Cross Griffon's Hasbro mould moves the figurine
-     * mounts to the top where they only add recoil, so the wiki says a Takara
-     * copy is "greatly preferred". That is a purchase decision.
-     */
-    mouldIdentification?: string;
-    /**
-     * What wears or breaks, and whether it matters — which is exactly what a
-     * USED-marketplace listing needs and what the sources keep volunteering:
-     * "spikes wear with use but do NOT affect usability", "very unlikely to
-     * break, even on Grip Base", "sharp wing tips can cause damage to Stadium
-     * walls".
-     */
-    conditionWatch?: string;
-    /** What else you must own for it to work — "needs a taller RC to clear the floor". */
-    needsToUse?: string;
-    /**
-     * Named finishing moves, with the character who performs them.
-     *
-     * Source: the bey corpus's own tables, e.g.
-     * `| Dark Wings | Phi | Layer-level impact at low spin | Burst Turbo |`.
-     * Nothing had ever joined them to a part or a bey.
-     */
-    specialMoves?: Array<{
-        name: string;
-        character?: string;
-        effect?: string;
-        system?: string;
-    }>;
-    /** The spirit bound to the bey — a game entity in its own right. */
-    bitBeast?: string;
-    /**
-     * How it wins.
-     *
-     * 🛑 FOUR classes are already evidenced and most models carry two. Beyond
-     * knock-out and destabilise-then-outspin: Cross Griffon has "some of the
-     * most effective stopping power of any Attack Ring", interrupting rotation
-     * without moving the opponent, and Cross Spiker delivers "spike attack" in
-     * left spin. An implementation with only KO and topple has nowhere to put
-     * either, and would render the generation's best stopping-power ring as a
-     * mid-tier smash part.
-     */
-    winCondition?: string[];
-    /**
-     * Every photograph of this part that a source carries, with its caption.
-     *
-     * 🛑 THE CAPTION IS THE DATA. "Advance Attacker with Metal Frame detached" is
-     * not a label for a picture — it is the statement that a photograph exists of
-     * the one feature the part is built around, and looking at it corrected the
-     * prose: every source calls the metal frame a "Metal Frame" that "separates
-     * from the ABS Caul", and the photograph shows it is a single die-cast
-     * triskelion — a central annulus, three radial arms, three tangential claws,
-     * with three registration pegs at 120° that are what permit the flip. No
-     * source says any of that.
-     *
-     * 🛑 `image` above is ONE `/media/<slug>` for the card. This is the gallery,
-     * and it holds SOURCE urls deliberately: routing them through `/media`
-     * requires uploading ~1,600 objects to live Storage, which is a separate,
-     * explicitly-authorised step. Recording what exists is free and reversible;
-     * publishing it is neither. Nothing renders these directly — Root Cause #27
-     * and the media rules still apply at the point of use.
-     *
-     * 🛑 Fetching needs `Referer: https://beyblade.fandom.com/`.
-     * `static.wikia.nocookie.net` hotlink-protects on the REFERER, not the
-     * User-Agent: a browser UA alone returns 403 `text/html`, which reads as "the
-     * image is gone" and sends you hunting for a replacement that does not exist.
-     *
-     * 🛑 fandom and WBO are ONE lineage here, not two sources. Both serve
-     * `1AdvanceStriker.JPG` under the same name. Dedupe on `name`, never on
-     * `url`, or one photograph is counted as corroboration of itself.
-     */
-    photos?: Array<{
-        /** The source's own caption. Empty on WBO, which usually gives none. */
-        caption?: string;
-        /** Original upload filename — the dedupe key across hosts. */
-        name?: string;
-        /** Full-size URL, with the host's thumbnail scaling undone. */
-        url: string;
-        /** `fandom` | `wbo` — which crawl it came from, for attribution. */
-        host?: string;
-        /** What this photo PROVES that the prose does not say. */
-        shows?: string;
-    }>;
-    /**
-     * What wear does to it.
-     *
-     * 🛑 WEAR CAN BE A POSITIVE, which a durability model that only degrades
-     * cannot express. hmsdb's best combo for Circle Upper wants "a Bearing Core
-     * 2 that is WORN ENOUGH to consistently flower pattern". Treating wear as
-     * monotonic damage contradicts the source.
-     */
-    wearBehaviour?: string;
-    /** Launcher or winder needed, and whether spin direction is chosen at launch. */
-    launcherRequirement?: string;
-    /** Where behaviour changes by stadium — range matters more in a wide one. */
-    stadiumDependence?: string;
-    /** Counters and countered-by, as the sources name them. */
-    matchups?: {
-        strongAgainst?: string[];
-        weakAgainst?: string[];
-        note?: string;
-    };
-    /** Parts the sources pair it with, verbatim from their combo lists. */
-    comboPartners?: string[];
-    /** Terms from `terms.json`, so the vocabulary stays closed. */
-    termsUsed?: string[];
-    /** Where a source was wrong or where two sources disagree. */
-    corrections?: Array<{
-        field: string;
-        was: string;
-        now: string;
-        basis: string;
-    }>;
-    /** confirmed | probable | weak — and the gate checks it against the record. */
-    confidence: "confirmed" | "probable" | "weak";
-    confidenceNote?: string;
-    /** Which sources the record was written from. */
-    sourceUsed: string[];
-    sourceUrl?: string;
-    authoredAt: string;
-    /** Set when a record is re-read after new sources became reachable. */
-    reReadAt?: string;
-}
-/** How hard a part is to obtain. Faceted, so it is a closed set. */
-export declare const PartRarityValues: readonly ["mass-retail", "booster", "random-booster", "set-only", "prize", "vendor-exclusive", "regional-exclusive"];
-export type PartRarity = (typeof PartRarityValues)[number];
-/**
- * How much a part matters competitively.
- *
- * 🛑 `collector` is not a weak `useful`. It means "worth owning rather than
- * playing" and it is the only tier assignable with NO performance evidence —
- * which is what a part like `attack-ring--dark-spike`, whose every source is
- * silent, honestly deserves.
- */
-export declare const PartCompetitiveTierValues: readonly ["essential", "useful", "collector", "outclassed"];
-export type PartCompetitiveTier = (typeof PartCompetitiveTierValues)[number];
-/** One slot of one model's composition. */
-export interface ModelSlot {
-    slotKey: PartSlot;
-    /** The corpus's own term for the slot, e.g. "METAL ATTACK RING (MAR)". */
-    slotLabel: string;
-    partName: string;
-    weightG?: number;
-    /** The `partGlossary` id, when the part resolved to a glossary row. */
-    partId?: string;
-    /**
-     * I9 — which COLOURWAY of that part this model needs.
-     *
-     * ── 🛑 THE CASE THIS EXISTS FOR, in the user's own words ────────────────
-     *
-     * *"there is a part called metal ball, it comes with 2 beyblades — Poison
-     * Zurafa S130MB and L-Drago Guardian S130MB. But the L-Drago version is very
-     * rare and costly and is in silver, while the Zurafa one is transparent black
-     * with a metal tip. Both behave the same way and have the same design, but to
-     * make an L-Drago bey I need the silver one and for Zurafa the black
-     * transparent one. Same with their S130s."*
-     *
-     * So: ONE glossary row (`performance-tip--mb`), same mould, same weight, same
-     * stats — and TWO physical variants that are NOT interchangeable and differ
-     * wildly in value. No stat distinguishes them.
-     *
-     * ── 🛑 WHY THIS FIELD RATHER THAN MATCHING ON `partId` ALONE ────────────
-     *
-     * The "buildable now" rollup would otherwise report *"you can build an
-     * L-Drago Guardian S130MB"* while the only MB on the shelf is the Zurafa
-     * black. A confident, specific, wrong answer with no error anywhere — and the
-     * seller discovers it holding the wrong part. Matching has to be
-     * `(partId, colourway)`.
-     *
-     * ── 🛑 UNSET MEANS "ANY", AND NEVER "THE FIRST ONE FOUND" ───────────────
-     *
-     * Most slots are genuinely colour-agnostic. Forcing a value everywhere would
-     * invent a constraint the corpus does not support, and defaulting to whatever
-     * happened to be in the bin is the same class of guess the price index
-     * refuses when its sample is too small.
-     */
-    expectedColourway?: string;
-}
-/**
- * Two slots collapsing into one, in systems where they are a single moulded
- * module.
- *
- * 🛑 This is why the slot set cannot be a per-generation constant: HMS has a
- * `RUNNING CORE` where Plastic Gen has a separate Spin Gear and Blade Base,
- * and 4D has a combined `4D Bottom` where MFB has a Spin Track and a tip.
- */
-export interface ModelSlotMerge {
-    into: PartSlot;
-    merges: PartSlot[];
-}
-export interface ModelCompositionDocument extends BaseDocument {
-    /** The corpus doc id, e.g. `gen2-mfb-big-bang-pegasus`. */
-    id: string;
-    name: string;
-    /** `gen1` … `gen4`, normalised — never the raw freeform header. */
-    generation: string | null;
-    /**
-     * The parenthetical from the raw header, kept because it is often the
-     * interesting part — but never a value anything groups or filters on
-     * (Root Cause #33).
-     */
-    generationNote?: string;
-    system?: string | null;
-    series?: string | null;
-    productCode?: string | null;
-    slots: ModelSlot[];
-    slotMerges?: ModelSlotMerge[];
-    /** The corpus file, so a claim can be traced back. */
-    source?: string;
-    /** The named-model category this composition describes, when one exists. */
-    categoryId?: string;
-    /**
-     * The character who used this bey, as a `character-*` category id.
-     *
-     * 🛑 An ID, not a name. Character names are re-localised between the
-     * Japanese and English releases (Takao Kinomiya / Tyson Granger), so a name
-     * is the one key guaranteed to drift — the same trap `brand-rows.ts` records
-     * for brands matching on display name.
-     */
-    owner?: string;
-    /**
-     * ── 🛑 THE ANIME SUCCESSION CHAIN, NOT RELEASE ORDER ────────────────────
-     *
-     * `previousBey` is the bey this one replaced in the STORY; `nextBey` is the
-     * one that replaced it. Both are composition ids.
-     *
-     * 🛑 IT CANNOT BE DERIVED FROM PRODUCT CODES, and a generator must not try.
-     * Tyson's chain runs Dragoon -> Dragoon S -> Dragoon V -> Dragoon V2 ->
-     * Dragoon G -> Dragoon MS, crossing four part systems and three toy lines,
-     * and the codes do not order it. The sequence is a narrative fact stated in
-     * prose on the bey and character pages, so it is READ.
-     *
-     * 🛑 BOTH DIRECTIONS ARE STORED AND MUST AGREE. A one-way link makes "what
-     * came before this" unanswerable from the earlier bey's page, and a
-     * `character.lineup` that disagrees with these links is the denormalised-
-     * mirror trap (Root Cause #42) — here it would silently break a progression.
-     * `audit-lineup-symmetry` checks both.
-     */
-    previousBey?: string;
-    nextBey?: string;
-}
-/** `(slot, code|name)` → document id. The ONE place this is composed. */
-export declare function partGlossaryId(slot: PartSlot, codeOrName: string): string;
-/**
- * Whether a listing of this TYPE is the physical assembly the composition
- * describes.
- *
- * 🛑 Found by measuring rather than by reasoning, and it is a real defect the
- * first version of D12 shipped: of 71 live products exactly ONE files under a
- * leaf that has a composition, and that one is
- * `art-dranzer-phoenix-poster` — so the only listing in the whole catalogue
- * that got a "Parts" tab was a POSTER, offering an attack ring, a weight disk
- * and a blade base as its contents. Nothing errored; it rendered a correct
- * part list for the wrong kind of object.
- *
- * The distinction is whether the listing IS the model or merely DEPICTS or
- * REFERENCES it. A print, a sticker sheet and a redemption code all sit under
- * the model's leaf on purpose (section 4.4: a sticker sheet belongs beside the
- * bey it is for) and none of them is made of its parts.
- *
- * 🛑 A `Record<ListingType, boolean>`, so a tenth listing type cannot compile
- * without answering the question — the lesson of Root Cause #61, which this
- * codebase has paid for ten hand-written enumerations of one union.
- */
-export declare const LISTING_TYPE_HAS_COMPOSITION: Record<import("../../products/types/index").ListingType, boolean>;