ui(free): explain partial outcomes in merchant language (#281)

[MrDarkRoot]

Summary

• Merchant outcome lines on the job summary, item cells, and History outcome column. Typed status stays in Details. item_label() and result_summary() contracts are unchanged.
• Counts come from persisted job/item rows, not the progress percent. Next step names Resume, fresh Preview, or Undo only when that existing control is already available. Viewing does not POST. Failures are not described as rollbacks. Undo is not a full rollback.
• No planner, journal, nonce, capability, or job-execution changes.

Copy

Status	Old headline	New headline	Claim kept
APPLIED	Changed	Changed	saved change
UNCHANGED	Already at the target price	Not changed	no change
UNSUPPORTED	Skipped at preview	Skipped	skip only; no stored SKIPPED
CONFLICT	Not changed	Newer price kept	newer value left unchanged
FAILED	Needs attention; not changed	Not changed; needs attention	not a rollback
NEEDS_REVIEW	Outcome uncertain; needs checking	Needs review; outcome uncertain	uncertain, not success

Tests

• php wordpress/tests/admin/outcome-copy-unit.php PASS (includes progress-unit, 165 checks)
• php -l PASS
• bash .github/ci/pr-fast.sh PASS (#133 PR_FAST PASS)
• Woo/browser suite not run here (no Docker). Hosted Admin must rerun WriteLeash Admin: real-browser accessibility and safety regression gate before RC #170 against this head.

Do not merge. Only @MrDarkRoot reviews and merges. PR_FAST and CI_COVERAGE must be green.

Closes #281