Update CodeBoarding workflow configuration

[ivanmilevtues]

Preview first, merge when ready

View your map · Configure & merge

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

This PR brings your CodeBoarding setup to the current shape:
one workflow file, codeboarding.yml, with a review and a sync job. It regenerates
that file so it will:

• run on CodeBoarding’s free hosted tier, declared as llm: hosted, which needs
  no secret at all, and
• keep id-token: write, which is how a run identifies your repository to the hosted
  tier. Nothing else to configure.

Sync delivery

Sync saves the generated diagram on its own codeboarding/baseline branch in this repository; dev never changes and there is nothing to merge.

Protect codeboarding/baseline

Sync and review load a Python pickle from that branch, and loading a pickle runs code, so anyone
who can push to it can run code in these workflows. Import a ruleset under Settings, Rules,
Rulesets, New ruleset, Import a ruleset, before the first sync:

• baseline-branch-ruleset-actions.json fits this workflow
  as generated, which pushes with the default github.token. It stops people pushing by hand,
  but any workflow with contents: write can still write the branch.
• baseline-branch-ruleset.json lets only the CodeBoarding Review app
  write it. Use it when sync pushes with the app's token as github_token.

More in the baseline branch. Rulesets on a private
repository need a paid GitHub plan.

Cleaned up

• Deletes codeboarding-sync.yml: its job now runs from codeboarding.yml, so CodeBoarding runs from one file.
• Deletes the generated files under .codeboarding/ from dev (5). The analysis now lives on
  codeboarding/baseline, so a copy here would only go stale. Your configuration (.codeboardingignore, the health settings) stays.

Only CodeBoarding’s own files are touched. If you’d customized a workflow, review the
diff before merging.

Opened for you by CodeBoarding.

[github-actions]

Hey! Your PR title Update CodeBoarding workflow configuration doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[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 38665580540 · attempt 1}

[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-15T01:28:24.471911Z	28334f8	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.