Add omniroute to project setup as a devDependency

[ada33-arch]

What

Makes omniroute a persistent part of the project setup instead of a one-off npm install -g omniroute.

• package.json — pins omniroute at ^3.8.49 under devDependencies, and adds an omniroute npm script.
• package-lock.json — regenerated to lock the resolved tree.
• README.md — new "OmniRoute" section documenting npm run omniroute / npx omniroute.

Why

A global install lives outside the repo: it has to be repeated on every machine, isn't version-pinned, and CI never sees it. As a devDependency the tool comes along with the existing npm install step already documented in the README, at a locked version, for every clone.

Verification

• npx omniroute --version → 3.8.49, resolved from node_modules/.bin/omniroute
• npm run typecheck → passes (exit 0)

Notes for the reviewer

Two things worth a look before this leaves draft:

• Lockfile size. omniroute pulls in ~1181 transitive packages, so package-lock.json grows by roughly 19k lines. That is the real cost of vendoring this into a repo that currently has three devDependencies.
• Audit findings. npm install reports 8 vulnerabilities in the new tree (1 low, 2 moderate, 5 high). I did not run npm audit fix — the fixes may involve breaking upgrades, and that call belongs to you. GitHub also flagged 2 pre-existing vulnerabilities on main that are unrelated to this change.

There are also peer-dependency warnings during install (react@18.3.1 via @emoji-mart/react, and marked@18 against marked-terminal's >=1 <16 range). npm resolves both with nested copies; nothing fails.

---

Generated by Claude Code