fix(config-write): skip redundant .gitignore append when existing rule covers path (#1484) - #1485

Merging this PR tags and publishes **v1.2.0**.

Generated by knope from the `.changeset/` fragments — don't edit it by
hand; add or amend a changeset on the source PR instead.

---

## Features

- Bridge liveness now pairs the wall-clock start time with a
boot-relative one that NTP cannot move. A host clock correction no
longer marks a running bridge Stopped, blanks its CPU/RAM chip, or
deletes its card.
([#1400](#1400))
- `clauster keepers --kill <pid> --force` now stops a live keeper that
the normal cleanup spared on a still-carded project. It runs the same
PID-reuse identity check first, and is the recovery path for a keeper no
other automated stop can reach.
([#1458](#1458))

## Fixes

- When the host clock is stepped by any amount, a bridge started after
this release keeps its Running card. A bridge record left by a previous
boot is no longer mistaken for a live process on a recycled PID. A
bridge started before this release is unchanged until its next spawn.
([#1431](#1431))
- Stopping an Interactive Session now checks the keeper PID against the
keeper start time recorded in the instance row. It no longer trusts only
a snapshot taken as the stop begins. A PID recycled onto an unrelated
process before the stop ran is no longer force-killed.
([#1479](#1479))
- Keeper liveness now pairs the wall-clock start time with a
boot-relative one that NTP cannot move. A host clock correction no
longer lets Forget delete the record of a running Interactive Session.
([#1427](#1427))
- ensure_gitignored avoids appending redundant entries when covered by
existing .gitignore ancestor directory rules, exact matches, or basename
patterns, while respecting subsequent negation rules.
([#1485](#1485))
- On Windows, a broken ConPTY now ends the Interactive Session and marks
its bridge stopped. The card no longer reads live over a bridge that is
gone. ([#1416](#1416))
- Subagent and skill frontmatter now parse the same way. A `---` fence
line can carry trailing whitespace on both surfaces. Before, a skill's
opening fence with trailing whitespace was rejected. A skill body no
longer keeps the whitespace after its closing fence. Both surfaces now
reject a mismatched explicit tag (`!!int`, `!!float`, `!!bool`,
`!!timestamp`) as a 422 instead of a 500.
([#1367](#1367))
- A config file that exists but cannot be read now fails the doctor
config row plainly. The other CLI verbs now exit 2 with a `config error`
message instead of a traceback. Before, an unreadable file made
`clauster doctor` and `/api/doctor` answer a 500.
([#1447](#1447))
- Subagent or skill frontmatter that parses but holds a value the JSON
response cannot represent is now refused as a 422. The shapes are a
non-finite float (`.nan`/`.inf`), a non-UTF-8 `!!binary`, and an integer
too large to serialize. A string holding a lone surrogate is refused
too. Each returned a 500 before.
([#1448](#1448))
- A self-referential YAML alias in subagent or skill frontmatter is now
rejected as a 422 at write time. Before, the write was accepted and
reading the stored value back failed with a 500.
([#1394](#1394))
- When the host clock is corrected, a Direct Session started after this
release keeps its Kill and Resume buttons. Before, a clock correction
reported a running session as lost. Sessions started before it are
unchanged until their next spawn.
([#1425](#1425))
- A hosted session whose persisted record holds a wrong-typed value now
reattaches with default metadata and a logged warning. Before, it failed
clauster's startup for every hosted session.
([#1377](#1377))
- A hosted session whose saved conversation id is off-shape now keeps
that id on disk, so an operator can repair it by hand. The dashboard
hides Resume for such a session, whether the id was captured live or
reloaded, instead of offering a Resume that only errors.
([#1453](#1453))
- Two gaps a corrupt `hosted_state.json` opened are now closed. Two
records that share an instance id no longer let a cached client id
resolve to the wrong session. A session whose saved project is
unreadable now says why it cannot be resumed, instead of offering a
Resume that never works.
([#1397](#1397))
- An empty `claude_session_uuid` in a corrupt `hosted_state.json` record
no longer blocks a hosted session from learning its real session id.
Before, that row lost `--resume` for the life of the process.
([#1391](#1391))
- An Interactive Session whose bridge reached ready without capturing a
connect link now reads Running after a Clauster restart. It matches the
spawn path. Before, a ready sidecar with no link and no notice
reattached stuck at Starting for the life of the process.
([#1460](#1460))
- Winding down a lingering pty keeper now checks its boot-relative start
time, so a host clock correction mid-shutdown no longer leaves the
keeper running.
([#1409](#1409))
- Keeper sidecars and hosted-session rows now record a boot id. A host
clock step no longer makes a live Interactive Session keeper or hosted
agent look dead across a reboot. A keeper or hosted session started
before this release is unchanged until its next spawn.
([#1462](#1462))
- The standalone binary now loads a `clauster deps install pty` pyte in
the Interactive Session keeper, so the live terminal works without
setting `CLAUSTER_PYTE_PATH`.
([#1488](#1488))
- An Interactive Session that captured no connect link now keeps its
notice and its Running status across a Clauster restart. Before, the
reattached card dropped the notice and flipped to Starting.
([#1451](#1451))
- A pyte render fault during the PTY keeper's connect-URL scrape no
longer kills the keeper. Before, it stranded the discovery sidecar at
`starting` or `ready` with the bridge orphaned. The scrape now skips
that chunk and retries on the next one.
([#1388](#1388))
- An Interactive Session that captured no connect link now names the
reason on its card.
([#1426](#1426))
- Stopping an Interactive Session now winds its keeper down on a host
whose `/proc` reports no boot time. Before, the keeper and its bridge
kept running and nothing was logged.
([#1427](#1427))
- When a pywinpty liveness check faults during teardown on Windows, a
`claude` login flow no longer stays stuck `active`. The four ConPTY
`isalive()` calls now read a fault as dead, and the teardown always
clears the flow.
([#1454](#1454))
- A terminal frame that pyte cannot render no longer crashes the
dashboard login mid-flow. The authorize-URL and token scans skip that
frame and keep scanning. If the sign-in still fails, the fault is named.
([#1375](#1375))
- The dashboard metrics sampler now handles a host with no procfs
`btime` line. It reports the bridge's own CPU and memory instead of
failing the request.
([#1430](#1430))
- An unterminated OSC 8 (terminal hyperlink) escape no longer swallows
the following line into its URI. Before, on the Windows ConPTY login
path, that handed the operator a corrupted, unopenable `claude
setup-token` authorize URL. On that path the hyperlink target is the
only recoverable copy.
([#1385](#1385))
- A hostile `bridge-pointer.json` now follows the documented contract
that a malformed pointer degrades to None. Deeply-nested JSON and an
oversized integer literal no longer raise out of pointer loading.
`clauster` can now back up and remove such a pointer, as it already did
for other corrupt ones. Before, the pointer wedged the next bridge
start. ([#1383](#1383))
- Reading a settings.json that holds a huge integer or a NaN/Infinity
float literal now returns a 422, not a 500. The message names only the
class of the offending value, never the value.
([#1463](#1463))
- A corrupt legacy `state.json` or `hosted_state.json` now degrades to
an empty store, as documented. It no longer takes clauster down on the
boot that imports it. The import logs every corrupt shape and copies the
file aside once as `*.corrupt.bak`. `clauster migrate` refuses to
rewrite a file it cannot read and leaves it untouched.
([#1413](#1413))
- Seven untrusted-input parsers now skip or reject a deeply-nested or
non-object payload instead of raising, and a junk `daemon_last_seq` in
`hosted_state.json` no longer blocks startup.
([#1336](#1336))
- Two more transcript readers skip a deeply-nested line instead of
failing the usage tally and the transcript viewer with a 500.
([#1372](#1372))

## Security

- `doctor`'s `config` row now reports a broken `clauster.yml` by
position and key path only. It never echoes the offending YAML line, the
rejected scalar, or the parsed mapping.
([#1428](#1428))
- A secret inside a YAML `!!omap`, `!!pairs`, or `!!set` in subagent or
skill frontmatter is now masked in the displayed frontmatter. An alias
pyramid that expands exponentially (a billion-laughs attack) is now
refused as a 422. Before, it tied up a worker on every read.
([#1414](#1414))
- A subagent's frontmatter now masks a secret written as a `!!binary`
value. It masks the base64 spelling like the plain-string spelling, by
key name and by secret-shaped content.
([#1459](#1459))
- A YAML `<<` merge-key pyramid in subagent or skill frontmatter is now
refused as a 422. Before, it tied up a worker thread for seconds inside
the parse on every read that lists agents or skills.
([#1461](#1461))
- A YAML parse error no longer echoes the offending frontmatter token to
the dashboard. A rejected subagent or skill now reports the error
category with its line and column. Before, PyYAML's message quoted the
token itself for an undefined alias, a duplicate anchor, or an unknown
tag. ([#1396](#1396))
- A hosted session's stored conversation id is now shape-checked before
it becomes the `--resume` value. A tampered record can no longer add an
argument to the spawn command line. An ended session that cannot be
resumed now says, on its row and in its panel, which part of its record
is missing. ([#1412](#1412))
- A stray OSC 8 (terminal hyperlink) opener can no longer swallow the
real authorize URL, because its parameter run now excludes ESC. The live
pty screen also re-redacts each row after the width re-fit, so
truncation can no longer shear a redacted identifier back into view.
([#1371](#1371))
- The live pty-screen view now masks a redactable token that wraps
across the fixed-width row boundary, which per-row redaction missed.
([#1492](#1492))
- The live terminal-screen view now masks a real identifier a consumed
escape welded onto the word before it. It also masks an id welded to
another id, and it matches the real id shape, so an ordinary name like
`resolve_session_transcript` stays readable.
([#1442](#1442))
- A greedy secret or id token can weld onto a UUID with no separator and
eat its leading hex digits. On the live pty-screen view, the rest of the
UUID no longer reaches the browser.
([#1499](#1499))
- A zero-width or invisible Unicode character inside a session or
environment identifier no longer hides it from the log redaction. Such
characters are now removed from the redacted log the dashboard shows.
([#1441](#1441))
- Log redaction now masks against the view a browser renders. An escape
sequence or an invisible control character can no longer weld a session
identifier onto the word before it, or split one in two. DCS, SOS, PM,
and APC escape payloads (device-control and private-message strings) are
now stripped whole, not streamed as readable junk.
([#1432](#1432))
- OSC escape sequences (terminal title, hyperlink, clipboard) are
stripped whole from the streamed bridge log and the `claude login` URL
scan. Before, their payload showed as visible text.
([#1337](#1337))
- The config editor documents which surfaces mask secret-shaped values
and which return raw, and recommends against storing a secret in a
subagent file.
([#1490](#1490))
- A rendered transcript turn's `timestamp` is now redacted like its
other fields, so an identifier carried in that field no longer reaches
the browser verbatim.
([#1372](#1372))

## Build System & Dependencies

- The unused `watchdog` runtime dependency is dropped, so installs, the
container image, and the frozen binary no longer ship it.
([#1325](#1325))
- Clauster now requires psutil 7.1 or newer. On a host whose `/proc`
reports no boot time, earlier psutil versions raised in the process
constructor. ([#1427](#1427))

Co-authored-by: clauster-ci[bot] <289303168+clauster-ci[bot]@users.noreply.github.com>