diff --git a/issues/build/a-boot-timeout-verdict-quotes-stdio-alone-and-never-the-16550-log.md b/issues/build/a-boot-timeout-verdict-quotes-stdio-alone-and-never-the-16550-log.md
new file mode 100644
index 00000000000..2cf6986ef16
--- /dev/null
+++ b/issues/build/a-boot-timeout-verdict-quotes-stdio-alone-and-never-the-16550-log.md
@@ -0,0 +1,18 @@
+---
+status: assigned
+kind: tooling
+opened: 2026-09-28
+---
+
+# A boot timeout's verdict quotes stdio alone, so an early kernel panic that only reached the 16550 log is invisible in it
+
+Evidence: PR #572's control run at `87629411`. The 16550 log held `EARLY
+PANIC: panicked at library/alloc/src/alloc.rs:659:9: memory allocation of
+4096 bytes failed`, and the verdict said "Boot timed out waiting for
+===READY===", quoting stdio alone; the panic line never appeared in it.
+
+**Exit**: the timeout verdict quotes the 16550 file's tail the same way the
+`Disconnected` arm already does — `fs::read_to_string(uart_log)`
+(`tests/common/qemu.rs:5147`) — rather than adding a second reader, shown by
+a test that stages an early panic. Owner: `tests/common/qemu.rs`, held by
+the orchestrator.
diff --git a/issues/build/ftruncate-flush-race-reds-intermittently-and-nothing-says-why.md b/issues/build/ftruncate-flush-race-reds-intermittently-and-nothing-says-why.md
index a4748478b38..e0905d05e12 100644
--- a/issues/build/ftruncate-flush-race-reds-intermittently-and-nothing-says-why.md
+++ b/issues/build/ftruncate-flush-race-reds-intermittently-and-nothing-says-why.md
@@ -1,5 +1,5 @@
 ---
-status: open
+status: expected-red
 kind: tooling
 opened: 2026-09-01
 ---
@@ -42,4 +42,18 @@ the loop is one-sided precisely because a sleep can overshoot. Whoever takes
 this decides what to measure; this entry is the rate and the refutation, not a
 design.
 
-`cargo run -- --known-red ftruncate_flush_race` says `NOT ON THE LIST`.
+Red again in the orchestrator's nightly for PR #572 at `87629411`: "the
+truncate did not serialise with the stalled flush".
+
+## Exit condition
+
+The capture holds when `set_len` entered the kernel relative to the stall's
+start, so a short `waited` is machine-distinguishable from a retry, and
+`ftruncate_flush_race` is green against that instrument on the dev host across
+the counts in the table above. Then this file and its `src/redlist.rs` row are
+deleted.
+
+## Owner
+
+The `ftruncate-flush-stall` actuator, `tests/common/volumes.rs`; held by the
+orchestrator.
diff --git a/src/redlist.rs b/src/redlist.rs
index ec48d2a75f5..884f0760969 100644
--- a/src/redlist.rs
+++ b/src/redlist.rs
@@ -35,6 +35,10 @@ pub const DISABLED: &[Disabled] = &[
     },
     Disabled { test: "desktop_window_child", issue: "issues/kernel/desktop-window-child-freeze.md" },
     Disabled { test: "doom_sound_flood", issue: "issues/audio/doom-sound-flood-played-full-scale-once.md" },
+    Disabled {
+        test: "ftruncate_flush_race",
+        issue: "issues/build/ftruncate-flush-race-reds-intermittently-and-nothing-says-why.md",
+    },
     Disabled { test: "handle_basic", issue: "issues/kernel/deferred-release-outlives-its-syscall.md" },
     Disabled {
         test: "handle_kill_policy",