fix: reduce executable registry size

[LJAYi]

Summary

• stop generating full executable action ID arrays in the Node and Cloudflare provider registries
• use the loaded executor module service keys to identify locally executable providers
• resolve those services to the exact action IDs present in the loaded catalog before creating CatalogStore
• preserve explicit executableActionIds, runtime execution metadata, and public response shapes

This is the first of the two changes discussed in #235. Catalog asset chunking will follow in a separate PR.

Why

The generated Cloudflare registry repeated all 12,743 executable action IDs even though each included provider already has a lazy executor module entry. The existing generator marks every action from an included provider executable, so the executor module service keys carry the same information more compactly.

Wrangler size comparison

Measured from v1.3.3 and this branch with Wrangler 4.115.0, the same Cloudflare bindings/configuration, --dry-run, and --minify:

Build	Minified upload	Gzip
v1.3.3 baseline	11,935.15 KiB	2,854.70 KiB
This PR	11,566.36 KiB	2,777.99 KiB
Reduction	368.79 KiB	76.71 KiB

The emitted cloudflare.js decreased from 12,221,596 to 11,843,955 bytes, a reduction of 377,641 bytes.

Validation

• generated both provider registries for 1,194 total / 1,192 Cloudflare providers
• oxlint . --fix
• oxfmt .
• node scripts/typecheck.ts src scripts-all examples
• vitest run — 61 test files and 591 tests passed
• Wrangler dry-run builds for both baseline and optimized revisions

Refs #235

[coderabbitai]

Summary by CodeRabbit

• Improvements

  • Catalog loading now automatically identifies executable actions based on configured services.
  • Explicitly configured executable actions continue to be supported alongside service-based detection.
  • Server environments now use a simpler, more reliable provider configuration when determining which actions can run locally.

• Bug Fixes

  • Improved consistency between provider configuration and the actions presented as executable.

Walkthrough

The provider registry generator now emits only executorModules. Catalog loading accepts executable services, resolves their provider actions, merges explicit executable action IDs, and passes the resulting set to catalog-store creation. Cloudflare and server startup derive executable services from executor module keys. Tests cover combined service-based and explicit executable action resolution.

Sequence Diagram(s)

sequenceDiagram
  participant Server
  participant executorModules
  participant CatalogLoader
  participant CatalogStore
  Server->>executorModules: read service keys
  Server->>CatalogLoader: pass executableServices
  CatalogLoader->>CatalogLoader: resolve service actions and explicit IDs
  CatalogLoader->>CatalogStore: create catalog with executableActionIds

Loading

Possibly related issues

• Issue 235: The changes implement service-key-based executable action resolution instead of generated action-ID arrays.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title is related to the change, but it does not use the required <type>(<scope>): <subject> format.	Rename it to something like fix(registry): reduce executable registry size.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description matches the registry-size reduction and catalog-loading changes in the pull request.

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code

---

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

[coderabbitai]

🧹 Nitpick comments (1)

src/catalog-store.test.ts (1)

76-88: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add a negative service-selection assertion.

The fixture currently makes every action executable, so it would not catch a regression that marks all catalog actions as locally executable. Add an unselected action and assert it remains catalog-only.

Suggested test adjustment

-    const providers = [providerFixture("example", ["ping", "pong"]), providerFixture("remote", ["ping"])];
+    const providers = [providerFixture("example", ["ping", "pong"]), providerFixture("remote", ["ping", "pong"])];

     expect(catalog.executableActionIds).toEqual(new Set(["example.ping", "example.pong", "remote.ping"]));
     expect(catalog.actionsById.get("example.pong")?.execution.locallyExecutable).toBe(true);
+    expect(catalog.executableActionIds.has("remote.pong")).toBe(false);
+    expect(catalog.actionsById.get("remote.pong")?.execution.locallyExecutable).toBe(false);

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/catalog-store.test.ts` around lines 76 - 88, Update the test case in
“resolves every action from executable services alongside explicit action ids”
to include an action from a non-selected service, then assert that action
remains in the catalog but is not marked locally executable. Keep the existing
executable-service and explicit-action assertions unchanged.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/catalog-store.test.ts`:
- Around line 76-88: Update the test case in “resolves every action from
executable services alongside explicit action ids” to include an action from a
non-selected service, then assert that action remains in the catalog but is not
marked locally executable. Keep the existing executable-service and
explicit-action assertions unchanged.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cd0beeec-9d1a-4fb8-b30e-a359ec29040a

📥 Commits

Reviewing files that changed from the base of the PR and between a332575 and b84f3b9.

📒 Files selected for processing (6)

• scripts/generate-provider-registry.ts
• src/catalog-store.test.ts
• src/catalog-store.ts
• src/server/cloudflare.ts
• src/server/cloudflare/catalog-assets.ts
• src/server/index.ts

💤 Files with no reviewable changes (1)

• scripts/generate-provider-registry.ts