A capacity setting away from its default is one line beside it on the capacity page, and the sentinel files no issue for it #3269

Intent: the direction's "a setting is one line where it belongs": no issue like #2505 on the board for a setting the owner chose.

Done:

• [ ] settingsAway in src/crew/sentinel.ts no longer becomes a finding issue; the capacity page (src/web/pages/capacity.ts) shows, beside each setting away from its default, one muted line "changed from <default> <N> days ago by <who> · Put back".
• [ ] Open setting: findings close on the next sentinel pass with a comment pointing at the capacity page; isSettingFinding callers keep working for closed ones.
• [ ] Tests: the line renders (escaped) for a changed setting and not for a default one; the sentinel files nothing for a changed setting; an open finding closes.

Files: src/crew/sentinel.ts, src/crew/setting_finding.ts, src/web/pages/capacity.ts, their tests. Risks: losing the reminder entirely; the line stays until the value is back at default. Fits: any builder on the crew (scout, mason or torque); a person assigns.

Parked by the crew: the check failed ("the board's forge strip > the sentinel's line is the admin's alone, and absent before the first hunt") and the decider saw no point in another try (pull #3294 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.