[bmscomp]

kates conformity check's table had a Detail column, and it put pod lists inside Observed. One waived rule with a long reason, or a few pod names, padded every row. On panda's payments-krafter report the table ran to about 200 columns.

Before, panda's payments-krafter report (banner omitted, cut at 120 columns):

  Status    Rule                      Expected  Observed                                                                               Detail
  ▲ WARN    brokers.antiAffinity      required  preferred (krafter-brokers-alpha-0, krafter-brokers-gamma-1, krafter-brokers-sigma-2)
  ○ WAIVED  monitoring.kafkaExporter  true      false                                                                                  FAIL, waived until …

After, the same report:

  Status    Rule                      Expected  Observed
  ────────  ────────────────────────  ────────  ─────────
  ▲ WARN    brokers.antiAffinity      required  preferred
            krafter-brokers-alpha-0, krafter-brokers-gamma-1, krafter-brokers-sigma-2
  ○ WAIVED  monitoring.kafkaExporter  true      false
            FAIL, waived until 2027-03-31 by platform-team: The Kind overlay turns Kafka Exporter off; enable it before…

✓ PASS: 0 fail, 1 warn, 1 waived, 22 pass, 0 unknown

What changes

• Four columns: Status, Rule, Expected and Observed.
• One fact per line under each row: the subjects that fall short, the waiver, the detail and the note. The lines are dimmed, start at the Rule column, and are each cut to the terminal's width. -o json keeps everything whole.
• Expected and Observed share the remaining width. They get what Status and Rule leave. A value cut to fit gets its own line underneath, whole, so a required listener still shows everything it expects and has (fix(conformity): show what a required listener expects and has #423's test still holds). The rule id is never cut.
• A shorter banner state line: not Ready, results may change.
• JUnit: failure messages keep the first three subjects and +N. A waived rule's facts are joined with · instead of ; , so a reason ending in a period stops rendering as .;.
• output.TableNotes: the house Table with an optional note per row. Table itself is unchanged.
• Docs: the Conformity Checks chapter's captured outputs and the CLI Reference's description of the table follow the new layout.

Tests

• TestTableNotes: a note starts under the second column, fits the terminal and ends with an ellipsis when cut.
• TestConformityCheckShowsTheGaps now has a four-pod rule with a long detail. It asserts that no line runs past the terminal and that the pods aren't on the rule's row.
• The JUnit test asserts the subjects in a failure message.

Checked locally: go vet, go test ./... under cli/, golangci-lint --new-from-rev=origin/main (0 issues), scripts/check-cli-style.sh, scripts/check-cli-compat.sh and scripts/check-book-style.sh. The before/after outputs above are panda's real reports, rendered through the old and new builds.

Not checked: a real colour terminal (the captures are non-TTY), and ASCII mode.