Revert 58 ithaca

[Dargon789]

Summary by Sourcery

Configure workflow permissions and merge queue, and remove obsolete configuration

CI:

• Restrict GitHub Actions workflows to read-only contents permissions for manual deployment, test infra, and permissions check jobs

Deployment:

• Add Mergify configuration for a parallel merge queue

Chores:

• Remove the CNAME file and introduce an empty Husky pre-commit hook file

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
legion	Ready	Preview, Comment	May 6, 2026 9:20am

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Configures minimal read-only contents permissions on several GitHub Actions workflows, introduces a basic Mergify configuration for merge queues, adds a new Husky pre-commit hook file, and removes the CNAME file from the repository.

Flow diagram for the new Mergify merge queue configuration

flowchart LR
  A[Developer opens or updates PR] --> B[GitHub runs workflows<br/>manual_deployment claude_code test_infra]
  B --> C{All required checks pass?}
  C -- No --> D[PR remains pending]
  C -- Yes --> E[Mergify evaluates rules]
  E --> F[PR added to merge queue account]
  F --> G[Merge queue schedules parallel merges<br/>skip intermediate results]
  G --> H[PR is merged into base branch]

Loading

File-Level Changes

Change	Details	Files
Restrict GitHub Actions workflows to minimal read-only contents permissions.	Add top-level permissions block with contents: read to the manual-deployment workflow Add job-level permissions block with contents: read to the claude-code check-permissions job Add top-level permissions block with contents: read to the test-infra workflow	.github/workflows/manual-deployment.yml .github/workflows/claude-code.yml .github/workflows/test-infra.yml
Introduce Mergify configuration to enable a basic merge queue setup.	Create .mergify.yml with a queue_rules section defining an 'account' queue Configure merge_queue behavior to skip intermediate results and run in parallel mode Add a minimal scopes.source.files configuration	.mergify.yml
Adjust repository meta/integration files by adding a Husky hook and removing the CNAME.	Add a new .husky/pre-commit script file (content not shown in diff) Delete the CNAME file from the repository	.husky/pre-commit CNAME

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 📃 Configuration Change Requirements

Waiting for:

• check-success = Configuration changed

This rule is failing.

Mergify configuration change

• check-success = Configuration changed

[sourcery-ai]

Hey - I've left some high level feedback:

• The newly added .husky/pre-commit file is empty; either populate it with the intended hook script (including a shebang and making it executable) or remove it to avoid a no-op hook.
• The .mergify.yml configuration defines a queue_rules entry named account without any conditions and an empty scopes.source.files map; please confirm this broad matching behavior is intentional or refine the rules/conditions to match the desired subset of changes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The newly added `.husky/pre-commit` file is empty; either populate it with the intended hook script (including a shebang and making it executable) or remove it to avoid a no-op hook.
- The `.mergify.yml` configuration defines a `queue_rules` entry named `account` without any conditions and an empty `scopes.source.files` map; please confirm this broad matching behavior is intentional or refine the rules/conditions to match the desired subset of changes.

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request introduces a Husky pre-commit hook for automated formatting and snapshot updates, along with a Mergify configuration for managing merge queues. Feedback suggests removing the clear command from the pre-commit hook to preserve terminal output and deleting the empty scopes block in the Mergify configuration to maintain a cleaner setup.

I am having trouble creating individual review comments. Click here to see my feedback.

.husky/pre-commit (1)

The clear command in the pre-commit hook is discouraged as it clears the terminal output, making it difficult to diagnose failures in the CI/CD pipeline or local development.

forge fmt && forge snapshot --isolate --match-contract Benchmark --via-ir && git add snapshots

.mergify.yml (6-8)

The scopes configuration with an empty files: {} object is likely unnecessary. If there are no specific file restrictions for the merge queue, this block should be removed to keep the configuration clean.