Refresh OpenAPI registry snapshot

[eXamadeus]

Why

Refreshes the OpenAPI registry snapshot to pull in the latest spec from api.agentfacets.io.

---

Note

Low Risk
Generated snapshot-only update with no schema or runtime code changes.

Overview
Re-runs bun run codegen:registry in packages/engine to pull the current Agent Facets Registry OpenAPI document from https://api.agentfacets.io/v0/openapi.yaml into the committed vendored snapshot at openapi.snapshot.yaml.

The only change in this PR is the snapshot Generated-At metadata (2026-07-13 → 2026-07-20); the spec content is unchanged, which is expected when production’s published schema has not moved since the last sync.

^{Reviewed by Cursor Bugbot for commit 513f3b9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 513f3b9

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@eXamadeus, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: CHILL

Plan: Pro Plus

Run ID: e4ae7e25-948c-4445-b584-0bd6fa88e5e4

📥 Commits

Reviewing files that changed from the base of the PR and between 7b89aad and 513f3b9.

📒 Files selected for processing (1)

• packages/engine/src/registry/openapi.snapshot.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch julian/07-20-refresh_openapi_registry_snapshot

---

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

[eXamadeus]

• Replace openapi-freshness staleness check with live registry-compatibility type-check job #434
• Refresh OpenAPI registry snapshot #433 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

This PR refreshes the OpenAPI registry snapshot by re-running bun run codegen:registry, which pulls the current spec from api.agentfacets.io/v0/openapi.yaml.

• The only change is the Generated-At comment timestamp (from 2026-07-13T04:53:26.365Z to 2026-07-20T14:06:08.660Z), meaning the underlying spec content is identical to the previous snapshot.
• No schema, endpoint, or component definitions were added, removed, or modified.

Confidence Score: 5/5

Safe to merge — the snapshot content is unchanged and only the generation timestamp was updated.

The entire diff is a single-line timestamp update in a generated, read-only snapshot file. No API schema, endpoint, or security definition was touched, so there is no behavioral change in the engine.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Refresh OpenAPI registry snapshot" | Re-trigger Greptile}

[eXamadeus]

Merge activity

• Jul 20, 5:05 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 20, 5:05 PM UTC: @eXamadeus merged this pull request with Graphite.