Live route surface disagrees with openapi.yaml and the published contract

[github-actions]

The gateway is serving routes that neither openapi.yaml nor the published contract describes, and/or documenting non-draft operations it does not serve.

Run: 34019319711 · commit 4ea990dadac4e2889d6abf100658f4296d6512cf

The machine-readable diff is attached to the run as the live-route-drift artifact. It is deliberately not committed: it enumerates the live route surface.

Each finding is cleared by documenting the operation in openapi.yaml, withdrawing the route, or adding an allowlist entry with a real justification in .github/scripts/live-route-drift-allowlist.json.
See .github/scripts/live-route-drift.mjs for what each direction means and why a 402 is presence rather than absence.

[github-actions]

The gateway is serving routes that neither openapi.yaml nor the published contract describes, and/or documenting non-draft operations it does not serve.

Run: 34096685904 · commit 8aa0e84d2db9ccfd6e38591916633a6af490b8ba

The machine-readable diff is attached to the run as the live-route-drift artifact. It is deliberately not committed: it enumerates the live route surface.

Each finding is cleared by documenting the operation in openapi.yaml, withdrawing the route, or adding an allowlist entry with a real justification in .github/scripts/live-route-drift-allowlist.json.
See .github/scripts/live-route-drift.mjs for what each direction means and why a 402 is presence rather than absence.

[github-actions]

The gateway is serving routes that neither openapi.yaml nor the published contract describes, and/or documenting non-draft operations it does not serve.

Run: 34199871731 · commit 8aa0e84d2db9ccfd6e38591916633a6af490b8ba

The machine-readable diff is attached to the run as the live-route-drift artifact. It is deliberately not committed: it enumerates the live route surface.

Each finding is cleared by documenting the operation in openapi.yaml, withdrawing the route, or adding an allowlist entry with a real justification in .github/scripts/live-route-drift-allowlist.json.
See .github/scripts/live-route-drift.mjs for what each direction means and why a 402 is presence rather than absence.

[github-actions]

The gateway is serving routes that neither openapi.yaml nor the published contract describes, and/or documenting non-draft operations it does not serve.

Run: 34324425711 · commit 3bed8280a2a9ad9abcb9861ee4c4cdd618cae079

The machine-readable diff is attached to the run as the live-route-drift artifact. It is deliberately not committed: it enumerates the live route surface.

Each finding is cleared by documenting the operation in openapi.yaml, withdrawing the route, or adding an allowlist entry with a real justification in .github/scripts/live-route-drift-allowlist.json.
See .github/scripts/live-route-drift.mjs for what each direction means and why a 402 is presence rather than absence.

[github-actions]

The gateway is serving routes that neither openapi.yaml nor the published contract describes, and/or documenting non-draft operations it does not serve.

Run: 34450521576 · commit 3bed8280a2a9ad9abcb9861ee4c4cdd618cae079

The machine-readable diff is attached to the run as the live-route-drift artifact. It is deliberately not committed: it enumerates the live route surface.

Each finding is cleared by documenting the operation in openapi.yaml, withdrawing the route, or adding an allowlist entry with a real justification in .github/scripts/live-route-drift-allowlist.json.
See .github/scripts/live-route-drift.mjs for what each direction means and why a 402 is presence rather than absence.