Name the template owner in the -v variables block

[max-sixty]

The question

When wt shows a template variables: block under -v, does it say which template the variables belong to? Mostly no — and in one case it genuinely can't be worked out from the header.

What was there

Four sites print a variables listing, and none named its owner in the header:

Site	Header	How you'd tell what it's for
foreground hook (command_executor.rs)	template variables:	the hook_type row at the bottom of the table, or the Running … line below it
background hook (hooks.rs)	template variables:	same — but see below
alias (alias.rs)	template variables:	only the Running alias greet line below it
wt step eval (eval.rs)	Available template variables	unambiguous (one template, named on the command line)

The adjacent blocks in the same -v lane already label themselves — ○ eval source, ○ user:noop result — so the variables table was the odd one out in its own family.

Background hooks turned that from inconvenient into ambiguous. wt -v remove <branch> prints one table per hook type back to back, then a single combined Running post-remove: cleanup (user); post-switch: notify (user) line — two identical headers over two ~20-row tables that differ only in their rows.

The change

Prefix each header with the hook type, alias name, or eval.

- ○ template variables:                 ○ post-remove template variables:
- ○ template variables:                 ○ post-switch template variables:

wt step eval -v now reads as one labeled family:

○ eval template variables:
  branch = feature/auth-oauth2
○ eval source
  {{ branch }}
○ eval result
  feature/auth-oauth2

eval's header was reworded from Available template variables for the same shape; it was never ambiguous, but it's the fourth member of the family and now matches the source / result headers directly beneath it.

Display-only — no logic changed. Snapshots and the generated step.md pages regenerated; cargo run -- hook pre-merge --yes green (4461 tests).

This was written by Claude Code on behalf of Maximilian Roos

🤖 Generated with Claude Code