Clarify source paths in PR readiness hash reviews #403
- MA
## Why
The #372 pilot prepared a valid conflict resolution, but the publisher rejected it because the agent listed the exception JSON path in `hashReviews.file`. The publisher requires the affected source path. Local replay passed once those fields named `apps/web/src/workspace.tsx`.
## Change
Clarify the worker's hash-review instructions: take `file` from the exception record, hash the proposed source blob, and explain each renewed exception. Regenerate the locked workflow. The publisher's policy is unchanged.
## Stack and verification
This change follows #402 in the local preparation stack. It will be restacked onto final `main` when its turn comes. The combined local #402–#404 stack passed 203 maintenance tests, `bun run ci`, `bun run types`, and `bun run build`. The locked worker workflow and CI must be checked again on the final PR head.
## Hash-review contract

MaggieAppletonauto-rebase-enabledlast month on GitHub
MaggieAppletonauto-merge-disabledlast month on GitHub
MaggieAppletonhead-ref-force-pushed 74980abdec02last month on GitHub
MaggieAppletonmerged f7aec55f84delast month on GitHub
MaggieAppletonhead-ref-deletedlast month on GitHub
MaggieAppletonreferenced this in Allow guarded CI fixes on stacked PRs #404last month on GitHub