GitHub Action: dataGriff/api-caller/setup-apic@v1 #60

Why

The CI recipes in docs/getting-started.md and docs/cookbook.md start with curl … install.sh | sh. A uses: step is what people expect, it caches the binary, pins a version, and it is the thing the course's CI lesson will show.

What

• A composite action at setup-apic/action.yml in this repo (so uses: dataGriff/api-caller/setup-apic@v1 works without a second repository). Inputs: version (default latest), install-dir. Outputs: version, path.
• Steps: resolve the tag, download the archive for the runner OS/arch (Linux, macOS, Windows), verify against checksums.txt (reuse the logic in install.sh; on Windows use PowerShell), optionally verify the cosign signature when verify-signature: true, cache with actions/cache keyed on version and platform, add to PATH.
• A v1 moving tag maintained by the release workflow (retag on each v1.x release), documented in AGENTS.md Releasing.
• Optional second action run/action.yml that wraps apic run with inputs targets, env, dir, redact and posts a job summary from --json (nice, not required for the first cut).
• Docs: every CI snippet in the docs and README switches to the action; install.sh stays documented for non-GitHub CI.

Where

setup-apic/action.yml, .github/workflows/release.yml (retag), a .github/workflows/action-test.yml that uses the action on all three OSes, docs/getting-started.md, docs/cookbook.md, docs/testing.md, README.md.

Tests

The action-test.yml workflow runs apic version and apic validate -C examples/httpbin via the action on ubuntu, macos and windows on every PR touching setup-apic/ or install.sh.