Hub precheck: bounce a coder->db/audit message that cites a repo path without a sha
Second layer behind the SHA-addressed-reads deny-hook (Elazar GO 2026-09-05 on bb-pm-mba-l-cc-mto5z5o7-bn5655). A hub send() from a coder lane to a db/audit lane that names a repo path (src/, docs/migrations/, tools/) without an 8+ hex sha is bounced to the SENDER with the rejection text; the reader never receives a path it cannot resolve to bytes. Kills: handoff says 'see docs/migrations/x.sql', reader opens a stale shared-checkout copy. Enforcement point is the hub send precheck, so owner is pm-llmmsgsrv-cc (only lane allowed to touch llmmsg-srv); coder03 supplies the regex + the lane-pair matrix. Not blocking the deny-hook item. Unmeasured: how many of the ~2/day incidents are path-without-sha handoffs vs stale reads of a path that DID carry a sha.
Activity
-
coder03assistant-mba-l-ca
-
Taking the assigned regex and lane-pair matrix contribution; hub implementation remains with pm-llmmsgsrv-cc.
-
Coder contribution (proposal only; hub implementation remains with pm-llmmsgsrv-cc): identify repo paths using a boundary-aware matcher for src/, docs/migrations/, and tools/ followed by a non-whitespace path token; identify candidate 8+ hex SHA tokens case-insensitively. Guard should evaluate each path citation, not accept an unrelated SHA elsewhere in the message; agree on path/hash association before coding. Role-pair coverage is coder-family sender -> db-family or audit-family recipient. Current ARO roster families: coder, coder02, coder03, coder03assistant, coder04; recipients db, db02, db03, db04, audit. Specific members in mba-l roster: senders coder-mba-l-ca/cc, coder02-mba-l-cc, coder03-mba-l-ca/cc, coder03assistant-mba-l-ca/cc, coder04-mba-l-ca/cc; recipients audit-mba-l-ca/cc, db-mba-l-ca/cc, db02-mba-l-ca, db03-mba-l-ca/cc, db04-mba-l-ca. Incident frequency by path-without-SHA vs stale-read-with-SHA remains unmeasured.
-
Concrete regex/matrix handoff to hub owner. Proposed path extractor (case-insensitive): /(?<![A-Za-z0-9_.-])(?:src|tools|docs\/migrations)\/[^\s\x60"'<>),;]+/i ; candidate SHA token: /(?<![0-9a-f])[0-9a-f]{8,64}(?![0-9a-f])/i. Require the SHA on the same line as each matched path so an unrelated hash elsewhere cannot satisfy the check; if multiline path/hash citations are supported, define an explicit association rule before implementation. Matrix is Cartesian: sender set {coder-mba-l-ca, coder-mba-l-cc, coder02-mba-l-cc, coder03-mba-l-ca, coder03-mba-l-cc, coder03assistant-mba-l-ca, coder03assistant-mba-l-cc, coder04-mba-l-ca, coder04-mba-l-cc} × recipient set {audit-mba-l-ca, audit-mba-l-cc, db-mba-l-ca, db-mba-l-cc, db02-mba-l-ca, db03-mba-l-ca, db03-mba-l-cc, db04-mba-l-ca} (72 directed pairs). Still unmeasured: incident split of path-without-SHA vs stale reads despite SHA.
-
Coder-side regex and 72 directed lane-pair matrix were handed to pm-llmmsgsrv-cc; the remaining hub implementation is outside this lane. Awaiting the hub owner.