v1.2.1

Fixed

• Board columns reach the footer in wall mode (#497). The columns stopped at a fixed 640 px height and left a gap above the legend. In wall mode they now take all the height between the Board header and the legend, follow the window as it is resized or goes fullscreen, and scroll inside themselves when they hold more cards than fit. With the "no open steps" strip showing, the columns end above it. Outside wall mode the Board is unchanged.
• The rail no longer pages one orchestrator at a time on a narrow window (#474). Below 1040 px the panes stack and the rail's height follows its rows, so it measured only the room its rows already took, paged, shrank, and settled on one row a page ("Showing 1–1 of 5"). A stacked rail now lists every row with no pager, and widening past 1040 px pages again on the page that holds the selection. Wide windows page as before.
• The Sonar scan no longer stalls for five minutes (#501). Every full analysis spent 300 s in SonarJasmin's React render simulation, which starts at frontend/src/main.tsx and walks the whole component tree until it hits its time limit; the job took 6 to 8 minutes, which looked like a hang during the 1.2.0 release. main.tsx, a 30-line bootstrap with no logic or tests, is now excluded from the scan. CI configuration only; no change to the product.
• podium_send can reply when several orchestrators share a name (#500). podium_peers now shows a short session id for orchestrators that share a name and machine, and says only name@machine#id reaches them. podium_send accepts that form and delivers to exactly that session; a bare duplicated name@machine is still refused, now with the ids to use instead of asking the person to rename one. An inbound message carries the sender's id, so the mod's reply line names name@machine#id. An older server sends no id, and the mod then falls back to the plain address.
• The history paging test no longer counts a timer's reads (#494). "builds rows for the requested page only" spied on every getAgents call, so a session broadcast timer that fired during a slow request (under coverage in CI) added to the count. The test now holds the throttle open for its fixture, so only the request's own calls are counted. It still fails if the route builds every row. Test only; no change to the product.