ci-integration.md

CI Integration

GitHub Actions

Use the committed example flow as the required CI gate. It type-checks the TypeScript surface, executes runtime and example flows, runs Rust tests, checks boundaries, and renders the domain graph:

name: Boundra

on:
  pull_request:
  push:
    branches:
      - main

jobs:
  verify-example:
    runs-on: ubuntu-24.04
    steps:
      - uses: actions/checkout@v6
      - uses: dtolnay/rust-toolchain@stable
      - uses: actions/setup-node@v6
        with:
          node-version: 24
      - run: corepack enable
      - run: pnpm install --frozen-lockfile
      - run: pnpm verify-example
      - run: pnpm verify-clean-room
      - run: cargo clippy --workspace --all-targets -- -D warnings

Local Verification

Run the same aggregate gate locally:

pnpm verify-example

The individual boundary command remains suitable for repositories that only adopt Boundra's analyzer.

Exit Codes

• 0: no boundary violations
• 1: boundary violations found
• 2: config, manifest, or CLI usage error
• 3: runtime scan or file system error

JSON Output

CI and agent integrations should prefer JSON output:

cargo run -p boundra-cli -- check-boundaries --root examples/order-billing --format json

Example:

{
  "status": "failed",
  "violations": [
    {
      "rule": "BR-001",
      "file": "domains/order/client/use-order.ts",
      "line": 3,
      "import": "../server/order-service",
      "message": "client layer cannot import server layer",
      "suggestion": "move shared contract to shared layer or call through an API boundary"
    }
  ],
  "meta": {
    "command": "check-boundaries",
    "violation_count": 1
  }
}