fix(web): a status name is not a category — stop guessing "done" (GDK-272)

[midagedev]

RESOLVED_STATUS_NAMES held resolved/closed/done/해결됨/종료/완료, and
two readers consulted it whenever the server sent no category: effectiveCategory
returned done on a name match, and HistoryTimeline's local isReopen painted a
reopen badge from isResolved(from) && !isResolved(to).

This is the trap the repo names first. status = 'In Progress' is silently zero
rows on a Korean account; docs/STATE_OF_PLAY.md hard-won #4 says a reopen is a
done-category → non-done transition and never a name match. The set's own
comment claimed it kept "only generic names that mean the same on every Jira" —
완료 is not a generic name, so the premise contradicted itself.

It was not dead code

internal/server/read.go:445 fills from_category from
view.categories[FromID], and read.go:650 seeds that map only from status ids
a currently-mirrored issue occupies. Any status the issue passed through that
nothing currently holds — a status removed from the workflow, say — arrives with
no category, and the name decides.

So it also broke on an English site with a custom done status ("Verified",
"Shipped"), not only on a third language. The audit round rated this
medium-confidence; verifying that seeding path is what promoted it to a
confirmed Highest defect.

What changed

• effectiveCategory trusts a real new|inprogress|done and otherwise returns
  inprogress. No name is consulted.
• isReopen moved into view-config.ts as the single owner of the reopen
  rule, and returns false when both categories are empty: an unpainted badge is a
  missing hint, a wrongly painted one is a false claim about the issue's history.
• matchesIdFirst's name fallback is deliberately untouched — that is the
  documented compatibility path for legacy saved views, a different decision.

Recurrence, and a correction to my own spec

tools/doc-checks.sh now matches '해결됨', '종료', '완료' as display-name
literals in web logic. Its old comment said this table was "deliberately not
matched (would fail the current tree; sibling issue)" — the round found that was
only a comment, not a grep exclusion; view-config.ts was already in the scan
path. So the work was adding patterns that catch the table, not removing an
exemption. My spec had that wrong and the round said so.

Lowercase done/resolved/closed stay out of the pattern on purpose: they are
also category keys and other-field values (a RangeField resolved, a GitHub PR
closed).

FAIL-first run by me: reintroducing new Set(['완료', '해결됨']) into
view-config.ts makes doc-checks fail and name the file and line; removing it
returns exit 0.

effectiveCategory had no unit test at all before this. 11 new cases now
cover the trusted values, an empty category with a Korean status name, 'Done',
a custom 'Shipped', and the reopen predicate.

Debuggability

The failure mode was silence — nobody could tell a category was missing and
something guessed. missingStatusCategorySeen() counts how often a category
decision ran without a category. Integer increment, no per-row logging.

Gates (lead, cold)

svelte-check 4250 files / 0 errors · vitest 34 files / 347 tests (was
336) · tools/doc-checks.sh all passed · Playwright 240 passed (mandatory
here — web/ changed).

Closes GDK-272.

🤖 Generated with Claude Code