Wrapper tool hardening and cleanup

LOG_REFACTOR_CONTRACT.md

@@ -1,5 +1,71 @@
 You are improving CLI/build logs for a NWN asset toolchain.
 
+## Status Snapshot
+
+Current state as of 2026-05-13:
+
+- This work is largely implemented for the current `build-haks` path.
+- The app layer now exposes `--quiet`, `--verbose`, and `--debug`, and normal
+  mode prints compact music summaries instead of raw per-file mappings.
+- Detailed mapping output is available behind verbose logging, and app tests
+  cover the compact versus detailed presentation split.
+
+Remaining work:
+
+- continue applying the same presentation discipline to other command families
+  where raw pipeline output still leaks through
+- keep summary wording and phase naming aligned as new generated-asset stages
+  are added
+
+## Active Scope
+
+Logging remains an active priority, but no longer for `build-haks` alone.
+
+The next logging phase should target:
+
+- `build-topdata`
+- `validate-topdata`
+- `compare-topdata`
+- `build-wiki`
+- `deploy-wiki`
+- release wrapper flows that currently interleave raw shell/tool output
+
+## Current Findings
+
+The asset-side log refactor proved the presentation model. The remaining gap is
+uneven command coverage:
+
+- topdata and wiki commands do not yet have the same polished phase/summarized
+  output contract as `build-haks`
+- release scripts still emit long shell-oriented logs that are useful for CI
+  diagnosis but not shaped into the same structured presentation model
+- wrapper-side status lines and toolkit-side progress lines are not yet fully
+  harmonized
+
+## Deferred Scope
+
+Defer cosmetic-only logging work that does not improve operator clarity.
+
+For now, prioritize:
+
+- structured summaries
+- deterministic phase labels
+- stderr/stdout hygiene
+- parity between topdata/wiki flows and the existing build-haks presentation
+
+## Immediate Plan
+
+1. Reuse the existing verbosity model for topdata and wiki command families.
+2. Define concise normal-mode summaries for topdata build/validate/compare.
+3. Add deploy/build wiki progress summaries that surface:
+   - local pages scanned
+   - create/update/skip/drift counts
+   - manifest path
+4. Keep debug mode capable of exposing raw internal progress when diagnosis is
+   required.
+5. Extend app-layer tests to cover topdata/wiki presentation once those
+   commands adopt the structured output contract.
+
 Goal: Make the logs cleaner, prettier, less repetitive, and easier to understand, without hiding important diagnostics.
 
 Current issues: