fix: copy PR URLs from durable records

[kunchenguid]

Intent

Abandon 3637. Have the crewmate who did the investigation start a clean slate PR. I wonder whether the fix should be that workers shouldn't report something like "PR 108". We should instruct it to always send full URL PRs whenever a PR is mentioned. Also, stop mandating a full URL - adjust the instruction there to something like: send full PR URL if you have one in the records, otherwise only report whatever identifier you do possess. Ask whether what I am proposing would be a sufficient fix.

Closed: #3637
Investigation: data/fm-supervision-url-hallucination-cause-s1/report.md

What Changed

• Require workers to report full forge-provided PR URLs whenever mentioning a PR.
• Make supervision copy PR URLs verbatim from durable records and otherwise report only the available identifier without arming PR checks.
• Align operational guidance, documentation, and regression coverage with the copy-or-abstain policy.

Risk Assessment

✅ Low: The change is limited to aligned worker and supervisor instructions plus behavioral checks of generated prompt output, with the previously unrequested enforcement fully removed.

Testing

Completed 1 recorded test check.

• Outcome: ⚠️ 1 error across 1 run (4m27s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 1 issue found → auto-fixed ✅

• ⚠️ bin/fm-pr-check.sh:58 - The new status-log refusal path exceeds the stated intent, which only requires worker/supervisor copy-or-abstain instructions. It also does not provide the claimed durable protection: status logs are append-only, and fm_pr_status_ready_urls returns every historical done-line URL, so after done: PR <wrong-url> followed by the diagnostic’s recommended corrected done line, the old URL still matches and can be recorded or merged. Remove this unrequested enforcement component and retain the required instruction changes; ask the user before adding a deterministic enforcement policy with explicit correction/supersession semantics.

🔧 Fix: Remove stale PR URL enforcement
✅ Re-checked - no issues remain.

⚠️ **Test** - 1 error

• 🚨 tests failed with exit code 1
• bin/fm-test-run.sh --changed --exclude-family real-herdr-gated

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge because the previously reported backlog-note PR misbinding is no longer authorized and no blocking failure remains.

No blocking failure remains.

_{Reviews (2): Last reviewed commit: "no-mistakes(ci): Removed backlog notes a..." | Re-trigger Greptile}