Rename suite to Agentic Superpowers and require review-gated delivery

[bells0]

Why

The suite captures durable agentic-engineering practices that should evolve across model generations. Public identifiers therefore need a model-neutral identity instead of the gpt56-* namespace.

What changed

• renamed the suite, plugin metadata, documentation, examples, and all eleven Skill IDs to Agentic Superpowers / agentic-*;
• kept GPT-5.6 as a versioned model-profile input rather than the product identity;
• added transactional migration from the eleven legacy gpt56-* Skill IDs with exact restore behavior;
• made the Agent responsible by default for verified-baseline branch selection, atomic commits, feature-branch push, and PR creation or update;
• reserved approval and merge decisions for an independent reviewer or the user, with explicit authority still required for merge and other high-impact Git actions;
• added deterministic checks and routing evidence for dirty-default-branch protection, no stepwise Git requests, PR-not-approval semantics, and safe post-merge cleanup.

Delivery responsibility

The change request preauthorizes the Agent's mechanical branch, commit, push, and PR work. PR creation is not approval. This PR must not merge until an independent authorized reviewer or the user approves, required checks pass, and merge is explicitly authorized.

Verification

• make validate
  • eleven-Skill structure and plugin metadata: PASS
  • package budget: 5,474 / 5,800 words
  • dependency-aware routing and 14 scenarios: PASS
  • 5 global runtime tests: PASS
  • install/restore, legacy migration, rollback, collision, locking, and path-safety tests: PASS
• git diff --check: PASS

Commits

• e29ec4c — rename suite to Agentic Superpowers
• d99120f — require review-gated feature-branch delivery
• 5ebf9de — make Agent own Git delivery mechanics

Risks and dependencies

• The GitHub repository is still named bells0/gpt56-superpowers; documentation targets bells0/agentic-superpowers. The remote repository rename is a separate external transition and should be coordinated with merge/publication so links do not remain temporarily unresolved.
• Existing installations rely on the migration transaction; restore compatibility is covered by the smoke suite.
• No merge, force push, history rewrite, visibility change, or branch deletion is included in this PR update.

Review checklist

• Feature branch used; default branch unchanged
• Atomic commits pushed and PR updated by the Agent
• Local required validation passed
• Latest remote check run passed
• Independent reviewer or user approved
• Merge explicitly authorized
• Repository rename/publication transition coordinated