[devjiwonchoi]

why?

The repo had no CI verifying it builds, and the spec was tracked manually. Both should be automated so equine stays green and in sync with Lichess without hand-maintenance.

how?

• ci.yml: on push/PR, run install → typecheck → build → test (Node 22, matching hey-api's engine).
• sync-openapi.yml: weekly, regenerate the client from upstream and open a PR when src/client changes.
• The sync PR uses secrets.SYNC_TOKEN (falls back to GITHUB_TOKEN) so the generated PR triggers CI — add a SYNC_TOKEN PAT secret for that to work.

Top of the stack — stacked on #152.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-09T00:38:16.751774Z	bcc5ee9	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2b9661dfbd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[devjiwonchoi]

Fixed in bcc5ee9: the create-pull-request step now uses token: ${{ secrets.SYNC_TOKEN || secrets.GITHUB_TOKEN }} with a comment explaining that a PAT/App token is required for the sync PR to trigger CI (GITHUB_TOKEN-created PRs don't fire workflows). Falls back to GITHUB_TOKEN if the secret is unset.

[devjiwonchoi]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: bcc5ee9b76

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[devjiwonchoi]

The current head (bcc5ee9) already addresses this: the step uses token: ${{ secrets.SYNC_TOKEN || secrets.GITHUB_TOKEN }}. Setting a SYNC_TOKEN PAT makes the sync PR trigger CI as recommended. The GITHUB_TOKEN fallback is intentional so the workflow still opens the PR (just without CI) when the secret isn't configured, rather than failing — documented inline. Not changing further.