[HaroldLeo]

Summary

The published AWS Bedrock SSO plugin is missing from Magpie's community plugin list. Add its npm package, provider ID, and English/Chinese summaries to registry.json.

registry.json
  + AWS Bedrock SSO → magpie-aws-bedrock-sso → bedrock-sso

The plugin uses an AWS CLI profile, including SSO / IAM Identity Center, to call Bedrock Claude and GPT models with SigV4 authentication instead of a Bedrock API key.

• npm: https://www.npmjs.com/package/magpie-aws-bedrock-sso
• Source and documentation: https://github.com/HaroldLeo/magpie-aws-bedrock-sso
• Magpie is the tested host; direct OpenCode use is unverified.

Evidence

• Before: 60 registry entries; no magpie-aws-bedrock-sso listing.
  After: 61 entries; exactly one addition, with all existing entries unchanged.
• JSON parsing, unique package names, English/Chinese summaries, and git diff --check pass.
• Provider ID matches the plugin's exported bedrock-sso ID.
• Confirmed npm package magpie-aws-bedrock-sso, version 0.3.3, is published with canonical source metadata.
• The full Bun suite was not run locally; Bun is not installed in this checkout's environment.

Merge Danger

Door: two-way

The entry can be removed to revert the listing.

Blast Radius: discovery

Only registry.json changes. The plugin stays independently maintained on npm; no plugin source, package version, or existing registry entry changes.