chore: sync from monorepo @ff6d73c

[WomB0ComB0]

Automated sync from resq-software/resQ@ff6d73c.

Review before merging — direct pushes to standalone repos are preserved.

[coderabbitai]

Warning

Rate limit exceeded

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

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ 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: 21bb2386-7e65-4758-acbf-383210a00af1

📥 Commits

Reviewing files that changed from the base of the PR and between 2ce6f0e and df4d7ba.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (22)

• .gitignore
• osv-scanner.toml
• resq-airspace/src/error.rs
• resq-airspace/src/instructions/grant_permit.rs
• resq-airspace/src/instructions/initialize_property.rs
• resq-airspace/src/instructions/record_crossing.rs
• resq-airspace/src/instructions/update_policy.rs
• resq-airspace/src/instructions/update_treasury.rs
• resq-airspace/src/lib.rs
• resq-airspace/src/state/airspace_account.rs
• resq-airspace/src/state/mod.rs
• resq-airspace/src/state/permit.rs
• resq-airspace/tests/host_init_regression.rs
• resq-airspace/tests/integration.rs
• resq-delivery/src/error.rs
• resq-delivery/src/instructions/mod.rs
• resq-delivery/src/instructions/record_delivery.rs
• resq-delivery/src/lib.rs
• resq-delivery/src/state/delivery_record.rs
• resq-delivery/src/state/mod.rs
• resq-delivery/tests/integration.rs
• vendor/solana-program-test/osv-scanner.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sync/monorepo-ff6d73c

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 1 minute and 54 seconds.}

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

[gemini-code-assist]

Code Review

This pull request removes several configuration files, downgrades dependency versions, and refactors code formatting. Feedback indicates that deleting .gitignore and osv-scanner.toml are regressions that will lead to tracking build artifacts and failing security scans. Additionally, downgrading the rand crate re-introduces known issues, and the removal of clippy suppressions in lib.rs, initialize_property.rs, and test files is expected to cause CI build failures due to argument count limits and transmute annotations.

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

.gitignore (1-6)

The removal of the .gitignore file is a significant regression. This will cause build artifacts (like the target/ directory), environment-specific files (like .DS_Store), and dependency folders (like node_modules/) to be tracked by Git. This file should be preserved in the standalone repository.

resq-airspace/src/instructions/initialize_property.rs (55)

The removal of #[allow(clippy::too_many_arguments)] will likely cause Clippy to fail during CI, as this handler takes 9 arguments (exceeding the default limit of 7). Since the arguments are necessary for initialization, this attribute should be retained.

#[allow(clippy::too_many_arguments)]
pub fn handler(

resq-airspace/src/lib.rs (1)

Removing the global #![allow(clippy::too_many_arguments)] suppression may lead to build failures in environments where warnings are treated as errors, especially given that some handlers in this crate exceed the default argument limit.

#![allow(unexpected_cfgs, clippy::too_many_arguments)]

resq-airspace/tests/host_init_regression.rs (1-6)

Removing the Clippy and unused item suppressions in test files may lead to build failures or excessive noise in CI, particularly for the missing_transmute_annotations lint which is triggered by the unsafe transmute in the instruction processor.

Cargo.lock (3976)

Downgrading the rand crate from 0.8.6 to 0.8.5 (and 0.9.3 to 0.9.2) is a regression. These newer versions were released to fix potential panics in ThreadRng. Unless there is a specific compatibility requirement, it is safer to stay on the latest patch versions.

osv-scanner.toml (1)

The removal of the osv-scanner.toml configuration file eliminates the rationales for ignoring known transitive vulnerabilities. This will likely cause security scanning tools to report these as unaddressed issues in CI.