Menu
Verify TAOM's Harmony patch, GameModel, and reflection bindings against the installed Bannerlord engine and refresh the committed API snapshot. Use after an engine update or patch change.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.
| name | verify-bindings |
| description | Verify TAOM's Harmony patch, GameModel, and reflection bindings against the installed Bannerlord engine and refresh the committed API snapshot. Use after an engine update or patch change. |
| argument-hint | ["check|refresh|full"] |
Re-verify that TAOM's engine touchpoints still bind against the installed Bannerlord version, and keep the committed v1.4.5 signature snapshot in sync. This is the standing, offline form of the migration S6 smoke-test gate.
Full background: docs/reference/taleworlds-api-snapshot/README.md.
Taom*Model GameModel, or a string-name reflection site against an engine member.$ARGUMENTS = check → run the binding gate only (Step 1).$ARGUMENTS = refresh → regenerate the snapshot only (Step 3).$ARGUMENTS = full or empty → all steps.BANNERLORD_GAME_DIR (or BANNERLORD_OVERRIDE_DIR) must point at the install — the gate loads the SandBox/CustomBattle/StoryMode module DLLs from there. If unset, the gate self-reports Assert.Inconclusive (it does not falsely pass). This is an environment fact to report, not fix (see .claude/rules/environment-failures.md).
dotnet test TAOM.Tests/TAOM.Tests.csproj -p:DisableModuleCopy=true --filter "TestCategory=BindingVerification"
Three test classes under TAOM.Tests/Migration/:
HarmonyPatchBindingTests — every [HarmonyPatch] / TargetMethod target resolves as Harmony resolves it.GameModelOverrideBindingTests — every Taom*Model is registered in SubModule.cs, overrides ≥1 base virtual, and doesn't shadow a base virtual without override.ReflectionSiteBindingTests — each catalogued auxiliary reflection member resolves.A red gate is a real finding — one of three classes. Fix at the source, do not silence the test:
| Failure message | Root cause | Fix |
|---|---|---|
AmbiguousMatchException on a patch | name-only [HarmonyPatch] on a method overloaded anywhere in the type hierarchy | pin argument types: [HarmonyPatch(typeof(X), "M", new[] { typeof(...) })] (the documented HarmonyLib way) |
target/member did not resolve / not found | engine renamed/moved/removed the member in this version | /research the new signature, update the patch / adapter / GameModel; if a reflection site, update both reflection-sites.md and the [DataRow] |
GameModel never AddModel'd | a Taom*Model compiles but isn't registered | add campaignStarter.AddModel(new TaomXModel(...)) in Main/SubModule.cs |
If the fix needs an unknown TaleWorlds signature, hand off to /research first. If it's a deeper "why did this break" question, use /investigate.
pwsh tools/snapshot_api_surface.ps1
Regenerates docs/reference/taleworlds-api-snapshot/{gamemodel-bases,patch-targets}.md from the installed DLLs (auto-derives the type list from TAOM.dll). Then prove reproducibility:
pwsh tools/snapshot_api_surface.ps1 -Check # exit 0 = committed files reproduce
Add a row to reflection-sites.md Category B and a matching [DataRow] in ReflectionSiteBindingTests.cs. Runtime-dynamic sites (instance.GetType()) go in Category C (not gated) and onto the punch-list instead.
The gate is offline-only. Patch application, prefab visual order, ruler equipment, alliance behaviour, naval safety, and dynamic-reflection CC flow need a running game — itemized in docs/migration/s6-runtime-punchlist.md. Surface these to the user; do not claim them verified from a green gate.
Report: gate result (pass/fail with the per-finding class for any failure), whether the snapshot reproduced (-Check exit code), and any open punch-list items the change implicates. Update docs/migration/TRACKING.md and CHANGELOG.md if bindings were fixed.