Correct A-30 to §529's finding stream forms; answer A-42, the gate finding's scope

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md

@@ -117,8 +117,11 @@ names the principle that settles it, and is cited as "design 47 G A-n".
   judged afresh, uses one mesh-sdk form of the writer that observes from its own state: it seeds what it holds from the
   state's keys before it starts, keeps them under its own lock, and its `Observe` answers them, so no part writes that
   adapter (the watchman's copy moves there; the assigner, builder and indexer use it).
-- **A-30** (§383, §686; principle 3) Every module whose writer publishes declares the events it says
-  (`finding-written`, `finding-cleared`, `findings-stated`) in its manifest; none publishes an event it does not declare.
+- **A-30** (§383, §529, §686; principle 3; corrected) Every module whose writer publishes declares its finding events
+  as §529 says: a foundation part (the validator's list) in its old `streams` section as `<module>-findings`; every
+  other part in its `requires` by the template `events` as `finding-events`, its entry listing `finding-written.*`,
+  `finding-cleared.*` and `findings-stated.*`. None publishes an event it does not declare, and no other part declares
+  `<module>-findings`.
 - **A-31** (A-14, A-22; principles 3 and 7) A module whose old finding keys end in no kind it owns (gitea's package
   registry, distribution) deletes those old keys once at its start, in its own code, so no stale finding stays; the
   writer's rule is unchanged.
@@ -156,3 +159,5 @@ names the principle that settles it, and is cited as "design 47 G A-n".
   indexer stop reading the build modules' `toolchains` buckets: they take a toolchain from the builder's own read verb
   or event where one serves it today. Where none does, the restored read stays for G, built as mesh-delivery 7a3c312a
   has it, and the lead notes it for the next milestone; no new verb is added in G for it.
+- **A-42** (§592; principle 8) The gate's `approval-carried-open` has scope `delivery`, a scope the mesh already uses
+  for the delivery's findings, and id `<repository>.<pull>`.