chore: update nix node_modules hashes

[DevFlex-AI]

Issue for this PR

Closes #

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Please provide a description of the issue, the changes you made to fix it, and why they work. It is expected that you understand why your changes work and if you do not understand why at least say as much so a maintainer knows how much to value the PR.

If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!

How did you verify your code works?

Screenshots / recordings

If this is a UI change, please include a screenshot or recording.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}

Summary by CodeRabbit

• Chores
  • Updated platform-specific package verification data for Linux and macOS environments.
  • Ensured dependency integrity checks use current SHA-256 hashes.

[vercel]

@opencode-agent[bot] is attempting to deploy a commit to the adevloper152's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4bffa120-8d1a-4263-b496-f5fcb06a2029

📥 Commits

Reviewing files that changed from the base of the PR and between 2bef5ce and 3f239b3.

📒 Files selected for processing (1)

• nix/hashes.json

---

📝 Walkthrough

Walkthrough

Updated the platform-specific nodeModules SHA-256 values in nix/hashes.json for four Linux and Darwin architecture keys.

Changes

Dependency Hash Updates

Layer / File(s)	Summary
Update platform hashes nix/hashes.json	Replaces the nodeModules SHA-256 hashes for all four supported platform keys.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a bunny with hashes, refreshed bright,
Four platforms now match just right.
Linux and Darwin hop in line,
With SHA-256 values crisp and fine.
Nibble, commit, and ship divine!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is just the template text and contains no actual PR details, verification, or completed checklist items.	Replace the template placeholders with a real issue link, change type, summary of the hash update, verification steps, and completed checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: updating Nix node_modules hashes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 2

⚔️ Resolve merge conflicts 💡

• Resolve merge conflict in branch dev

🛠️ Fix failing CI checks 💡

• Fix failing CI checks

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[github-actions]

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

What needs to be fixed:

• No "Type of change" checkbox is checked. Please select at least one.
• No issue referenced. Please add Closes #<number> linking to the relevant issue.
• "How did you verify your code works?" section is empty. Please explain how you tested.
• Not all checklist items are checked. Please confirm you have tested locally and have not included unrelated changes.

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]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

[DevFlex-AI]

@codesmith-bot fix all conflict in a new pr

[blacksmith-sh]

Got it, I'm creating a new PR to fix the conflicts.

[blacksmith-sh]

@DevFlex-AI

@codesmith-bot fix all conflict in a new pr

Conflicts resolved in a new PR: #12

The only conflict was in nix/hashes.json, where both branches had auto-generated hash-update commits from the nix-hashes workflow. I kept the hashes already on dev (af17678), since this repo's own CI computed them most recently against the same lockfile. The merge therefore introduces no content changes; it just reconciles the divergent history, so #10 can be closed once #12 merges.