chore: FCS bump b21433ecc + harness [3c.3] enmity tables section

[logicallysynced]

Summary

Two commits ahead of main:

• 3c274c0 — chore: bump FCS submodule 5d3840d68 → b21433ecc (two upstream commits: routine struct refresh + a comments-only addition for EventSystemDefine)
• 988d9bb — harness: add [3c.3] ENMITY TABLES section — always show both lists

FCS bump (3c274c0)

Latest upstream commits since the previous pin:

b21433ecc Add names from EventSystemDefine as comments
e04ec6b37 Update structs

Nothing that touches public-API names, field layouts, or anything Sharlayan reflects against. Sharlayan.dll size unchanged at 10980 KB; all 189 tests still pass; harness builds clean.

Verified Lumina 7.5.0, Lumina.Excel 7.4.3, NLog 6.1.3, Newtonsoft.Json 13.0.4, and ILRepack.Lib.MSBuild.Task 2.0.45 are all at latest stable via dotnet list package --outdated — nothing else to bump. No open Dependabot PRs.

Harness enmity section (988d9bb)

The harness previously surfaced enmity only via TargetInfo.EnmityItems, which Reader.Target.cs:111 gates behind CurrentTargetID > 0 — so the table was invisible whenever the player had no target. Two distinct enmity-related structures exist on UIState and both deserve visibility for testing:

List	Source	Surface	What it represents
AGGRO	UIState.Hater._haters (AGROMAP_KEY / AGRO_COUNT_KEY)	PlayerInfo.EnmityItems	"Who is aggro'd ON the player"
HATE	UIState.Hate._hateInfo (ENMITYMAP_KEY / ENMITY_COUNT_KEY)	TargetInfo.EnmityItems (gated)	"The player's own hate table"

The new [3c.3] ENMITY TABLES section:

• Logs CanGetAgroEntities / CanGetEnmityEntities capability flags so a stripped scan (missing signature) is obvious at a glance.
• AGGRO list — prints PlayerInfo.EnmityItems plus the raw HaterCount for cross-check.
• HATE list — reads ENMITYMAP_KEY directly using HateItem offsets, bypassing the target gate so the data is always visible. Names are resolved against GetActors() since hate entries store only ID + Enmity in memory.
• Engaged actors — top 10 actors with IsAgroed || InCombat set, independent of either table, as an eye-check that ActorItem.IsAgroed (CharacterData.Flags bit 1) lights up correctly.

The earlier TargetInfo.EnmityItems print in [3c] is kept and now annotated to point at [3c.3] so it's clear why the same data shows up twice in different forms.

Version

9.0.38 → 9.0.39 (Sharlayan source changed via the FCS submodule bump; harness-only change in 988d9bb does not bump per policy).

Test plan

• pwsh .\build.ps1 clean — 0 warnings, 0 errors.
• dotnet test — 189 / 189 pass.
• dotnet list package --outdated — no available updates.
• Debug DLLs deployed to Chromatics Build Dependencies/Sharlayan/.
• Run pwsh .\harness.ps1 against a live client and verify [3c.3] shows the AGGRO and HATE lists with sensible counts when engaged and empty otherwise.

🤖 Generated with Claude Code