Documentation Roadmap

The wiki should grow with proven public API surface, not ahead of it.

Near-term documentation work:

• connect the current FTK2.ModAPI source checkout to DocFX metadata generation;
• audit XML comments on public SDK types and fill meaningful gaps without changing behavior;
• synchronize first-mod and item/ability examples directly from ExampleMod;
• expand item gameplay-property pages when current source/audit results are available;
• update custom-ability pages after tooltip, equipped-action, combat-availability and native-execution acceptance tests close;
• add the real Nexus Beta URL after publication;
• mirror the main site's exact palette/logo/navigation language after the current site source is available.

Future public API work such as custom passives, statuses and traits should receive documentation only when that API milestone actually exists and is validated.