feat: add capabilities.json (platform-registry Phase D)

[yakimoto]

Backfills this repo into wave-foundation/frameworks/platform-registry.

🤖 Generated with Claude Code

---

Summary by cubic

Adds capabilities.json to publish wave-av/sdk into the platform registry (Phase D) for discovery, dependency mapping, and lifecycle tracking.

• New Features

  • Sets schemaVersion: "1" and foundationPin: "v1".
  • Tracks repo: "wave-av/sdk", version: "2.0.4", lifecycle: "beta", maintainers [{"team":"sdk"}].
  • Declares consumes: wave-av/api-spec and frameworks/platform-registry.
  • Adds tags: sdk, public, typescript, @wave-av/sdk.

• Bug Fixes

  • Corrects version to match package.json (2.0.4).

^{Written for commit 50a14bc. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 50a14bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 31 minutes and 41 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: ASSERTIVE

Plan: Pro

Run ID: 295117c8-fee7-439e-8f1e-1c24e7bebe90

📥 Commits

Reviewing files that changed from the base of the PR and between c4d10d5 and 50a14bc.

📒 Files selected for processing (1)

• capabilities.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/capabilities-json

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch feat/capabilities-json

---

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

[sentry]

Bug: The version in capabilities.json ("2.0.14") is inconsistent with the actual package version in package.json ("2.0.4"). This will publish incorrect metadata to the platform registry.
_{Severity: HIGH}

Suggested Fix

Update the version field in capabilities.json to match the version in package.json. The value should be changed from "2.0.14" to "2.0.4". Consider adding a CI check to validate version consistency between these files in the future.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: capabilities.json#L4

Potential issue: The `version` field in `capabilities.json` is set to `"2.0.14"`, but
the actual package version defined in `package.json` is `"2.0.4"`. This metadata file is
consumed by the `wave-foundation/frameworks/platform-registry`. When this change is
merged, the registry will index a non-existent version of the SDK. This will cause
failures for any downstream systems or developers that rely on the registry for
dependency resolution or compatibility tracking, as they will be pointed to a version
that has not been published. Existing CI/CD pipelines do not validate the consistency
between these two files, so there are no safeguards to prevent this incorrect metadata
from being published.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[cubic-dev-ai]

1 issue found across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>