…3853)

* ci(review): auto-clear the gate after approvals on fork PRs

The review-signal clear job runs on pull_request_review, but for fork PRs that event's token is read-only — it 403s removing labels / setting the check, so a fork approval never cleared the gate (e.g. #3852 stayed blocked after a code-owner approved).

New review-clear workflow runs on workflow_run after Review signal completes for a review submission. From the base repo (write token, works for forks) it resolves the PR from the run head SHA and re-dispatches the review-signal flag logic, which reads the approval and clears the gate fork-safely. No loop: the dispatch run has event=workflow_dispatch, which this job's if-condition excludes.

* ci(review): remove the fork-broken clear job, unify clearing via review-clear

The old clear job ran on pull_request_review and could not write on fork PRs (read-only token → 403), so it never cleared fork approvals. review-clear.yml now handles clearing for all PRs via workflow_run + fork-safe flag re-dispatch. Remove the redundant clear job. Add a tiny review-anchor job that runs on approval so the Review signal workflow reliably completes (not skipped), guaranteeing review-clear's workflow_run fires.

The two are views of the same cut's settings, not separate destinations, so a
segmented toggle reads truer than a tab bar. Tests select the items by
role=radio + name since @astryxdesign/core 0.1.3 doesn't forward data-testid
(upstream fix facebook/astryx#3852).