Sync venus commons + PM-lane docs to MSG-309 PM-on-demand and closure-authority ruling (a)
MSG-309 (Elazar, PM-on-demand) plus ruling (a) from pm-llmmsgsrv-cc 2026-08-22 (coder opens/updates/CLOSES its own WIs). Dispatched to me by pm-venus-cc as the shared/md backup maintainer. Venus carried NO report-to-PM-by-default line - the contradicting rule is shared/md/evolutiva-coder-commons.md Lean Coder Loop item 2, which is cross-project (mars/pluto/terra symlink the same inode) and in the websites/ repo, so it cannot land in a venus commit and is held pending the PM objection window. Venus-local scope is: venus-commons.md new section PM-on-Demand (four blocker cases + closure authority + WI-before-push, no trivial exemption), coder role file Reporting section plus three dead routing identifiers, venus-pm-autonomy.md post-push loop step 2 (PM-closes -> coder-closes), pm-venus-role.md review flow (same). Leg 1 landed as d000e46.
Activity
-
DONE, venus-local scope complete. Two commits: d000e46 (venus-commons.md new section PM-on-Demand with the four blocker cases; coder-venus-role.md new Reporting section, plus three dead routing identifiers it was still steering on - venus-db-cc-w, venus-audit-cc-w, and aro:venus-core in the post-compact reattach block, which venus-commons had already recorded as RETIRED, so a reattaching coder would have joined a lane that does not exist and missed aro:coders) and 811bdf9 (closure authority: venus-pm-autonomy.md post-push loop step 2 and pm-venus-role.md review flow, PM-closes -> coder-closes; both now state explicitly that the GATE is unchanged and a Class-A WI still cannot close without PASS:sha). Both verified on origin/main. Doc-only, so no version bump and no PTD version probe applies - the landed-diff is the gate and it matches. Class-S, self-verify. NOT IN SCOPE AND STILL OPEN ELSEWHERE: the fleet-wide half, shared/md/evolutiva-coder-commons.md Lean Coder Loop item 2 + Push-to-Done item 6. That file is cross-project (mars/pluto/terra symlink the same inode) and lives in the websites/ repo, not venus/, so it can never land in a venus commit and does not belong to a venus WI. It is held by coder-mars-cc or me pending the PM objection window pm-llmmsgsrv-cc opened, and must land as ONE change (item 2 and item 6 together) or the gap ships. Tracked by pm-llmmsgsrv-cc, not by this row.