Order API host before tail output

[codemountains]

Summary

• defer the events tail watch header until the initial event-list request succeeds
• keep the API host diagnostic ahead of the human-readable monitoring layout
• avoid printing a watch layout when the initial API request fails
• document the output-order contract and isolate an existing endpoint-selection test from the user's local config

Root cause

events tail printed Watching endpoint and its column header before making its first API request. The API host is intentionally logged lazily on the first fetch, so its stderr diagnostic appeared underneath the stdout table header and looked like a malformed event row.

User impact

The API host now appears before the tail layout. If the initial event-list request fails, the CLI reports the host and error without claiming that it started watching the endpoint.

Testing

• added TDD coverage for combined stdout/stderr ordering
• added coverage that an initial API error does not print the tail layout
• direnv exec . just check (typecheck, Biome, Markdown lint, 232 unit tests)