fix(ci): resolve zizmor alerts #35 (bot-conditions) and #36 (artipacked)

[WomB0ComB0]

Summary

• Alert refactor: extract shared TUI terminal module and slim workspace deps #35 (bot-conditions, Error) in auto-merge.yml:29: replaced github.actor_id == '49699333' with github.event.pull_request.user.login == 'dependabot[bot]'. The pull_request event payload is fixed at trigger time and cannot be spoofed via workflow re-runs the way github.actor / github.actor_id can.
• Alert refactor: apply PR review feedback — glob members, fix deploy-cli broken links, sync CLAUDE.md #36 (artipacked, Warning) in release-plz.yml:23: removed the explicit token: input on actions/checkout and set persist-credentials: false. release-plz-action already reads GITHUB_TOKEN from the step's env: block for git push and API calls, so persisting the credential in .git/config only widens the leak surface.

Closes the two open security alerts:

• https://github.com/resq-software/crates/security/code-scanning/35
• https://github.com/resq-software/crates/security/code-scanning/36

Test plan

• zizmor audits at https://github.com/resq-software/crates/security/code-scanning should drop alerts refactor: extract shared TUI terminal module and slim workspace deps #35 and refactor: apply PR review feedback — glob members, fix deploy-cli broken links, sync CLAUDE.md #36 once master has these workflow changes.
• On the next dependabot PR, the auto-merge job's if: evaluates true under the new condition (verified locally — dependabot[bot] is the immutable PR author for dependabot/* branches).
• release-plz still runs on its weekly cron / manual dispatch — it consumes GITHUB_TOKEN from the step env, not from .git/config, so removing persist-credentials is safe.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Rate limit exceeded

@WomB0ComB0 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 25 minutes and 55 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ccad0c88-3d52-4344-a62e-bca719a610b8

📥 Commits

Reviewing files that changed from the base of the PR and between c5d0c1d and 6d8ce0f.

📒 Files selected for processing (2)

• .github/workflows/auto-merge.yml
• .github/workflows/release-plz.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/zizmor-bot-actor-and-credentials

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}