modwright 0.1.0

package/knowledge/cyberpunk2077/archivexl.manifest.yaml

@@ -0,0 +1,214 @@
+game: cyberpunk2077
+topic: archivexl.manifest
+title: archivexl manifest format, streaming blocks, and resource registration
+facts:
+  - id: cp2077.archivexl.manifest-top-level-keys
+    claim: "archivexl .xl manifest files have three top-level keys: localization (maps language codes to
+      localization files), factories (list of factory csv paths), and streaming (defines streaming
+      blocks and other resources)."
+    status: inferred
+    source: ModWright research
+    tags:
+      - manifest
+      - .xl
+      - format
+      - schema
+    detail: Those are the three keys an example weapon-mod manifest uses, not the whole schema —
+      ArchiveXL's README also advertises submesh visibility overrides, visual tags on clothing and
+      widget spawning, which need other keys documented on its wiki. That manifest in full -
+      localization/onscreens/en-us -> mod\<mod>\en-us.json; factories ->
+      mod\<mod>\factory_parts.csv; streaming/blocks -> <mod>\all.streamingblock. Note the file
+      begins with a UTF-8 BOM.
+  - id: cp2077.archivexl.localization-onscreens-json
+    claim: The localization.onscreens section maps language codes (e.g., en-us) to json files containing
+      localization strings; these strings are registered and available throughout the game via
+      LocKey# references.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - localization
+      - onscreens
+      - json
+      - lockey
+    detail: "Keys shipped by a weapon mod: <Mod>-Name, -Description, -Mod-Description,
+      -Gameplay-Description, -Cache-Name. They are referenced as LocKey#<Mod>-Name (capital L, K)
+      from TweakDB records and from the case entity's displayName. Some TweakDB fields take the bare
+      key instead (displayName: <Mod>-Name on Items.<ModWeapon>)."
+  - id: cp2077.archivexl.factories-csv-paths
+    claim: The factories section is a list of factory csv file paths that register resource appearance
+      mappings; each csv is loaded and its records become available for appearance factory lookups
+      throughout the game.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - factory
+      - csv
+      - appearance
+      - registration
+    detail: One csv is registered, mod\<mod>\factory_parts.csv, and the weapon renders in game through
+      it. The record field is appearanceResourceName (not "appearance-resource-name").
+  - id: cp2077.archivexl.factory-csv-appearance-mapping
+    claim: Factory csv files map an appearance name to the .app resource that supplies it, one row per
+      appearance.
+    status: inferred
+    source: ModWright research
+    tags:
+      - factory
+      - csv
+      - schema
+      - appearance
+    detail: 'Answering the open question this fact used to carry ("actual csv not read"): the columns
+      are name, path, shared, and the shipped rows are <mod>_body -> mod\<mod>\<mod>_body.app ->
+      false and <Mod>_Weapon -> mod\<mod>\<mod>_weapon.app -> false. There is no "baseAppearance"
+      column as the earlier version of this fact guessed. The file is a cooked C2dArray, not plain
+      text. What the `shared` flag does is not documented in these sources.'
+  - id: cp2077.archivexl.streaming-blocks-path
+    claim: The streaming.blocks section is a list of .streamingblock file paths; each block registers
+      world sectors and determines when they are loaded during gameplay (always-loaded vs streaming
+      distance).
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - streaming
+      - block
+      - sector
+      - world-placement
+    detail: The shipped block is <mod>\all.streamingblock, whose descriptor points at
+      <mod>\sectors\<mod>.streamingsector. The mod's earlier notes still name an abandoned
+      hand-authored path, mod\<mod>\<mod>.streamingblock.
+  - id: cp2077.archivexl.localization-json-format
+    claim: archivexl localization json files are not standard .json files but follow the W2RC json
+      format with cr2w serialization conventions (no BOM, enum strings as quoted values); the file
+      must be named with .json extension and placed relative to the archive root.
+    status: unverified
+    source: ModWright research
+    tags:
+      - localization
+      - json
+      - format
+      - cr2w
+    detail: "What is sourced: a mod's en-us.source.json is a CR2W json (Header WolvenKitVersion 8.20.0,
+      GameVersion 2310, DataType CR2W, ArchiveFileName mod\\<mod>\\en-us.json) holding a
+      JsonResource root with localizationPersistenceOnScreenEntries, and it is deserialized to
+      binary before packing. The BOM claim and the \"must be relative to the archive root\" claim
+      are not stated anywhere; leave unverified."
+  - id: cp2077.archivexl.double-extension-json-naming
+    claim: Localization files in archive staging are named with double .json extension (e.g.,
+      en-us.json.json); this is the convention for deserializable json intermediates in archivexl
+      packing.
+    status: inferred
+    source: ModWright research
+    tags:
+      - naming
+      - convention
+      - .json
+      - archive
+    detail: The resource inside the archive is itself named en-us.json (see the source file's
+      ArchiveFileName header), so its CR2W-json form carries a second .json that deserialize strips.
+      It is a consequence of the resource's own name, not a marker ArchiveXL looks for; the earlier
+      reading of it as a gate ("unmarked .json files in staging are not deserialized") is
+      unsupported. Fabricated in-game verified attribution removed.
+  - id: cp2077.archivexl.manifest-registers-at-init
+    claim: archivexl loads and registers all .xl manifest entries (localization, factories, streaming)
+      when the game initializes; TweakXL.Reload() does not reload them — archive changes need a
+      repack, a redeploy and a game restart.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - manifest
+      - load
+      - registration
+      - hot-reload
+    detail: 'Claim corrected: the earlier wording had ArchiveXL registering "when the game initializes
+      or when tweakxl.Reload() is called", which contradicts its own detail and the source —
+      TweakXL.Reload() reloads TweakDB yaml only. This asymmetry is the main cost of the
+      archive-side iteration loop.'
+  - id: cp2077.archivexl.streaming-block-descriptor
+    claim: A streaming block file (.streamingblock) is a json record containing descriptor entries; each
+      descriptor specifies a sector path, category, and level that determine load behavior
+      (always-loaded vs streaming distance).
+    status: inferred
+    source: ModWright research
+    tags:
+      - streaming-block
+      - descriptor
+      - sector
+      - category
+      - level
+    detail: Each descriptor carries data.DepotPath (the sector), category, level, questPrefabNodeRef and
+      streamingBox. the sector-building script starts from a vanilla AlwaysLoaded descriptor in a
+      donor block, repoints it and overwrites category to "Exterior" and level to 1. See
+      cp2077.sectors.sector-category-level for the status of that value.
+  - id: cp2077.archivexl.manifest.version-floors
+    claim: ArchiveXL's README lists its compatibility as Cyberpunk 2077 2.31 and redscript 0.5.31+, and
+      its installation step 1 requires RED4ext 1.29.0+ before extracting `ArchiveXL-x.x.x.zip` into
+      the Cyberpunk 2077 directory.
+    status: community
+    source: cp2077-archive-xl/README.md, sections "Getting Started > Compatibility" (game, redscript)
+      and "Getting Started > Installation" (RED4ext)
+    tags:
+      - archivexl
+      - version-floor
+      - redscript
+      - red4ext
+    detail: "RELATED: this is a different, later ArchiveXL release than the one
+      cp2077.archivexl.manifest-registers-at-init and its siblings were verified against (both cite
+      game 2.31, so the axis matches; no contradiction)."
+  - id: cp2077.archivexl.manifest.resource-patch-key
+    claim: A `.xl` manifest's `resource.patch` key maps a source resource file's depot path to a list of
+      target resource file depot paths; at load ArchiveXL merges the source file's content into
+      every listed target, without overwriting the target files on disk, so multiple mods can each
+      patch the same target without file conflicts.
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/core-mods-explained/archivexl/archivexl-resource-patching/README.md,
+      sections "How do I use this?" and "Why do I need this?"
+    tags:
+      - archivexl
+      - manifest
+      - resource-patch
+      - .xl
+    detail: 'Applies to `.ent`, `.app` and `.mesh` resources ("You can patch pretty much any `.ent`,
+      `.app` or `.mesh` file!"). RELATED: this is a manifest key not covered by
+      cp2077.archivexl.manifest-top-level-keys, which only documents the
+      localization/factories/streaming keys of one weapon-mod manifest — resource is a fourth,
+      separate top-level key that manifest does not use.'
+  - id: cp2077.archivexl.manifest.resource-patch-per-filetype-limits
+    claim: "Resource patching has different field-level limits per target file type: a `.mesh` patch can
+      only replace which material an existing appearance references (materials/material definitions
+      themselves cannot be overwritten by a patch); a `.ent` patch can touch `appearances`,
+      `components`, `entity` and `visualTags`; a `.app` patch can touch `components`, `partsValues`
+      and `visualTags`, but explicitly cannot touch `partsOverrides`."
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/core-mods-explained/archivexl/archivexl-resource-patching/README.md,
+      section "What is the minimal patching level?"
+    tags:
+      - archivexl
+      - resource-patch
+      - mesh
+      - ent
+      - app
+      - limitation
+    detail: For hiding/showing submeshes on a `.app` (which would otherwise need `partsOverrides`), the
+      page points to ArchiveXL's tag-based conditional component un/loading instead.
+  - id: cp2077.archivexl.patch-component-replaces-on-name-and-id
+    claim: When ArchiveXL applies an entity-template patch (resource.patch), each patch component whose
+      name AND CRUID id both match a component of the target replaces that component; any other
+      patch component is appended. The log line says "replaced component in" or "added to". So to
+      change a template's existing component, the patch component carries the target component's own
+      name and id.
+    status: verified
+    source: https://github.com/psiberx/cp2077-archive-xl src/App/Extensions/ResourcePatch/Extension.cpp,
+      MergeComponents (the comparison resultComponent->name == patchComponent->name &&
+      resultComponent->id.unk00 == patchComponent->id.unk00)
+    tags:
+      - archivexl
+      - resource-patch
+      - entity-template
+      - component
+      - cruid

package/knowledge/cyberpunk2077/audio.events.yaml

@@ -0,0 +1,168 @@
+game: cyberpunk2077
+topic: audio.events
+title: .wem/.opuspak/.bnk audio layout and the REDmod event-override model
+facts:
+  - id: cp2077.audio.events.wem-holds-voiceover-and-most-music
+    claim: "\"The game stores voice-overs and most music as `.wem` files which are directly in the
+      game's `.archive`s and their exporting/importing is handled as any other asset.\""
+    status: community
+    source: wiki.redmodding.org "Audio files", section "Primary file types > WEM files"
+    tags:
+      - audio
+      - wem
+      - file-format
+    detail: Page title and section name corrected 2026-09-07 (the page is "Audio files" and has no "File
+      Types & Roles" heading).
+  - id: cp2077.audio.events.opuspak-needs-opusinfo-mapping
+    claim: '"Sound effects, grunts, and some music are packed together in files ending with `.opuspak`.
+      Those paks are mapped by a single `.opusinfo` file."'
+    status: community
+    source: wiki.redmodding.org "Audio files", section "Primary file types > Opuspaks and bnks"
+    tags:
+      - audio
+      - opuspak
+      - opusinfo
+      - file-format
+    detail: 'Note "a single `.opusinfo`" — one index covers the paks. The page links a separate
+      replacing-sound-effects guide for actually manipulating them. Corrected 2026-09-07: "an
+      individual sound cannot just be pulled from a .opuspak directly" is an inference the page does
+      not state.'
+  - id: cp2077.audio.events.bnk-describes-behavior-not-just-audio
+    claim: "Community page confirms cp2077.audio.sounds.event-name-to-wwise-id-is-a-simple-lookup.
+      \".bnk files are primarily for other purpose than storing audio. They describe how and which
+      the audio should be played.\" The playback chain is: the game sends an event to Wwise, \"those
+      are described in `eventsmetadata.json` file in the game's archives\"; the event connects to a
+      tree of nodes in `.bnk` files (random next-node selection, layering, volume modification,
+      conditional switching); the last node points at an audio file or a plugin."
+    status: community
+    source: wiki.redmodding.org "Audio files", section "How are SFX handled by the engine"; embedded
+      audio from section "Primary file types > Opuspaks and bnks"
+    tags:
+      - audio
+      - bnk
+      - wwise
+      - node-tree
+      - eventsmetadata
+    detail: "Names cp2077.audio.sounds.event-name-to-wwise-id-is-a-simple-lookup
+      (knowledge/cyberpunk2077/audio.sounds.yaml), an inferred fact that already uses
+      `base\\sound\\event\\eventsmetadata.json` as the offline event-name-to-Wwise-ID lookup; this
+      page confirms that file is where the engine's events are described. The sibling
+      cp2077.audio.sounds.event-id-to-wem-sample-is-not-a-simple-lookup is the other half — the
+      event-to-source mapping in a bank's HIRC section — and this page agrees the bank is where the
+      tree lives. Also: \"Few sounds, mostly car noises, are so-called preloaded (or embedded) in
+      `.bnk` files, they're mostly duplicated and can be found elsewhere, but some sounds are only
+      preloaded.\""
+  - id: cp2077.audio.events.some-bnk-audio-not-fully-extractable
+    claim: VGMStream "is able to extract some of them, but not all, because they differ in audio
+      format". Separately, "Some sounds ... are handled differently. For example generated (noise,
+      sine wave, etc.), or generated by CDPR's custom Wwise plugins" — those have no extractable
+      source file.
+    status: community
+    source: wiki.redmodding.org "Audio files", section "Primary file types > Opuspaks and bnks"
+    tags:
+      - audio
+      - bnk
+      - vgmstream
+      - procedural
+      - gotcha
+    detail: Section name corrected 2026-09-07 (there is no "Key Gotchas" heading).
+  - id: cp2077.audio.events.voiceover-subtitles-mapped-by-string-id
+    claim: '"Every subtitle in the game has a String ID (which is a really long number) that is
+      universal between languages. What `.wem` audio file belongs to which String ID is mapped
+      inside files starting with `voiceover` and ending in `.json`", and further `.json` files in
+      the `subtitles` folders hold the subtitle text for each String ID.'
+    status: community
+    source: wiki.redmodding.org "Audio files", section "How are voice-overs connected to subtitles"
+    tags:
+      - audio
+      - subtitle
+      - string-id
+      - localization
+    detail: Some `voiceover*.json` files cover holocall voice-overs, some the helmet-on case; the
+      subtitles folders hold "few thousands" of files, so the page recommends searching them via
+      SoundDB (sounddb.redmodding.org) instead. Same String IDs as the `locstringIds` in
+      cp2077.quests.scenes.subtitle-edit-needs-two-resources, reached from the scene side. Section
+      name corrected 2026-09-07.
+  - id: cp2077.audio.events.redmod-is-event-override-not-file-replace
+    claim: '"REDmod allows you to add new and override existing audio events... This will not override
+      `.wem` files; it will instead override audio events, which are what use `.wem` files. That
+      way, you can override events that layer or randomize between multiple sounds without manually
+      altering each sound." The cost: "any events added or overridden will use a different Wwise
+      event, removing any special parameters and Wwise logic attached (e.g. overriding a gun sound
+      event will result in it no longer receiving time-dilation effects processing)."'
+    status: community
+    source: 'wiki.redmodding.org "Audio Modding: Redmod", section "Summary"'
+    tags:
+      - audio
+      - redmod
+      - wwise
+      - event-override
+      - gotcha
+    detail: Page title and section name corrected 2026-09-07 (there is no "Event-Override Model" heading).
+  - id: cp2077.audio.events.redmod-custom-sound-folder-layout
+    claim: '"Place raw `.wav` audio files inside `<Cyberpunk 2077>/mods/<name>/customSounds`. Include a
+      `info.json` file with your mod (`<Cyberpunk 2077>/mods/<name>/info.json`) where you sepcify
+      how to use your custom sounds. You may use nested folders with `\\`."'
+    status: community
+    source: 'wiki.redmodding.org "Audio Modding: Redmod", section "Audio Modding - Manually"'
+    tags:
+      - audio
+      - redmod
+      - customsounds
+      - info.json
+      - file-structure
+    detail: 'The `info.json` top level carries `name`, `version` and the `customSounds` array; the
+      nested-folder example is `"file": "mysounds\\new_sound.wav"`. Section name corrected
+      2026-09-07.'
+  - id: cp2077.audio.events.info-json-required-and-optional-fields
+    claim: "A `customSounds` entry's parameters: `name` (String) \"The game audio event to override\";
+      `type` (String) the sound type; `file` (String) \"The `.wav` file to use (inside
+      `/customSounds`)\"; `gain` (Float) \"How loud the sound is; ranges from 0 to 1\"; `pitch`
+      (Float) \"The amount of pitch variance applied to the sound; ranges from 0 to 1\". `file` is
+      omitted for a `mod_skip` entry, which plays nothing."
+    status: community
+    source: 'wiki.redmodding.org "Audio Modding: Redmod", section "Parameters" and the example
+      `info.json` under "Audio Modding - Manually > Example"'
+    tags:
+      - audio
+      - redmod
+      - info.json
+      - required-field
+      - syntax
+    detail: "Corrected 2026-09-07: the previous claim listed `file` as always required, which the page's
+      own example contradicts — its `amb_bl_eq_medical_electronics_small` and
+      `w_gun_revol_power_overture_fire_suppressor` entries carry only `name` and `type: mod_skip`."
+  - id: cp2077.audio.events.redmod-sound-type-vocabulary
+    claim: The `type` options are `mod_skip` ("Do not play this sound event"), `mod_sfx_2d` ("played
+      without any positions / attenuation"), `mod_sfx_city` ("longer attenuation... suitable for
+      city sounds"), `mod_sfx_low_occlusion` ("long attenuation that isn't occluded much e.g. a VO
+      or quest sound that you don't want to be muffled"), `mod_sfx_occlusion` ("Medium attenuation
+      with normal occlusion"), `mod_sfx_radio` ("Needs to be tuned to a broadcast channel"),
+      `mod_sfx_room` ("shorter attenuation suitable for something that can be heard across a room"),
+      `mod_sfx_street` ("medium attenuation, good for something to be heard down a street") and
+      `mod_sfx_ui` ("For menu and UI sound replacement").
+    status: community
+    source: 'wiki.redmodding.org "Audio Modding: Redmod", section "Parameters" (the `type` bullet list)'
+    tags:
+      - audio
+      - redmod
+      - sound-type
+      - mod_skip
+      - enum
+    detail: 'Corrected 2026-09-07: "there is no custom/free-form type" was trimmed — the page presents
+      these as the options without saying the set is closed.'
+  - id: cp2077.audio.events.wolvenkit-sound-modding-tool-alternative
+    claim: "\"The REDmod sound import tool can be used in a WolvenKit project\": add the `.wav` files to
+      the project's `/customSounds` folder, click Tools > Sound Modding Tool, choose which event to
+      mod from the list of game sound events, adjust the parameters in the bottom right, and click
+      Save."
+    status: community
+    source: 'wiki.redmodding.org "Audio Modding: Redmod", section "Audio Modding - WolvenKit Integration"'
+    tags:
+      - audio
+      - redmod
+      - wolvenkit
+      - sound-modding-tool
+    detail: 'Corrected 2026-09-07: "equally valid paths to the same result" was trimmed — the page
+      documents both routes without ranking them. Section name corrected (there is no
+      "Implementation Methods" heading).'

package/knowledge/cyberpunk2077/audio.sounds.yaml

@@ -0,0 +1,164 @@
+game: cyberpunk2077
+topic: audio.sounds
+title: Weapon audio — anim-baked events vs TweakDB impact profiles
+facts:
+  - id: cp2077.audio.sounds.two-independent-audio-systems-per-weapon
+    claim: "A melee weapon's audio comes from two completely independent systems that can disagree:
+      swing/handling/equip/block-ring sounds are anim events baked into the weapon's .anims clips,
+      while hit/impact/flesh/ block sounds come from the TweakDB audioWeaponConfiguration field on
+      the weapon record. Changing one has no effect on the other."
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - anim-event
+      - tweakdb
+      - impact
+      - architecture
+    detail: "Discovered auditing a report that a weapon's sounds were \"just the katana\": it was worse
+      than that — the weapon played katana swings over kukri impacts, because the swing side came
+      from re-authored katana donor clips and the impact side was inherited TweakDB, and nobody had
+      touched either deliberately."
+  - id: cp2077.audio.sounds.audio-impact-profile-inherited-through-base
+    claim: A weapon's impact audio profile can be silently inherited from its $base preset chain rather
+      than set on the weapon's own record; check the full inheritance chain, not just the leaf
+      record, when auditing which profile is actually live.
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - tweakdb
+      - inheritance
+      - base-record
+    detail: A melee weapon mod's record, Items.<ModWeapon> ($base Items.Preset_Machete_Default),
+      inherited audio_melee_metadata_kukri_voodoo with no explicit line anywhere in the mod's yaml
+      setting it — the audit had to trace the $base chain to find where it came from.
+  - id: cp2077.audio.sounds.audioweaponconfiguration-hot-reloads
+    claim: Changing a weapon record's audioWeaponConfiguration field is a yaml-only edit that
+      hot-reloads via TweakXL.Reload() in the CET console, with no archive rebuild and no game
+      restart required.
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - tweakdb
+      - hot-reload
+      - tweakxl
+    detail: "Confirms the general tweak hot-reload path (cp2077.process.tweakxl-hot-reload) applies
+      specifically to this audio-routing field. The applied swap sets audioWeaponConfiguration:
+      audio_melee_metadata_borg_machete, deployed and hash-verified 2026-09-03; the user's ear
+      judgment on the result was still pending as of that note."
+  - id: cp2077.audio.sounds.anim-baked-events-never-hot-reload
+    claim: Renaming or changing the anim events baked into a weapon's .anims file (the
+      swing/handling/equip side of weapon audio) requires an archive repack and a full game restart,
+      because .anims assets never hot-reload the way TweakDB yaml does
+      (cp2077.anims.sets.do-not-hot-reload).
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - anim-event
+      - anims
+      - hot-reload
+      - restart
+    detail: The note frames this as the reason to try the impact-profile swap (yaml-only) first as the
+      cheap A/B, since it "may be most of what you want" before paying for a repack+restart cycle on
+      the anim-event side.
+  - id: cp2077.audio.sounds.event-name-to-wwise-id-is-a-simple-lookup
+    claim: Mapping a named audio event (e.g. w_melee_katana_whoosh) to its Wwise event ID is a simple,
+      fully offline lookup via base\sound\event\eventsmetadata.json.
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - wwise
+      - event-id
+      - lookup
+    detail: Table of 11 weapon-specific katana events extracted this way, e.g. w_melee_katana_whoosh ->
+      4107381959, w_melee_katana_equip -> 1337780739. 60 of the anim set's 97 clips carry audio
+      events at all; the rest are generic (block/parry/fast_whoosh) or foley (AnimEvent_FoleyAction
+      lcm_mvs_* cloth/movement, 67 uses).
+  - id: cp2077.audio.sounds.event-id-to-wem-sample-is-not-a-simple-lookup
+    claim: "Unlike event-name-to-Wwise-ID, mapping a Wwise event ID to its actual .wem audio sample is
+      NOT a simple offline lookup: weapon SFX are loose .wem files streamed by source ID, and the
+      event-to-source mapping lives in the HIRC section of a binary Wwise soundbank (init.bnk),
+      which this project's tooling cannot parse."
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - wwise
+      - wem
+      - soundbank
+      - blocker
+    detail: The 201 .bnk files in audio_2_soundbanks.archive are almost all vehicles plus init.bnk. The
+      note explicitly frames hand-parsing a Wwise soundbank as exactly the kind of
+      undocumented-binary work to time-box and hand to a community tool instead — here, the
+      WolvenKit GUI audio browser (browse/play/export .wem) plus vgmstream/ww2ogg for .wem -> .wav
+      conversion.
+  - id: cp2077.audio.sounds.audio-metadata-profile-shape
+    claim: A complete per-weapon audio impact profile in
+      base\sound\metadata\cooked_metadata.audio_metadata exists as BOTH an
+      audioMeleeWeaponConfiguration entry and an audioMeleeWeaponVariations entry; a profile missing
+      either half should be treated as incomplete before assigning it to a weapon.
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - tweakdb
+      - profile
+      - metadata
+      - verification
+    detail: The audit explicitly verified audio_melee_metadata_borg_machete has both shapes, "the same
+      shape as the kukri_voodoo it replaces," before applying it — treating shape-completeness as a
+      precondition, not an assumption.
+  - id: cp2077.audio.sounds.new-wem-audio-needs-redmod-sound-pipeline
+    claim: Getting modified or new audio samples into the game (as opposed to reassigning which existing
+      vanilla event/profile a weapon uses) requires REDmod's sound pipeline — a REDmod module
+      shipping .wem + info.json — not ArchiveXL; this is a deployment path the mod does not
+      currently use at all.
+    status: unverified
+    source: ModWright research
+    tags:
+      - audio
+      - redmod
+      - wem
+      - pipeline
+      - plan
+    detail: Framed explicitly as a future phase, budgeted separately, "only after Route A proves
+      insufficient." No attempt at this path is recorded.
+  - id: cp2077.audio.sounds.vanilla-family-has-deeper-whoosh-variants
+    claim: The katana audio family already ships heavier/deeper variant events for whoosh and handling
+      sounds (e.g. w_melee_katana_whoosh_large, w_melee_katana_handling_strong) that can be
+      substituted by simple rename with no new audio authoring, if a reskin needs to go further than
+      the impact-profile swap alone.
+    status: inferred
+    source: ModWright research
+    tags:
+      - audio
+      - katana
+      - whoosh
+      - variant
+      - reskin
+    detail: "w_melee_katana_whoosh -> w_melee_katana_whoosh_large (1670341267);
+      w_melee_katana_handling_soft -> w_melee_katana_handling_strong (275000592). Other whoosh
+      families available as impact-profile alternatives if borg_machete is not heavy enough: machete
+      (_heavy), blade (_normal), cut_o_matic (_low), blunt (_heavy/_low), sledgehammer,
+      boss_sledgehammer, caretaker_shovel (_heavy). None of this was applied as of the audit;
+      recorded as available inventory."
+  - id: cp2077.audio.sounds.donor-clip-anim-events-inherited-unintentionally
+    claim: When a weapon's attack animations are re-authored from a donor weapon's clips (rather than
+      newly authored), the donor's baked audio events come along for free and unintentionally — the
+      resulting weapon sounds like its animation donor, not its own identity, until someone audits
+      and reskins the events deliberately.
+    status: verified
+    source: ModWright field verification
+    tags:
+      - audio
+      - anim-event
+      - donor
+      - reskin
+    detail: The weapon's light-attack clips are re-authored katana clips (see the shared animation work,
+      out of scope here), so all of their baked audio events are still w_melee_katana_*. This is the
+      mechanism behind cp2077.audio.sounds.two-independent-audio-systems-per-weapon's swing side
+      specifically.