Add CodeBoarding architecture analysis

[ivanmilevtues]

Preview first, merge when ready

View your map · Configure & merge

The preview runs on this pull request. Merge the workflows to keep maps updated. Settings can be changed in this same pull request before merging.

This PR adds the CodeBoarding GitHub Action via two workflows:

• codeboarding-sync.yml: on every push to main, commits
  .codeboarding/analysis.json (your architecture baseline + readable docs). This is
  what the CodeBoarding viewer opens.
• codeboarding.yml: runs on every push to a pull request, keeping an
  architecture-diff comment current and uploading that PR’s analysis as a build artifact
  for the viewer’s PR diff. Each run continues from the one before it, so a push costs a
  fraction of a full analysis.

Both are needed: sync produces the baseline; review diffs against it.

Sync delivery

Sync commits the generated baseline directly to main.

Works out of the box

Just merge it: the Action runs on the free tier, with no secret to add. The
id-token: write permission lets it identify your repo to CodeBoarding’s hosted LLM,
metered against a weekly limit for the repository owner.

Want more, or unmetered, usage?

Switching is a change to these workflow files rather than a secret you add, because the
file names which credentials a run uses. Use Configure & merge in the viewer to pick:

• a CodeBoarding plan (unmetered, and raises the analysis-depth ceiling from 3 to 10), or
• your own provider key: OpenRouter, Anthropic, OpenAI, Google, AWS Bedrock and
  others.

Before merging, this updates the same setup pull request and tells you which secret to
add under Settings → Secrets and variables → Actions.
After merging, use repository settings in the dashboard to open an update PR.

Opened for you by CodeBoarding.

[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-10-13T19:02:02.800116Z	31b91ef	PR opened

ℹ️ 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.

[github-actions]

CodeBoarding review · analyzing…

⏳ CodeBoarding is analyzing this pull request's architecture changes.

Open it in CodeBoarding meanwhile: the files, comments and review are there already, and the diff appears when the run finishes.

_{run 38451103652 · attempt 1}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 31b91eff48

ℹ️ 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".

[chatgpt-codex-connector]

Pin the CodeBoarding action to an immutable SHA

Both new workflows reference the mutable @v1 tag, so an upstream retag or compromise can replace the code executed with contents: write, id-token: write, and PR/issue write permissions without any reviewed repository change. Replace this reference and the identical one in codeboarding.yml with the verified 40-character release SHA and retain the version tag as a trailing comment.

AGENTS.md reference: AGENTS.md:L579-L579

Useful? React with 👍 / 👎.