Feedback fanout banner false alarm fix

When launching many remote-control workers in rapid succession (e.g. 8 at once via a fan-out script), the remote-control banner health-check frequently times out even though the session is alive and building. This is a false alarm caused by Console being loaded down during rapid boot.

Why: Confirmed across 6/8 workers in a Tier 1 fan-out: sockets were live, panes actively generating, but banner never painted inside the check window. set -e on the launcher aborted the remaining workers unnecessarily.

How to apply: In any fan-out or multi-spawn launcher script: (1) treat a missing RC banner as a warn not a hard fail, do not use set -e around the banner check; (2) use at least 12s inter-spawn sleep to avoid boot overload; (3) verify session health by checking the tmux socket + pane output, not just the banner. Patch forge_suite_tier1_fanout.sh before any Wave 2 run.

[auto-memory session 57205162-c1eb-485a-ba96-f5b45b27ab9b, confidence 0.85, mode direct]