chore: fix pre-push hook (DEBT-002)

[KooshaPari]

User description

Summary

Fixes DEBT-002 — the broken pre-push hook that ran npm scripts against a non-existent root package.json, blocking every git push with an ENOENT / Missing script abort.

Findings on main (pre-fix state)

• .husky/pre-push invoked npm run check:any-budget:t11 && npm run check:tracked-artifacts. Neither script is defined in any package.json in the repo (verified via grep -l), so git push aborted with npm error Missing script — not the original ENOENT for npm test described in docs/TECH_DEBT.md, but the same class of failure.
• lefthook.yml does not exist at the root or anywhere in the repo (verified via find).
• Root package.json does not exist (verified via find); real manifests live in @omniroute/opencode-plugin/, @omniroute/opencode-provider/, open-sse/, desktop-electrobun/, electron/.

Changes

• .husky/pre-push — replaced with a no-op shell script (exit 0) and a comment explaining the DEBT-002 background, the two real fix paths (workspace-aware npm/pnpm scripts OR port to lefthook + cargo make), and the re-enable trigger (CI runs the full test matrix and root package.json is restored).
• lefthook.yml — already absent on main; nothing to do.
• Root package.json — already absent on main; nothing to do.

Verification

• git push no longer aborts with npm error code ENOENT / Missing script.
• Hook still exits cleanly with the no-op shell script.
• Pre-push hooks run from .husky/pre-push (set via husky install in packageManager field of sub-package.jsons).

Related

• DEBT-002 in docs/TECH_DEBT.md
• PLAN.md § 4.1 (operational readiness)
• worklogs/2026-06-17-fleet-readiness.md (worklog entry — exact filename may differ; fleet worklog schema is worklogs/<date>-<req-id>-<slug>.md)

Out of scope (not touched)

• The pre-existing docs/intent/OmniRoute.md working-tree modifications were left untouched (auto-save from a parallel process, not related to DEBT-002).
• The unrelated feat(a2a): implement smartRouting skill commit (341fce795, DEBT-006) that was on this branch from a prior session was left as-is — DEBT-002 fix is the additional 13a670057 commit on top.

---

Branch: chore/l5-117-fix-pre-push-hook-2026-06-18
Base: main
Owner: @KooshaPari/core
Commits ahead of main: 2 (1 unrelated feat(a2a): implement smartRouting skill + 1 chore: fix pre-push hook (DEBT-002))

---

CodeAnt-AI Description

Stop pre-push from blocking git pushes

What Changed

• The pre-push hook now does nothing instead of running broken checks against a missing root package.json
• git push no longer fails with ENOENT or “Missing script” from this hook
• The hook now points contributors to the real fix path and notes that CI still runs the full test matrix

Impact

✅ Fewer push failures
✅ No more missing-script errors on pre-push
✅ Cleaner contributor workflow

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Review limit reached

@KooshaPari, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 57 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 32271664-faad-447a-8874-809c94b76f09

📥 Commits

Reviewing files that changed from the base of the PR and between 4781711 and 13a6700.

📒 Files selected for processing (1)

• .husky/pre-push

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key: "review"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/l5-117-fix-pre-push-hook-2026-06-18

---

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.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud