docs: add missing published npm packages to org profile README

[yakimoto]

Summary

• The Packages table in profile/README.md listed only 3 of the 6 published @wave-av npm packages.
• Adds rows for @wave-av/cli (1.0.8), @wave-av/workflow-sdk (1.0.6), and @wave-av/dispatch (0.7.0), matching the existing table format (name / description / npm shields.io badge).

Test plan

• Verified all three packages are publicly listed on npm.
• Diff is scoped to the Packages table only, matching existing row format.

---

Note

Low Risk
Documentation-only update to the profile README with no runtime or security impact.

Overview
The Packages table in profile/README.md now lists all six published @wave-av npm packages instead of three.

New rows follow the same format as existing entries: package link, short description, and shields.io npm version badge for @wave-av/cli, @wave-av/workflow-sdk, and @wave-av/dispatch (dispatch links to the dispatch-edge repo). No other sections of the README change.

^{Reviewed by Cursor Bugbot for commit ce9bc01. Configure here.}

Note

Add three missing npm packages to org profile README

Adds rows for @wave-av/cli, @wave-av/workflow-sdk, and @wave-av/dispatch to the packages table in profile/README.md. Each row includes GitHub repository links and npm version badges.

^{Macroscope summarized ce9bc01.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_527e4205-d835-4e22-b432-bc97ae976cc7)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 9 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

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

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4d129a05-1d6c-4695-a8d3-487eebe822a4

📥 Commits

Reviewing files that changed from the base of the PR and between 7767662 and ce9bc01.

📒 Files selected for processing (1)

• profile/README.md

---

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

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-code-review]

PR Summary by Qodo

Add missing @wave-av npm packages to org profile README

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Expand the profile Packages table to include all published @wave-av npm packages.
• Add entries for @wave-av/cli, @wave-av/workflow-sdk, and @wave-av/dispatch with badges.
• Keep table formatting consistent with existing package rows and links.

Diagram

graph TD
  A["GitHub org profile"] --> B["profile/README.md"] --> C["Packages table"] --> D["New npm rows"]
  D --> E["npmjs.com badges"]

  subgraph Legend
    direction LR
    _doc["Doc file"] ~~~ _ext{{"External site"}}
  end

Loading

High-Level Assessment

The PR’s approach is appropriate: directly add the missing package rows to the existing Markdown table to keep the profile accurate and consistent. Alternatives like auto-generating the table from npm/GitHub metadata add tooling and maintenance overhead that isn’t justified for a small, static list.

Files changed (1) +3 / -0

Documentation (1) +3 / -0

README.mdAdd missing @wave-av packages to the README Packages table +3/-0

Add missing @wave-av packages to the README Packages table

• Adds three new rows to the Packages table for @wave-av/cli, @wave-av/workflow-sdk, and @wave-av/dispatch. Each entry includes the GitHub repo link, a short description, and an npm version badge matching the existing format.

profile/README.md

[qodo-code-review]

Qodo Fixer

No findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR.

[macroscopeapp]

Approvability

Verdict: Approved ce9bc01

Documentation-only change adding npm package listings to the org profile README. No runtime impact, and the author owns the changed file.

^{You can customize Macroscope's approvability policy. Learn more.}

[devin-ai-integration]

Devin Review found 2 potential issues.

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}