Wrapper tool hardening and cleanup

CONFIGURATION_HARDENING_CONTRACT.md

@@ -1,5 +1,27 @@
 Create a long-term multi-repository hardening plan focused on making YAML configuration the authoritative source of truth.
 
+## Status Snapshot
+
+Current state as of 2026-05-13:
+
+- This hardening effort is active and partially complete.
+- YAML authority, strict config loading, and effective-config inspection are
+  implemented.
+- Major repository behavior now flows through normalized config, including HAK
+  layout, topdata packaging, extract behavior, autogen manifests, scripts, wiki,
+  and music datasets.
+- The remaining gaps are mostly about reducing legacy compatibility surface,
+  moving more tests to YAML fixtures, and deciding which residual toolkit
+  defaults stay intrinsic versus become explicit schema.
+
+Primary outstanding work:
+
+- reduce reliance on `nwn-tool.json` in tests and migration fixtures
+- keep pruning repository-shaped defaults that still live in code when they
+  should be surfaced as schema-backed settings
+- maintain docs/examples for `config effective` and the normalized key space as
+  the schema evolves
+
 # Goal
 
 Reduce hardcoded behavior across all repositories and toolkit code.