v1.0.7

Fixed

• The bridge told agents to read journalctl for their own mistakes. The daemon
  reports every failure as a 500, and the bridge classified by status code alone, so
  a missing url parameter and a Chrome that would not start looked identical and
  both carried the advice to check the host's logs. That advice is wrong for a bad
  argument, and following it for one trains the agent to ignore the real 500s.

  The daemon now labels its failures (error_kind: validation | chrome | internal)
  and the bridge reads that label instead of guessing from the status. A
  validation failure gets a hint about the argument names and types, is not
  retried — the identical request cannot succeed — and no longer holds the
  daemon's lock for the length of three doomed attempts. A chrome failure gets the
  retry-once-then-check-the-logs advice it deserves.

  A label the bridge does not recognise is ignored rather than guessed at, so a
  future daemon label degrades to the status-based classification instead of
  becoming an unknown kind.