Missing CLI to diagnose "Latest filled block is not available

Description: Operators frequently encounter Latest filled block is not available when L2 loses L1 sync (#17263). Currently no CLI command exists to check L1→L2 sync status, forcing manual analysis across multiple Docker containers. Problem: text - taiko-cli status: shows general node status - No command shows: L1 head block vs L2 filled block gap - Operators hunt logs across l1_node, l2_geth, l2_nmc (5+ containers) Reproduced in Codespace (real operator scenario): text # Simulates real L1 RPC failure (empty/commented endpoint) cd packages/taiko-client/internal/docker/nodes/ # L1_ENDPOINT commented (real broken config) docker compose up What operators see: text l1_node | error: invalid value '' for '--timestamp <NUM>' (crash) l2_geth | WARN Beacon client online, no consensus updates received l2_geth | INFO Marked indexing initer as stalled Current debugging = 30+ minutes: text docker ps # 5 containers docker logs l1_node | tail # crash? docker logs l2_geth | tail # sync? docker logs l2_nmc | tail # tracker? # operator guesses which failed Request: CLI command to show L1 sync status in one line (similar to taiko-cli status). Screenshots attached: docker ps (l1_node restarting) docker logs l2_geth (sync stalled) docker-compose.yml (L1_ENDPOINT missing)