blindpay-python/.github/workflows/api-sync-check.yaml at main · blindpaylabs/blindpay-python · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
name: API Sync Check

on:
  workflow_call:

jobs:
  api-sync-check:
    name: Run deterministic spec-sync patcher checks
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Python
        uses: actions/setup-python@v5
        with:
          python-version: "3.12"

      - name: Map validity (every spec-map.json entry resolves)
        run: python3 .api-sync/sync.py --validate-map

      - name: State reconciliation (--check)
        run: python3 .api-sync/sync.py --check

      - name: Determinism proof
        run: |
          set -e
          rm -rf /tmp/api-sync-proof-a /tmp/api-sync-proof-b
          cp -r . /tmp/api-sync-proof-a
          cp -r . /tmp/api-sync-proof-b
          # Re-applying the already-committed snapshot against itself must be
          # a deterministic no-op in any generic CI context (no externally
          # delivered spec-current.json is available here). The stronger
          # proof -- that applying genuinely NEW drift twice from the same
          # starting state produces byte-identical results -- is covered by
          # tests/test_api_sync.py::TestDeterminism.
          (cd /tmp/api-sync-proof-a && python3 .api-sync/sync.py --apply --spec .api-sync/spec-snapshot.json)
          (cd /tmp/api-sync-proof-b && python3 .api-sync/sync.py --apply --spec .api-sync/spec-snapshot.json)
          diff -rq /tmp/api-sync-proof-a /tmp/api-sync-proof-b
          diff -rq . /tmp/api-sync-proof-a

      - name: Coverage report (non-blocking)
        continue-on-error: true
        run: python3 .api-sync/sync.py --coverage --spec .api-sync/spec-snapshot.json

      - name: Type audit (non-blocking)
        continue-on-error: true
        run: python3 .api-sync/sync.py --audit-types --spec .api-sync/spec-snapshot.json