v0.1.39

wtc 0.1.39

This release makes WTC easier to adopt with a small harness scaffold, clearer
guides and TUI recordings, and offline release notes for harness upgrades.

Features

• wtc harness init scaffolds six project-owned files. Generic collection
  instructions come from the CLI, and wtc docs exposes them outside a collection.
• The public README has collection, environment, secrets, and harness recordings
  using real commands against synthetic repositories.
• wtc open detects unstacked narrow layouts and repairs pane geometry.
  Narrow/wide transitions preserve running pane processes. A previously broken
  wide layout may still be classified as wide; switching to narrow and back repairs it.
• wtc release-notes reads the embedded release archive offline. Use
  wtc release-notes --since 0.1.35 to read newer releases in upgrade order,
  or wtc release-notes 0.1.39 to read this release.
• Release publishing requires a committed version-specific note and uses that
  same Markdown for the GitHub release body.

Harness upgrade

Pin 0.1.39 or newer for a config-only harness: 0.1.38 does not contain the
complete embedded instruction fallback or scaffold commands. Existing populated
harnesses keep their configuration and hooks. The small scaffold
is optional: it does not replace local policy or copy over an existing harness.
Review local instruction and skill overrides before moving duplicated generic
guidance to CLI defaults. Read wtc docs, inspect wtc skills diff, and retain
project-specific sections in overlays or harness-owned instructions.

For each CLI upgrade, run the target binary with
release-notes --since <old-pin> before changing the harness pin. Older installed
binaries cannot describe future releases. Review the changed commands, hooks,
and compatibility notes; update the pin and compatibility range together, then
regenerate the collection environment, install its tools, and render guidance.
Test the harness's affected hooks and workflows in a disposable collection.