catalog: rename "superpowers-bridge" to "superspec" (v1.0.1)

[WangX0111]

Description

This PR renames the catalog entry ID from superpowers-bridge to superspec and bumps the version to v1.0.1.

Why is it needed?

1. Avoid Naming Confusion: The primary reason for this rename is to prevent overlap and identity confusion with similar existing extensions/repositories in the ecosystem (such as @RbBtSn0w's "Superpowers Bridge", catalog ID: superb). Switching to superspec aligns the extension ID with our upstream repository name (WangX0111/superspec).
2. Fix Installation Failure: Version 1.0.0 was completely uninstallable from the catalog due to spec-kit's namespace validator rejecting the extension commands (speckit.superpowers.* did not match the catalog ID superpowers-bridge).

This version (v1.0.1) fixes the mismatch by strictly aligning everything (catalog ID, extension.id, all 5 command names, and all 3 hook command refs) under a single, distinct namespace: superspec.

Changes:

• Removed entry "superpowers-bridge" (v1.0.0).
• Added entry "superspec" (v1.0.1) in the correct alphabetical position.
• Updated download_url to point to the v1.0.1 archive.
• Preserved original created_at timestamp (2026-04-22).
• Set updated_at to 2026-05-30.

Impact on existing users:
None. Version 1.0.0 had downloads: 0 in the catalog because the validator blocked all initial installation attempts.

Testing

• Tested locally with uv run specify --help
• Ran existing tests with uv sync && uv run pytest
• Tested with a sample project (if applicable)

Additional Verification Details:

• ✅ URL https://github.com/WangX0111/superspec/archive/refs/tags/v1.0.1.zip is reachable (HTTP 200).
• ✅ Extension repository CI passes successfully on v1.0.1.
• ✅ Verified local installation: specify extension add ./superspec --dev successfully outputs superspec / Commands: 5 | Hooks: 3 | Status: Enabled.
• ✅ Confirmed archive contents: extension.yml correctly defines id: "superspec", and all command/hook namespaces use speckit.superspec.*.

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (describe below)

Used AI assistance for refine descriptions to ensure clarity and professional phrasing in the PR documentation.