Answer A-104: the runner's write verbs, kept results, toolchain and unanswered asks

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

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

@@ -408,3 +408,10 @@ names the principle that settles it, and is cited as "design 47 G A-n".
   module's own registration decides: its first branch is the one read. The `Entry` and `Ready` helpers over the branch
   follower, the `<module>_entry_again` tool, the `entry-not-found` finding and the entries rows of
   `<module>_first_views` are built once, in `meshcatalogclient` and mesh-sdk's views, and every reader uses them.
+- **A-104** (§22, §70, §482, §25, §416, §535, §647, A-70, A-77, A-68; principle 7) The runner's write verbs (`review`,
+  `rerun`, `accept`, `cancel`) are served by its tools bundle, which writes the state `pipelines` by compare-and-set and
+  says `step-ended`; an optional step still waiting does not hold a pipeline's end, only a required one does. A step
+  ask's kept results are the `kept` entries whose `package` is the artifact's package (from the entry); its
+  `toolchain` is the runner's `toolchain.<language>` kept as heard from `toolchain-agreed`. An unanswered ask is read
+  from the build seat holder's `ask-taken` as §647 says (not the seat list), its five minutes a key with its own time to
+  live in a state `bounds` of the runner.