Consider: Parallelise acceptance tests (Phase 5a G)

[leggetter]

Summary

Use multiple Hookdeck projects and API keys so CI can run acceptance test subsets in parallel without shared state. This would shorten CI feedback as the suite grows (~243+ tests after metrics).

Context

From the Hookdeck Agentic DX Master Plan / Phase 5a CLI plan: Future phase: Acceptance test speed / parallelization.

Proposed approach

• Multiple projects + API keys: e.g. HOOKDECK_CLI_TESTING_API_KEY for job 1, HOOKDECK_CLI_TESTING_API_KEY_2 for job 2.
• Split tests: By package or build tag so each CI job runs a subset against a different project. No shared project state → jobs can run in parallel. Total wall-clock time becomes the slowest job instead of the sum.
• Optional: Smoke vs full tiers — small smoke set on every PR; full suite on merge to main or on release.
• Optional: Tags or env var to select which set runs (e.g. -tags=acceptance_full or env).

References

• Phase 5a plan: phase_5a_cli_updates_bd801679.plan.md → "Future phase: Acceptance test speed / parallelization"
• Current CI: go test ./test/acceptance/... -v -timeout 20m; tests use testing.Short() to skip when -short is set.

Label

Consider for backlog / when prioritising CI speed.