PAB-8: materialize independent extension forks

[pablopunk]

Description

This PR introduces independent, self-contained extension forks. Previously, duplicating an extension created a file that imported and re-exported the original manifest—keeping the copy tied to the original and risking unintended edits. Now, duplication generates a standalone file that inlines the full extension definition, removes the dependency on the original, and properly scopes action IDs under the new extension identity (e.g., copy-id:hello-action).

What changed

• New utility createStandaloneExtensionFork in extension-manifest.ts: transforms an extension source string into a self-contained fork. It inlines the original object literal, applies the new ID and title, and re-maps all action IDs with the new extension prefix. Only extensions whose default export is an object literal can be forked (callable exports are rejected).

• Refactored duplication flow in main.ts: the duplicateCreatedAction handler now uses createStandaloneExtensionFork to build the fork and then activates it via stageExtensionProposal and activateManagedExtension, aligning duplication with the normal extension management pipeline.

• New tests in extension-manifest.test.ts: verify that the generated fork contains no import of the original, works correctly when loaded (correct identity and namespaced action IDs), and that non-object-literal exports are rejected.

Impact

• Duplicated extensions are now fully independent and can be freely edited by users or AI without affecting the original.
• Action IDs are automatically namespaced to avoid collisions across forks.
• The duplication process is more robust and consistent with how other extensions are registered.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nvm	Ready	Preview, Comment	Jul 18, 2026 11:58am

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	❌
Security	✅
Business Logic	❌

Access your configuration settings here.

​