12 V to 5 V / 1 A Buck Molecule (TPS54202)

@@ -123,7 +123,7 @@ Every remaining row is closed in the binary; see docs/release-0.1.37.md on adom/  | # | gap | fix belongs in | |---|---|---|-| 36 | `capture start` after the editor was closed and reopened used the run's stored window handle (724124), which no longer existed, so the recorder did not start and the first 23 label groups went on unfilmed. It should rediscover the editor window (by board path) when the stored one is gone. | aiflow (capture) |-| 37 | `kicad_silk_text_batch` takes rotation as `rotation` (it refuses `angle` with "unsupported text field angle"), and it caps the stroke at a quarter of the text height, so on a board whose minimum stroke is 0.08 mm, 0.30 mm text is impossible (0.32 mm is the floor). Neither is in the verb's documentation. | kicad-bridge docs, aiflow-silkscreen skill |-| 38 | the silkscreen clip was 2.7 GB for 17 minutes (about 2.6 MB/s); the bridge pull failed after 10 minutes and ConfRoomROG has no ffmpeg to shrink it. It came across split into 200 MB parts with PowerShell. The recorder's bitrate, or a transcode before the pull, should keep a step clip pullable. | adom-bridge recorder, aiflow (pull in parts) |+| 36 (fixed in 0.1.38) | `capture start` after the editor was closed and reopened used the run's stored window handle (724124), which no longer existed, so the recorder did not start and the first 23 label groups went on unfilmed. It should rediscover the editor window (by board path) when the stored one is gone. | aiflow (capture) |+| 37 (documented in 0.1.38) | `kicad_silk_text_batch` takes rotation as `rotation` (it refuses `angle` with "unsupported text field angle"), and it caps the stroke at a quarter of the text height, so on a board whose minimum stroke is 0.08 mm, 0.30 mm text is impossible (0.32 mm is the floor). Neither is in the verb's documentation. | kicad-bridge docs, aiflow-silkscreen skill |+| 38 (fixed in 0.1.38) | the silkscreen clip was 2.7 GB for 17 minutes (about 2.6 MB/s); the bridge pull failed after 10 minutes and ConfRoomROG has no ffmpeg to shrink it. It came across split into 200 MB parts with PowerShell. The recorder's bitrate, or a transcode before the pull, should keep a step clip pullable. | adom-bridge recorder, aiflow (pull in parts) | | 39 | the silkscreen dashboard replay recording opens in a Hydrogen webview on the user's machine; with the test box rule ("use the test box so the user is not disturbed") it was not recorded. The dashboard's board.json and events.jsonl are in the run for a later replay. | aiflow-silkscreen (a test-box surface for the dashboard) |

@@ -120,6 +120,10 @@ Everything in this run that aiflow did not guide, gate or measure was logged as | 33 | `finish` after adopting a routed board | bug | **closed in 0.1.37** | | 34 | `compose` could not assemble the video from a relative run path | bug | **fixed in 0.1.35** | | 35 | clip pulls that fail silently (four clips lost) | bug | **closed in 0.1.37** |+| 36 | `capture start` used a dead window handle after the editor was reopened | bug | **fixed in 0.1.38** |+| 37 | the silkscreen text verb's `rotation` field and stroke cap were undocumented | docs | **documented in 0.1.38** (aiflow-silkscreen, aiflow-power-layout) |+| 38 | a 2.7 GB step clip could not be pulled in one piece | bug | **fixed in 0.1.38** (pulled in 200 MB parts) |+| 39 | the silkscreen dashboard replay needs a Hydrogen tab on the user's machine | skill | open (board.json and events.jsonl kept in the run for a later replay) |  Ten companion skills from this run shipped in adom-aiflow 0.1.34 (2026-09-29), and 0.1.37 (2026-09-30) closed every remaining gap in the binary. Its new `planeUnder` gate then found one thing on this board: an EN via and part of the VOUT sense trace on B.Cu under the input hot loop (see the gap log).