[worktrunk-bot]

Two recipes on the Tips & Patterns page fail when copied. This PR fixes both, adds a test that runs the database recipe straight from the page, and makes the hook-output JSON report real branch names so the log recipes can scope to the current branch.

• Database per worktree: the set-vars step passed three KEY=VALUE pairs to one wt config state vars set, which accepts exactly one (error: unexpected argument 'port=…' found). Because the step failed, vars.container and vars.port were never set for the db step or pre-remove. The step now runs three vars set calls chained with &&. The recipe also stored db_url, and vars keys have rejected underscores since fix: reject underscore in vars keys (invalid git config variable name) #2285 (Git config variable names can't contain them). It's now db-url, in the vars get example too. fix: use underscores in db_url var key examples #1848 had moved this key from hyphens to underscores because Jinja parses vars.db-url as subtraction. That doesn't apply here: the recipe reads the key only with wt config state vars get db-url, never in a template.
• Monitor hook logs: wt config state logs get --hook=user:post-start:server and the wtlog alias built on it fail with unexpected argument '--hook', because refactor(config-state): structured JSON for logs; drop --hook/--branch filters #2161 removed that flag. Its replacement, a jq filter over wt config state logs --format=json, couldn't scope to the current branch. The JSON branch field was the sanitized log directory (feature/x became feature-x-<hash>), so the help example used startswith and head -1 and tailed whichever worktree's server log was newest.
• Hook-output JSON branch: the field now holds the real branch name. It maps each log directory back through sanitize_for_filename over the local branches, and is null when no local branch writes there: a deleted branch, a detached HEAD, or a directory two branches share. The recipes in the help and on the page match [.branch, .source, .hook_type, .name] exactly. The extending page's hook-log alias compared .branch with {{ branch | sanitize_hash }}, the on-disk form, and now passes {{ branch }} to jq with --arg, like its other values. The wtlog alias becomes a shell function taking the hook name.

test_doc_example_database_set_vars_step_runs pulls the set-vars step from the page's TOML block, runs it as a wt alias with wt on PATH, and checks the stored port. It fails on main with the argument error above. After the first fix it also caught the db_url rejection. test_logs_get_json_branch_is_unsanitized covers the branch mapping, including the deleted and shared-directory cases. I ran the new recipe by hand from a feature/x worktree next to an other/y worktree, and it tailed only the feature/x log.

The skills/ and plugins/ copies of the page are regenerated by test_docs_are_in_sync.

[worktrunk-bot]

The replacement hook-log recipe is no longer scoped to the current branch. The removed wt config state logs get --hook=user:post-start:server resolved the current branch, with --branch as the override. wt config state logs --format=json lists hook_output for every branch's subtree under .git/wt/logs/, sorted newest first. Take a repo where several worktrees each run a server post-start hook: tail -f / wtlog server then follows whichever worktree wrote its log most recently, not the one the user is in. That is the usual setup for the per-worktree dev-server pattern this page describes.

A plain branch filter is harder than it looks, because .branch is the sanitized directory name. A name that isn't already filename-safe gets a hash suffix: feature/x is stored as feature-x-<hash>. So select(.branch == "$(git branch --show-current)") misses those branches, and a startswith on a tr / - form can also match a sibling such as feature-x2. The wt config state logs --help example (src/cli/config.rs, "Path to one hook log (e.g. the post-start server hook for the current branch)") has the same gap and claims current-branch scoping that its jq doesn't do.

A maintainer should choose between two options: document the recipe as picking the newest matching log across all branches, or add a branch filter to the JSON output. The second could be an unsanitized branch value or a current-branch --branch option, which would restore what #2161 dropped. I haven't pushed a fix because this changes the output format.

[worktrunk-bot]

The hook-log alias now splices {{ branch }} into a jq string literal inside a single-quoted shell program. Aliases render with POSIX shell escaping, so a branch name that needs quoting ends the single quote early. Git accepts a"b (git check-ref-format --branch 'a"b'), and that branch renders as ["'a"b'", $kind, $name], which is a shell syntax error. Before this change, sanitize_hash rewrote the ", so this is a regression. Pass the branch through --arg like the other values and leave the placeholders unquoted, so wt's escaping yields exactly one argument each. The fix is below, and I'll push it with the regenerated mirrors.