[L03TJ3]

Description

<wip, description coming shortly)

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

About # (link your issue here)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• PR title matches follow: (Feature|Bug|Chore) Task Name
• My code follows the style guidelines of this project
• I have followed all the instructions described in the initial task (check Definitions of Done)
• I have performed a self-review of my own code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have added reference to a related issue in the repository
• I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
• I have added screenshots related to my pull request (for frontend tasks)
• I have pasted a gif showing the feature.
• @mentions of the person or team responsible for reviewing proposed changes

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
good-wallet-v2	Ready	Preview	Jul 29, 2026 9:30am

[L03TJ3]

@blueogin could you verify the intended Wallet integration shape here and, if needed, follow up with Copilot to align the automation instructions?

At current head 940cfb7, the mismatch is already present within this PR:

• The generated task prompt asks a new integration to add both static entry loaders and follow the custom agent exactly. That prompt is sent to Agent Tasks with main as its base.
• The custom-agent instructions also require loaders for both entries.
• The documentation example stores both as entries.react and entries.webComponent.
• But the actual registry type in this same head uses a single entry selected by integrationMode: Web Component by default, or React explicitly.

This is an instruction/example inconsistency affecting generated integrations, not evidence of an existing Wallet runtime failure. The package descriptor can still advertise both supported exports without Wallet storing both loaders. Merging main into this branch alone would not automatically reconcile these instructions, since the single-entry registry is already here.

If the current single-entry host model is intended, please align the prompt, custom-agent instructions and documentation example, then validate the example and a generated new-widget integration against the current registry types/build/tests. If dual loaders are intended instead, please clarify the corresponding host/registry change needed before enabling the automation.