chore: remove superseded eval dispatch implementation plan

[mrizzi]

Summary

• Remove docs/superpowers/plans/2026-05-07-eval-pr-fork-dispatch.md — a process artifact from the subagent-driven development workflow that was accidentally included in PR feat(ci): dispatch eval execution for fork PR secret access #123

The plan describes the original artifact-based design which was replaced during security hardening. It contains stale YAML with security vulnerabilities (artifact poisoning, ${{ }} injection) that were fixed in the implementation but never backported to the plan. The spec at docs/specs/2026-05-07-eval-pr-fork-dispatch-design.md is the authoritative document.

Test plan

• No functional changes — documentation removal only

🤖 Generated with Claude Code

Summary by Sourcery

Documentation:

• Delete the outdated eval PR fork dispatch plan document from the superpowers plans docs directory.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes an outdated and security-sensitive eval dispatch implementation plan document that was superseded by the main design spec, with no functional or runtime changes.

File-Level Changes

Change	Details	Files
Remove a superseded eval PR fork dispatch implementation plan document that contained stale, insecure YAML examples.	Delete the outdated plan markdown file from the superpowers plans documentation tree Rely on the existing design spec document as the authoritative reference for the eval dispatch behavior Ensure no runtime or configuration code paths reference the removed plan, keeping the change documentation-only	docs/superpowers/plans/2026-05-07-eval-pr-fork-dispatch.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}