v0.6.1

Changed

• The related-gate CI recipe in docs/integrations/ci.md now derives the PR
  changed-file list from the checkout (git diff BASE...HEAD with
  fetch-depth: 0) and falls back to a retried GitHub API call. Outcomes are
  reported as clean, violation, or infra-error, and the sticky comment
  updates on every outcome (including infrastructure failure). Adopters who
  copied the previous recipe must re-copy it and set fetch-depth: 0 on the
  checkout step; a shallow checkout breaks the new primary path.
• Shipped Swift and Dart scanner executables are now named
  docbridge-swift-scanner and docbridge_dart_scanner. Paths under
  dist/bin/<platform>/speclink-* no longer exist; delete chmod +x
  workarounds that hard-coded those names rather than updating the paths.

Fixed

• Bundled Swift and Dart scanner binaries no longer have to be executable at
  install time. Installers do not reliably preserve the executable bit on files
  under dist/bin/, which made docbridge check fail on every Swift or Dart
  project; DocBridge now restores the bit on its own bundled scanners when the
  current process cannot execute them. Consumers can remove chmod +x
  workarounds from their build recipes. When the bit cannot be restored, or when
  the binary is executable but the filesystem refuses to execute it as a
  noexec mount does, code_scanner_unavailable now names the cause and the
  remedy instead of surfacing a bare spawn error.