pstack: add Benny issue automation pack

[poteto]

Summary

• add a dormant Benny source pack for thread-only issue triage and evidence-backed repro and fix workflows
• copy the pack into target repositories so live automations read committed files directly without exposing Benny as slash skills
• keep pstack enabled only for shared workflow dependencies and preserve user-owned configuration outside pack refreshes

Test plan

• node scripts/validate-plugins.mjs
• validate the manifest exposes only ./skills/, direct operational paths, Markdown links, JSON and YAML examples, frontmatter, and unique skill names
• scan the branch for discovery contradictions, private names, IDs, credentials, endpoints, and local plugin paths
• run git diff --check origin/main...HEAD and review the full branch diff

---

Note

Medium Risk
New automation workflows that can create tracker issues and draft PRs from Slack; mitigated by extensive guardrails, fail-closed behavior, and draft-only merges, but adopters must configure integrations correctly.

Overview
Bumps pstack to 0.10.0 and documents a new Benny automation pack under automations/benny/ (not registered in the plugin manifest—only ./skills/ remains exposed).

Benny is a dormant source pack for two coordinated Cursor automations on Slack issue reports: triage (classify, dedupe tracker, one thread-only verdict with [benny:bug] / [benny:performance] / [benny:other]) and repro-and-fix (wait for trusted triage markers, double UI repro via a pluggable control adapter, optional bounded fix and draft-only PRs). Setup is agent-driven via FOR_AGENTS.md: merge the pack into the target repo at .cursor/automations/benny/, enable pstack in that repo’s .cursor/settings.json for shared skills (how, why, tdd, unslop, principles), and keep user config outside the pack so refreshes don’t overwrite it. Live automations read committed SKILL.md paths directly—not slash skills or plugin cache.

The pack adds operational skills (triage-issue-reports, reproduce-and-fix-issues, setup-benny), reference docs (control adapter, feature map, routing, verify-existing-fix), YAML/templates, and strict fail-closed rules (immutable thread coordinates, no source-channel root posts, coordinator-only Slack writes, no worker Slack credentials).

^{Reviewed by Cursor Bugbot for commit 1028dd3. Bugbot is set up for automated code reviews on this repo. Configure here.}