skills(running-tend): weigh root-cause fix over lossy config workaround

[worktrunk-bot]

Adds a triage rule to running-tend capturing a maintainer-flagged bad case from the daily review-runs analysis.

The bad case

In #3390 (triage of #3389), triage of the ⚑ branch_worktree_mismatch flag shipped a docs-only PR recommending users reconfigure worktree-path = "{{ branch | basename }}". On #3390 the maintainer pushed back — "why do we drop the prefix?" — then explicitly asked to log it as a bad case and closed the PR.

Two problems the rule targets:

• Lossy workaround presented as the fix. basename collapses alice/foo and bob/foo to foo, colliding on one directory, whereas the default {{ branch | sanitize }} keeps them distinct (alice-foo / bob-foo). The collision downside only surfaced after the maintainer challenged it.
• Jumped to a docs workaround over the root-cause code fix. The proportionate fix was teaching the path-match check to tolerate a dropped namespace prefix, not asking every affected user to adopt a lossy template. The "docs-only, no risk" framing masked a bad recommendation — low code risk ≠ good guidance.

The rule

A new ### Weigh the root-cause fix before shipping a config/docs workaround subsection under Issue Triage, placed right after "Suggesting Aliases for Niche Feature Requests" (which encourages config-based deflection) as a tempering counterpoint: check whether a configurable workaround is lossy/foot-gunny, weigh a proportionate root-cause code fix first, and surface any recommended config's downsides up front.

Gate assessment

• Gate 1 (confidence): Critical — directly flagged by @max-sixty ("log this as a bad case"). 1 occurrence is sufficient at Critical.
• Gate 2 (magnitude): Targeted one-subsection addition; evidence bar met by the Critical maintainer flag.

Already recorded in the review-runs-tracking evidence log. Kept as a separate atomic PR from the open cargo-PATH skill note (#3361) — different concern, non-overlapping section.

_{Run 29081037464 · daily review-runs}