fix(review): skip the cost hold when the owner already recorded the cost decision #9403

Refs: #9276, #9224

Problem

The code-review lane's cost hold (#9342, ci-workflows v0.64.1 apply-review-hold) runs again on every new head. It adds needs-human even when the owner has already recorded the cost decision for that PR, as a **Decision recorded.** Cost: comment on the closing issue, which is the #9224 rule.

Seen on #9332:

• The owner removed the label at 13:15:47Z after his Q50 decision (feat(pr-pipeline): restore Refine as its own stage that tidies every PR before review #9306 (comment)).
• A base merge pushed a new head, and claude-review added the label back at 13:20:21Z (feat(pr-pipeline): restore pr-refine as the refine stage for fix-docs #9332 (comment)).

Every later base merge repeats this, so the owner is pulled back into a loop he has already closed.

Done when

• A review lane does not apply a cost hold when the PR's closing or linked issue carries an owner-authored **Decision recorded.** Cost: comment newer than the PR's createdAt. The babysit merge gate already reads this, in babysit_risk.py's cost rule.
• The owner check uses the same author rule as the babysit cost gate: the owner's account, unedited, not an agent login.
• A test covers it: a cost-class change with a recorded decision gets no hold; without one, it is held.
• Holds for the trust-gate and critical-security classes are unchanged.

Where

The /review:code-review skill's hold criteria (plugins/review, #9342) and/or the hold step's deterministic inputs. Pick the place that can read the issue comment reliably. A skill instruction alone is model judgment; prefer a deterministic check in the hold step or the ci-status gate.