honker: row 194 PRD 1.7 draft, adding to the fixed hire list is a PRD change (mos-1035 item 3, sage-1395)

agents/honker/work/queue-194/PRD-1.7-DRAFT.md

@@ -58,8 +58,8 @@ Under "Added in version 1.2", after REQ-COS-2:
 >     working-push actions of an assigned task. A role holding any other action, such as launch, end,
 >     organization, naming, hire, review verdict or merge authority, or any action added later, is never
 >     hired. So the chief never hires a chief, never picks its own reviewers or merge gate, and the author
->     is never the reviewer. This holds whatever the role file's list says. Changing the fixed list is a
->     reviewed commit.
+>     is never the reviewer. This holds whatever the role file's list says. Adding to that list is a PRD
+>     change.
 >   - The chief may set a hired instance's model and narrow its limits, and nothing else about it.
 >   - The user can forbid per agent. The user marks an instance so the chief can't fire it, end its runs
 >     or change its model, and marks role kinds the chief can't hire. Only the user changes these marks, through the
@@ -119,8 +119,10 @@ REQ-WAIT-3, appended:
   the routing commit (duckworth-0022 N9, sage-1387).
 - REQ-LAND-2 and REQ-COS-3 meet at the coder. Coder declares Gitea credentials, so REQ-COS-3's
   credentials bound keeps the chief from hiring one until a later version lifts it. `git.push.remote` isn't
-  on REQ-COS-3's fixed list either, so a coder holding it stays unhireable until a reviewed commit adds it
+  on REQ-COS-3's fixed list either, so a coder holding it stays unhireable until a PRD version adds it
   (row 194 D2.3).
+- Adding to the fixed action list is a PRD change (mos-1035 item 3, sage-1395). The role file's
+  `hireable` list stays a reviewed commit in `roles/`.
 - The credentials bound names no row number, so the text doesn't go stale when row 199 lands. A later
   version lifts it.
 - This draft follows the PRD's own style: plain words, no semicolons in new sentences, and the status