Generated via Copilot on behalf of @krukow
Summary
There is no automated guard against accidental changes to the public API surface. For a 1.0.0 GA (a one-way door for the public contract), the validation/quality phases should not be able to silently grow or mutate the surface.
Proposed fix
Commit an API snapshot artifact (public symbols + arglists + spec keys for github.copilot-sdk*) and add a test that fails when the live public surface drifts from the snapshot. Updating the snapshot becomes a deliberate, reviewable step.
A baseline snapshot of the current surface (74 public vars in github.copilot-sdk: 65 fns, 3 macros, 6 values) has already been generated during the GA prep pass and can seed this guard.
Sequencing
Defer building the guard until after the Phase 1 upstream API-parity pass settles the surface (to avoid churning the snapshot during parity fixes).
Severity
ga-nice-to-have — process/quality guard that protects the GA contract through the remaining validation phases.
Summary
There is no automated guard against accidental changes to the public API surface. For a 1.0.0 GA (a one-way door for the public contract), the validation/quality phases should not be able to silently grow or mutate the surface.
Proposed fix
Commit an API snapshot artifact (public symbols + arglists + spec keys for
github.copilot-sdk*) and add a test that fails when the live public surface drifts from the snapshot. Updating the snapshot becomes a deliberate, reviewable step.A baseline snapshot of the current surface (74 public vars in
github.copilot-sdk: 65 fns, 3 macros, 6 values) has already been generated during the GA prep pass and can seed this guard.Sequencing
Defer building the guard until after the Phase 1 upstream API-parity pass settles the surface (to avoid churning the snapshot during parity fixes).
Severity
ga-nice-to-have— process/quality guard that protects the GA contract through the remaining validation phases.