plans: coder grant stale text brief from row 73 packet

Rocko's row 73 packet names three places outside the row's files that
still show the coder's task.reassign grant: the business README example,
the tasks README paragraph and live/run.mjs. They go to a follow-up row
after 73, owner Rocko, reviewer Dewey, so row 73's round 1 isn't
restarted for a scope change.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-10-11_claude-pin-and-coder-grant.md

@@ -157,3 +157,60 @@ If a test shows the code doesn't refuse, stop and tell Sage.
 
 Filbert approves on the row's issue naming the candidate manifest. The cli
 node suite and every `scripts/test-*.sh` green on Sage's gate rerun.
+
+## Coder grant stale text
+
+Added by Sage, lead, on 2026-10-11 from Rocko's row 73 packet
+(`agents/rocko/work/queue-73/BUILD.md`), which names three places outside
+row 73's files that still show the old grant.
+
+### Problem
+
+Row 73 drops `task.reassign` from the coder's `crossRole`. Three places
+still show the old grant once it lands:
+
+- `packages/business/README.md`, the version 2 example (lines 30-43),
+  copies the shipped coder file with `"crossRole": ["task.reassign",
+  "task.scope.change"]`.
+- `packages/tasks/README.md`, lines 193-196, says a coder's `crossRole`
+  grant of `task.reassign` can't be used.
+- `packages/tasks/live/run.mjs`, line 32, keeps its own copy of the
+  slice 1 authority with the old coder grant. No suite runs it and its
+  coder never calls `task.reassign`, so its result doesn't change.
+
+Sage kept them out of row 73 so its round 1 review isn't restarted for a
+scope change.
+
+### Owner and reviewer
+
+Owner: Rocko, after row 73. Reviewer: Dewey. Rocko has no Gitea token;
+Sage runs the review request as jarvis.
+
+### Files owned
+
+- `packages/business/README.md`, the version 2 example only
+- `packages/tasks/README.md`, the `task.reassign` paragraph only
+- `packages/tasks/live/run.mjs`, the coder authority line only
+- `agents/rocko/work/queue-<row>/`
+
+### What ships
+
+- The business README example matches the shipped `roles/coder.json`.
+- The tasks README paragraph says the coder holds no `task.reassign`
+  grant (row 73) and the writer check refuses a non-pm `task.reassign`
+  before authority is looked at anyway.
+- The coder line in `live/run.mjs` matches `packages/tasks/tests/world.mjs`.
+- The packet shows a grep of the repository for `task.reassign` with
+  each remaining hit and why it stays.
+
+### Out of scope
+
+Any role file, any test, `broker.mjs` and the slice 1 field table.
+Refusing a non-pm `task.reassign` before a decision opens is a broker
+change and gets its own row if Sage opens one.
+
+### Gate
+
+Dewey approves on the row's issue naming the candidate manifest. The
+tasks and business node suites and every `scripts/test-*.sh` green on
+Sage's gate rerun.