l0ng-ai bfa58af587 fix(config): say "your config is broken" once, not once per pane spawn ...

`Config::load` runs on every pane spawn and every palette command, and the
parse-failure arm logged a warning each time. One stray comma in config.json
therefore produced a log made of the same line: measured at 23 copies after
opening three tabs and sending one command, growing for as long as the session
lasts and burying every other warning in the file.

The answer was already there. `quarantine` refuses to keep a second copy of
contents it has kept before — that check is what stops a broken config filling
the directory with identical `.corrupt` files — so it already knows whether a
breakage is newly seen. It now says so, and the parse message is a warning the
first time and a debug line afterwards.

Nothing else moves: the file is still kept aside, `save` still refuses to run
against a quarantined config, and the user's file is untouched.

Verified against a running instance with a deliberately malformed config.json:
the same four operations that produced 23 warnings now produce 1, there is
still exactly one `.corrupt` file, and config.json is byte-identical to what
was written before the app started.

2949 tests pass.

2026-08-15 18:29:17 +08:00

..

tty7-cli

fix(cli): machine ls --json was missing the machine it runs on

2026-08-15 18:11:17 +08:00

tty7-core

fix(config): say "your config is broken" once, not once per pane spawn

2026-08-15 18:29:17 +08:00

tty7-server

fix(resize): defer the reflow to the daemon's Size echo on remote routes too (#632)

2026-08-14 16:02:04 +08:00