row 271 (264d, #1776): BUILD.md records mos-1336, Mos's approval under mos-1292 of the later3l, rows() and thread-shares migration test changes on the 3m to 3n rebase, with its conditions

agents/gizmoduck/work/queue-271/BUILD.md

@@ -637,8 +637,9 @@ The mos-1315 kinds, one label up:
 - Engine copies: account- :90, gitea- :80 and grant-migration.test.mjs :83 copy `3m-3n.sql` after
   206's `3l-3m.sql`.
 
-Changes outside the mos-1315 list, the same kind 206 made for thread_shares. They go to Mos with the
-review request (mos-1292):
+Changes outside the mos-1315 list, the same kind 206 made for thread_shares. Mos approved all three
+under mos-1292 in mos-1336 (19:58Z). Conditions: neither name list grows past these two names without
+Mos, and a gate red in these files outside the listed lines goes to Mos:
 - `later3l` in account- :21-22, gitea- :38-39 and grant-migration.test.mjs :24-25 gains
   `session_ops` and `message_cancels`, with a comment line. These tests compare sqlite_master before
   and after older steps, and the 3m to 3n objects are new there just as thread_shares is. My first