Linear VCS Bridge

Implementation: lib/vcs/ — provider.mjs (contract), github.mjs, harness.mjs, index.mjs (selection).

References:

• Linear webhooks: https://linear.app/developers/webhooks
• Linear Diffs: https://linear.app/docs/diffs
• Harness API: https://apidocs.harness.io

Why an abstraction rather than two bridges

Linear's own code-review product (Diffs) integrates with GitHub only. A Harness Code shop gets no review surface in Linear at all. Everything else — extracting issue keys, naming branches, transitioning on merge, commenting on deploys — is identical between the two hosts.

So the split is: one provider-neutral behaviour layer, and a thin adapter per host that only covers what genuinely differs.