Four defects, all in code that accepted something it should have refused.

`parsePrNumber` ran `Number(raw)` past an integer check, so `007`, `7.0`, `7e0`,
` 7`, `+7` and `0x7` all became 7. A dispatch on `007` then computed the
concurrency group `review-007`, which supersedes nothing and lets two passes
write the same comment surface. The raw string now has to match
`^[1-9][0-9]*$` before it is parsed.

`REVIEW_SERVICE_URL` was only checked for emptiness before the capability token
rode an Authorization header to whatever it named. It now has to parse as an
`https:` URL, and the new optional `expected-service-origin` action input pins
the origin exactly when a caller sets it.

Nothing read the pull request's state, so a `workflow_dispatch` for a closed or
merged PR was reviewed like any other. The dispatch arm now refuses anything
that is not open and unmerged, and refuses with a distinct error when the forge
returns neither field rather than guessing.

A runtime 403 or 404 from the resolve endpoint was logged as "resolution is
unavailable on this instance", which is false on a `-j4k` server the version
probe just confirmed serves the route. The classification now follows the probe:
on a `-j4k` instance the failure is reported as a refusal, quoting the status and
the endpoint, and "unsupported" is left for instances whose probe found no
`-j4k`. Either way the pass still degrades to replies rather than failing the
run.

`dist/index.mjs` is rebuilt to match.

@@ -64,0 +71,7 @@
+  if (shape.status !== 403 && shape.status !== 404) {
+    return undefined;
+  }
+  const endpoint = typeof shape.url === "string" ? shape.url : "an unrecorded endpoint";
+  if (!serverSupportsResolution) {
+    return {
+      reason: "unsupported",

@@ -64,0 +65,5 @@
+  if (shape.status !== 403 && shape.status !== 404) {
+    return undefined;
+  }
+  const endpoint = typeof shape.url === "string" ? shape.url : "an unrecorded endpoint";
+  return `review-wrapper: the forge refused conversation resolution with HTTP ${shape.status} from ${endpoint}; the version probe reports a -j4k instance, so the route exists and the task token is not allowed to use it — projecting replies only for the rest of this pass`;

@@ -43,6 +48,6 @@
 function parsePrNumber(raw: string | undefined): number {
-  const prNumber = Number(raw);
-  if (raw === undefined || !Number.isInteger(prNumber) || prNumber <= 0) {
+  if (raw === undefined || !PR_NUMBER.test(raw)) {
     throw new Error(`workflow_dispatch input pr_number is not a positive integer: ${String(raw)}`);
   }
-  return prNumber;
+  return Number(raw);
+}