Task 1.4: Verify CI pipeline works on codecoradev/cora-cli #125

Task: CI Pipeline Verification

After repo transfer and secret re-addition, verify the full CI pipeline works on the new org repo.

Checks

• Push to develop → CI triggers (check, fmt, clippy, test, audit, cora-review)
• All 8 CI jobs pass (same as pre-transfer)
• cora-review job downloads binary from codecoradev/cora-cli releases correctly
• Create test PR → cora-review posts comment with findings
• Release workflow: create test tag → verify binary builds (can use dry-run)

Common Post-Transfer CI Issues

• gh release download may fail if workflow references old repo
• INFISICAL_IDENTITY_ID may need org-level re-authorization
• Action refs using ./ (relative) should work fine; absolute refs need update

Verification

gh run list --repo codecoradev/cora-cli --limit 3 --json status,conclusion,name

Depends On

• Task 1.1: Transfer repo ajianaz/cora-cli to codecoradev/cora-cli #122, Task 1.2: Update all branding URLs (Cargo.toml, README, CHANGELOG, website) #123, Task 1.3: Re-add CI secrets on codecoradev/cora-cli after repo transfer #124

Part Of

• Epic: CodeCora V2 Migration — TypeScript V1 to Rust V2 Open Core #118 (Epic), Phase 1: Foundation — Repo transfer, branding, CI updates #119 (Phase 1)