v1.6.0-rc.9

v1.6.0-rc.9

Full Changelog: v1.6.0-rc.8...v1.6.0-rc.9

[1.6.0-rc.9] — 2026-07-28

Added

• Continuous Portwing edge log streams. The authenticated container-log WebSocket now bridges correlated dd:container_log_chunk, dd:container_log_end, and dd:container_log_error frames, cancels the agent stream when the viewer closes, preserves stdout/stderr and timestamp decoding, and caps each downstream viewer at 1 MiB of buffered data. Older Portwing agents degrade to their one-shot response without breaking the viewer.
• Real Portwing fleet-soak workflow. Pull requests and the weekly quality schedule run actual signed Portwing processes against Drydock's production edge gateway through concurrent exec, sustained logs, forced controller backpressure, and reconnect storms. Machine-readable evidence records RSS/heap budgets and is retained for 90 days.

Changed

• The portwing/1.0 edge endpoint is enabled by default. DD_EXPERIMENTAL_PORTWING=false remains as an emergency disable for new edge connections. OpenAPI, operator docs, and translated feature summaries now describe the stable/default-on behavior.

Fixed

• The row "Updating/Queued/Scanning" overlay chip is no longer clipped at the pinned-column edge. The table's pinned identity-cluster cells (sticky z-10) painted over the full-width row overlay hosted in the first cell and cut the centered chip in half at the cluster boundary. While an overlay is active the host cell now sits above its z-10 row siblings (and still below the sticky header). (#631)
• Registry errors no longer replace the container's tag in the tag column. A rate-limit/auth/not-found registry error rendered a danger pill instead of the current tag (table mode) or appended one (card mode), duplicating the warning glyph + tooltip the registry column already shows. The tag cell now always shows the actual tag; the registry column glyph remains the single error flag. (#631)