Fix Trail invocation docs for non-global installs

[willwashburn]

Summary

• replace the misleading npx trail fallback with npx --yes agent-trajectories
• document the repo-local npm run trail -- ... source runner for contributors and agents
• add the trail npm script backed by vite-node so this repo can run the CLI without a global install or build step

Verification

• npm run trail -- --help
• npm run trail -- status
• ./node_modules/.bin/biome check package.json package-lock.json README.md AGENTS.md docs/trail-snippet.md
• npm run typecheck
• npm run build
• npm run test:run

[coderabbitai]

Warning

Review limit reached

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

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

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

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

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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ff2b8b7-193c-4d07-a622-ec7ba746a3fb

📥 Commits

Reviewing files that changed from the base of the PR and between 1abd6e2 and 98d1426.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• AGENTS.md
• README.md
• docs/trail-snippet.md
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-trail-npx-usage

---

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

[cubic-dev-ai]

No issues found across 5 files

_{Re-trigger cubic}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3b18167e7b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid claiming local installs can run trail directly

This instruction is incorrect for the common case where users run npm install agent-trajectories locally and then invoke commands from a normal shell: local npm binaries are linked under node_modules/.bin, not placed on the global PATH, so trail start ... will fail with command not found unless run via npx/npm exec (or inside an npm script). Because this section is specifically about non-global installs, the current wording will send users and agents down a broken path.

Useful? React with 👍 / 👎.