@jiroamato/pstack 0.0.0-stage → 0.15.15

package/pstack/automations/benny/skills/reproduce-and-fix-issues/references/verify-existing-fix.md

@@ -0,0 +1,93 @@
+# Verify an existing fix
+
+Use this mode when an open pull request or merged commit plausibly fixes the report.
+
+The existing artifact owns the fix. Verify it. Do not edit it, author a competing patch, or open another pull request.
+
+## Qualify the artifact
+
+Require one concrete artifact:
+
+- An open pull request with code changes that address the symptom
+- A merged pull request
+- A merged commit with matching code and intent
+
+A thread claim, tracker status, branch name, or cause hypothesis without a pull request or commit is not enough.
+
+When several artifacts exist, choose the one linked from the source thread or tracker. Otherwise choose the closest match to the affected code and state why.
+
+## Protect the working tree
+
+Use an isolated worktree or another clean checkout when the repository supports it. Do not overwrite user changes.
+
+Record:
+
+- Baseline revision
+- Patched revision
+- Pull request or commit URL
+- Build and environment inputs shared by both runs
+
+Use regular `github.com` pull request links.
+
+## Measure the baseline
+
+For an open pull request, use its base branch as the baseline.
+
+For a merged fix, use the revision immediately before the fix when that revision builds and represents the old behavior.
+
+Through the configured control adapter:
+
+1. Bring up the baseline app.
+2. Confirm the correct app and environment.
+3. Run the reported path through real UI actions.
+4. Observe the discriminating symptom.
+5. Reset and repeat it.
+6. Capture baseline recording, screenshot, and state check.
+
+If the symptom does not appear twice on the baseline, there is no baseline. Do not claim that the fix works.
+
+## Measure the patched build
+
+Build and run the pull request or fix commit with the same environment and data.
+
+1. Run the same UI path.
+2. Repeat it twice.
+3. Confirm that the broken state is gone.
+4. Confirm the expected state appears.
+5. Capture after recording, screenshot, and the same state check.
+
+Do not stop at compilation or tests. The after result must come from a running patched app.
+
+## Outcomes
+
+### Confirmed
+
+The baseline reproduces twice and the patched build resolves it twice.
+
+- Mark operations status as verified.
+- Link the artifact.
+- Post one concise source-thread reply after the source preflight.
+- Include the before and after result.
+- Open no pull request.
+
+### Insufficient fix
+
+The symptom appears on both baseline and patched builds.
+
+- Mark operations status as reproduced but not fixed.
+- Link the artifact and say it did not resolve the symptom.
+- Post the normal confirmed-repro source update if the run has not already used it.
+- Open no competing pull request.
+
+### Inconclusive
+
+The baseline does not reproduce, the patched app cannot run, or the evidence does not show the discriminating state.
+
+- Do not claim success.
+- State which half could not be measured.
+- Keep the result in the operations thread or run output.
+- Post nothing in the source thread unless a direct question requires an answer.
+
+## Cleanup
+
+Stop both builds, remove temporary profiles and captures according to retention policy, and return the repository to its prior state without discarding user work.

package/pstack/automations/benny/skills/setup-benny/SKILL.md

@@ -0,0 +1,271 @@
+---
+name: setup-benny
+description: Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
+disable-model-invocation: true
+---
+
+# Set up Benny
+
+Benny ships as a dormant automation pack inside pstack. The plugin manifest exposes only pstack's normal skill root; this file and the two operational files are not slash skills.
+
+The human enters setup by pointing their agent at the pack's `FOR_AGENTS.md`. The bootstrap flow copies the whole pack into the target repository, then reads this file directly at `.pstack/automations/benny/skills/setup-benny/SKILL.md`.
+
+Benny needs external configuration and two live automations (Claude Code scheduled tasks, or Codex Automations).
+
+Do not create or update an automation until the user explicitly asks. Never put a secret value in plugin files, prompts, or committed configuration.
+
+## 1. Copy the pack and enable shared pstack skills
+
+Do this before asking for Benny configuration and before invoking the harness's automation creator.
+
+Ask which repository will run the automations. The source pack is the directory containing `FOR_AGENTS.md`. The destination is `<target-repository>/.pstack/automations/benny/`.
+
+Merge the entire source pack into the destination:
+
+1. Create the destination when it is absent.
+2. Copy every source file to the same relative path.
+3. Preserve destination-only files. Never delete unrelated files during install or refresh.
+4. Keep user-owned configuration, feature maps, and routing maps outside the destination. Never overwrite them.
+5. When an existing source-managed file differs, inspect the diff and merge without discarding local edits. If ownership is ambiguous, stop and ask before replacing it.
+6. Verify that the destination contains `FOR_AGENTS.md`, this setup file, both operational files, their references, and the templates.
+
+If this file is already being read from the target destination, treat the copy as complete and run the same verification before continuing.
+
+Enable pstack for the target repository.
+
+On Claude Code, add it to the repository's `.claude/settings.json`. If the file or `.claude` directory does not exist, create it. Merge this into the existing JSON:
+
+```json
+{
+	"extraKnownMarketplaces": {
+		"pstack-plugins": {
+			"source": { "source": "github", "repo": "jiroamato/pstack" }
+		}
+	},
+	"enabledPlugins": { "pstack@pstack-plugins": true }
+}
+```
+
+Preserve every unrelated top-level setting and every other plugin entry. If the `pstack@pstack-plugins` entry already exists, change only its value. Validate the file after editing it.
+
+On Codex, plugins are user-scoped. Install pstack for the user who runs the automations with `codex plugin marketplace add jiroamato/pstack`, then `codex plugin add pstack`.
+
+Reload the target project or start a fresh agent rooted there. Verify that these shared pstack skills resolve from project scope:
+
+- `how`
+- `why`
+- `tdd`
+- `unslop`
+- `principle-separate-before-serializing-shared-state`
+- `principle-minimize-reader-load`
+- `principle-guard-the-context-window`
+- `principle-sequence-verifiable-units`
+- `principle-fix-root-causes`
+- `principle-prove-it-works`
+
+On Claude Code, do not count a skill loaded from the current session or a user-scoped plugin. The check must show that a fresh agent in the target repository receives pstack through project settings. On Codex, confirm the automation's user has pstack installed.
+
+If project-scoped plugin installation is unavailable or any shared dependency does not resolve, stop and explain the failure.
+
+The Benny files are read directly from `.pstack/automations/benny/`. Do not add that directory to a plugin manifest or expect its `SKILL.md` files to appear in the slash-skill list.
+
+Tell the user that the pstack settings (`.claude/settings.json` on Claude Code), `.pstack/automations/benny/`, and any referenced secret-free configuration must be committed before either automation is enabled. Do not commit them unless the user asks.
+
+Once this check passes, live automation prompts may read the committed operational files by their stable repository-relative paths. They must not embed a plugin cache path or copy the file contents.
+
+## 2. Adapt the configuration
+
+Open these copied examples:
+
+- `../../templates/configuration.example.yaml`
+- `../reproduce-and-fix-issues/references/feature-map.example.md`
+
+Create user-owned copies outside `.pstack/automations/benny/`. These are configuration files, not pack files. Example locations:
+
+- Project config, such as `.pstack/benny/configuration.yaml`
+- Project feature map, such as `.pstack/benny/feature-map.md`
+- Project routing map, such as `.pstack/benny/routing.md`
+- User config, such as `~/.config/benny/configuration.yaml`
+- User feature map, such as `~/.config/benny/feature-map.md`
+
+Fill one feature-map section for every user-facing feature the automation may reproduce. Keep it at the user point of view. Do not freeze implementation details or current code paths in the map.
+
+Do not edit the copied examples. Pack refreshes may update source-managed files after conflict review, but they must never touch the user-owned copies.
+
+Prefer committed, secret-free files in the target repository when a fresh automation checkout must read them. Otherwise paraphrase the required values into the live prompt. Reference a repository file only after the automation creator confirms that the file is committed in the repository where the automation runs.
+
+Use stable repository-relative paths for committed pack and configuration files. Never reference the plugin source directory or a plugin cache path from a live automation.
+
+## 3. Fill the required choices
+
+Ask for or confirm:
+
+- Source Slack channel ID
+- Optional operations or status channel ID
+- Repository URL and default branch
+- Triage identity or Slack user ID
+- Issue tracker type, team, project, labels, and intake status
+- Tracker adapter skill or MCP actions
+- Optional routing map path
+- Required app-specific verification skill name (uses bundled pstack `control-ui` for web/IDE/Electron)
+- Required user-facing feature-map path
+- Status emoji strings
+- Pull request URL format
+- Polling and effort budgets
+- Model slug for triage, repro, code work, and media review
+
+Use only model ids shown as available in the user's model picker or supported model list. Do not guess a slug and do not carry over a private default.
+
+The source channel, triage identity, repository, tracker adapter, app-specific verification skill, and feature map must be explicit. Fail setup if any required value stays ambiguous. There is no separate generic `control` skill; web/IDE/Electron driving uses bundled pstack `control-ui` with the configured app-specific adapter.
+
+Use pstack's `unslop` skill on the final automation names, descriptions, and prompt shims before saving them.
+
+## 4. Check integration capabilities
+
+The triage automation needs:
+
+- Read access to the configured source Slack channel and its threads
+- Thread-reply access in that channel
+- Attachment metadata and file download access when reports include media
+- Search, read, create, and update access through the configured issue-tracker adapter
+
+The repro automation needs:
+
+- Read access to the source thread
+- Thread-reply access in the source channel
+- Optional post and edit access in the configured operations channel
+- Repository read and history access
+- A pull request action that can open a draft pull request
+- The configured control-adapter skill
+
+Prefer the Slack actions your harness provides (a Slack MCP server or channel) for reads and posts. The optional `BENNY_SLACK_BOT_TOKEN` may fill a narrow gap such as editing one operations status message or downloading an attachment. Store the value in a secret manager or environment, not in YAML.
+
+Do not use undocumented integration endpoints.
+
+## 5. Prepare the routing map
+
+If the user wants reroutes or owner pings:
+
+1. Copy `../triage-issue-reports/references/routing.example.md` outside `.pstack/automations/benny/`.
+2. Replace every placeholder with public or organization-local values.
+3. Keep owner pings off by default.
+4. Allow a ping only for a configured feature owner or a confirmed likely regression author.
+
+If no routing map is configured, triage may classify a report but must not guess a destination or owner.
+
+## 6. Verify the control adapter
+
+Read `../reproduce-and-fix-issues/references/control-adapter.md` and the user's completed feature map.
+
+Confirm that the named skill can:
+
+- Bring up the target app
+- Navigate every mapped feature through the real UI
+- Exercise mapped states through declared adapter actions
+- Inspect state without forcing the result
+- Capture screenshots
+- Start and stop a recording
+- Clean up its processes and temporary data
+
+If any capability is missing, leave the repro automation disabled. It must fail closed rather than claim a reproduction it did not perform.
+
+## 7. Prepare the live automations
+
+Ask whether this is first-time creation or configuration of existing automations.
+
+Read `../../FOR_AGENTS.md` from the copied pack as the primary user-intent source for either path. Use it to understand the two triggers, tools, instructions, outcomes, and shared rules.
+
+### First-time creation
+
+Create one automation at a time.
+
+For each automation:
+
+1. Read the matching copied prompt template as secondary internal source material.
+2. Turn `FOR_AGENTS.md`, the finished Benny configuration, and the template intent into a complete natural-language request.
+3. Tell the live prompt to read and follow its exact committed operational file under `.pstack/automations/benny/`.
+4. Use the stable repository-relative path, not a plugin source or cache path. Do not copy the operational file contents into the live prompt.
+5. Read and follow the harness's automation creator (the `schedule` skill on Claude Code, the Automations editor in the Codex app).
+6. Let it discover Slack channels, the repository, and connected integrations.
+7. Let it confirm that the copied pack and any referenced configuration files are committed in the same repository where the automation will run.
+8. Let it show its draft, obtain approval, ask readiness, and open the automation editor.
+9. Finish the editor handoff for this automation before starting the next one.
+
+Give the automation creator this complete triage intent, filled from configuration:
+
+- Name `benny-triage`.
+- Read and follow `.pstack/automations/benny/skills/triage-issue-reports/SKILL.md` for every run.
+- Trigger on each new top-level report in the configured source Slack channel.
+- Read the triggering thread and reply only inside it.
+- Use the configured issue-tracker integration.
+- Classify, inspect evidence, trace cause, dedupe, and create only clear new bugs.
+- End one thread-only verdict with the configured `[benny:bug]`, `[benny:performance]`, or `[benny:other]` marker and optional tracker URL.
+- Never post a source-channel root message.
+
+After the triage editor handoff is complete, give the automation creator this complete repro and fix intent:
+
+- Name `benny-reproduce`.
+- Read and follow `.pstack/automations/benny/skills/reproduce-and-fix-issues/SKILL.md` for every run.
+- Trigger on the same new top-level reports in the configured source Slack channel.
+- Use the configured repository and default branch.
+- Read the source thread and reply only inside it.
+- Include pull request creation and the configured tracker, control-adapter, and feature-map requirements. Paraphrase mapped user paths and states unless the automation creator confirms an eligible committed file in the same repository.
+- Wait for a trusted triage marker before acting.
+- Reproduce the exact symptom twice through the mapped real UI and capture evidence.
+- Verify an existing fix without authoring over it.
+- Attempt an optional bounded fix only after confirmed repro, then open a draft pull request when proof and checks pass.
+- Never post a source-channel root message.
+
+Do not duplicate the automation creator's Slack, repository, integration, completeness, authentication, draft-review, approval, readiness, or editor-handoff work.
+
+### Existing automations
+
+The automation creator is creation-only. Do not use it to search for, inspect, or update existing automations.
+
+Finish configuration, routing, control-adapter, and feature-map validation. Then give the user this concise editor checklist.
+
+For the existing triage automation, update:
+
+- Name and description
+- Direct instruction to read `.pstack/automations/benny/skills/triage-issue-reports/SKILL.md`
+- New top-level Slack report trigger and source channel
+- Slack thread read and reply capabilities
+- Issue-tracker integration
+- Paraphrased triage instructions, thread-only rule, and Benny verdict markers
+
+For the existing repro automation, update:
+
+- Name and description
+- Direct instruction to read `.pstack/automations/benny/skills/reproduce-and-fix-issues/SKILL.md`
+- Matching Slack trigger and source channel
+- Repository and default branch
+- Slack thread read and reply capabilities
+- Pull request action
+- Tracker, control-adapter, and feature-map requirements
+- Paraphrased marker wait, evidence, verification, and bounded-fix instructions
+
+Ask the user to update each existing automation directly in its automation editor. Do not create replacements or duplicates.
+
+### Creation boundary
+
+Never call a direct automation backend service or backend automation tool. Never use a browser URL that carries draft fields. Never build or open a harness deep link. For new automations, the only finish path is the automation creator's reviewed editor handoff.
+
+Do not enable either automation until the thread-safety test passes after the editor save.
+
+## 8. Test thread safety
+
+Use a test channel or a harmless test report.
+
+Before testing, confirm that the target repository's pstack settings (`.claude/settings.json` on Claude Code), `.pstack/automations/benny/`, and every referenced secret-free configuration file are committed on the branch used by the automation checkout. Confirm that both live prompts point at their exact committed operational files. If any check fails, stop. Tell the user that the automation cannot be enabled yet.
+
+Verify:
+
+1. Triage stores the root `thread_ts` and posts exactly one verdict as a reply.
+2. The verdict contains one configured marker.
+3. Repro accepts the marker only from the configured triage identity.
+4. Repro keeps the same immutable source coordinates.
+5. No source-channel root message appears.
+6. A delegated worker cannot use any Slack write action.
+7. Missing coordinates, a deleted parent, or a failed preflight produces no post and no tracker issue.
+
+Enable normal traffic only after all seven checks pass.

package/pstack/automations/benny/skills/triage-issue-reports/SKILL.md

@@ -0,0 +1,240 @@
+---
+name: triage-issue-reports
+description: Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
+disable-model-invocation: true
+---
+
+# Triage issue reports
+
+Classify one Slack report and post one useful verdict in its source thread. Create a tracker issue only for a clear, new bug. Do not reproduce or fix it here.
+
+Load the external Benny configuration supplied by the automation. If the config is missing, malformed, or incomplete, stop without posting or writing to the tracker.
+
+## Hard safety rules
+
+- The source channel and root thread coordinates are immutable.
+- Never post a root message in the source channel.
+- Never post to another channel, broadcast a reply, send a DM, or start a replacement thread.
+- Preflight the source parent before any tracker write and immediately before the verdict post.
+- If the parent is missing, deleted, inaccessible, or uncertain, stop with no writes.
+- Post one substantive verdict. Do not narrate progress.
+- The coordinator is the only Slack poster.
+- Delegated workers return findings only. They must be read-only and receive no Slack credentials or write actions.
+- Every child prompt must forbid `SendSlackMessage`, `PostToSlack`, `chat.postMessage`, and every other Slack write.
+- If worker isolation cannot enforce those limits, do the work in the coordinator.
+- Never create an issue that cannot link back to the source thread.
+- Prefer no ticket over a guessed or duplicate ticket.
+- Apply pstack's `principle-separate-before-serializing-shared-state` to source coordinates.
+- Apply pstack's `principle-minimize-reader-load` and `unslop` skills to the final verdict.
+
+## 1. Freeze source coordinates
+
+Before making a work list or delegating:
+
+1. Read `source_channel_id` from the trigger.
+2. Require it to equal the configured source channel.
+3. Set `SOURCE_THREAD_TS` to `trigger.thread_ts` when present. Otherwise use `trigger.ts`.
+4. Require a nonempty `SOURCE_THREAD_TS`.
+5. Store `SOURCE_CHANNEL_ID` and `SOURCE_THREAD_TS` as immutable values.
+6. Read the thread and verify that its root has exactly those coordinates.
+7. Fetch a stable source permalink.
+
+Every later source read and post must use those stored values. Never replace them with a reply timestamp or an operations-thread timestamp.
+
+## 2. Read the whole report
+
+Read the root and current replies before deciding.
+
+Capture:
+
+- Reporter wording
+- Product version, app build, environment, and platform when present
+- Expected behavior
+- Observed behavior
+- Frequency and trigger
+- Error text or stack signature
+- Existing issue, commit, or pull request links
+- Any explicit statement that someone is already fixing it
+
+Inspect every relevant attachment.
+
+- Read screenshots at full useful resolution.
+- Review video for the state transition that separates correct and broken behavior.
+- Read logs, traces, and crash text for concrete signatures.
+- If media needs specialist review, use a read-only media worker and ask a narrow question. The worker returns findings only.
+- If an attachment cannot be read, say so in the verdict. Do not invent what it shows.
+
+Use evidence already in the thread before asking the reporter for more.
+
+## 3. Trace cause before routing
+
+Do a bounded source and history pass before choosing an owner or destination. Use pstack's `how` skill to trace the path from the reported action to the observed result. Use `why` when the report looks like a regression or touches defensive code.
+
+1. Identify the likely code path from the reported action to the observed result.
+2. Check whether the visible symptom belongs to that code path or a dependency below it.
+3. Check recent changes when the report looks like a regression.
+4. Check whether a merged commit or open pull request already addresses the same symptom.
+5. Separate confirmed facts from hypotheses.
+
+This pass does not need a complete root cause. It must be strong enough to avoid routing a visible symptom to the wrong owner.
+
+If the repository cannot be read, do not guess a code owner. Continue with a conservative classification and say that cause tracing was unavailable.
+
+## 4. Classify
+
+Choose one category.
+
+### Bug
+
+Something violates intended behavior. Examples include wrong output, broken state, an error, a crash, a hang, a silent no-op, or a regression.
+
+### Performance
+
+The report describes measurable slowness, excess memory, battery drain, jank, or another resource problem. Treat it as a bug, but preserve measurements and profiles.
+
+### Feature request
+
+The current behavior appears intentional and the reporter wants a different behavior or affordance.
+
+### Question or feedback
+
+The report asks how something works, expresses a preference without a concrete defect, or gives general feedback.
+
+### Reroute
+
+Cause tracing shows that another configured destination owns the issue.
+
+When the bug versus feature line is unclear, do not file. The one verdict may ask one focused question and use the `other` marker.
+
+## 5. Apply configured routing
+
+Read the optional routing map from `routing.map_path`.
+
+- Match on confirmed product area, code path, or error signature.
+- A visible symptom alone is not enough when cause tracing points elsewhere.
+- If no route matches, say the owner is unclear. Do not guess.
+- Do not cross-post. Tell the reporter where to take the issue in the source thread.
+
+Owner pings are off by default. A ping is allowed only when all of these hold:
+
+1. The routing map explicitly names the owner.
+2. The config allows that ping type.
+3. The item is a feature request that needs owner input, or recent history identifies a likely regression author with strong evidence.
+4. The owner is not a broad on-call group.
+
+No other case gets a ping.
+
+## 6. Use the issue-tracker adapter
+
+The tracker is an adapter, not a required vendor. A Linear adapter is one valid example. A GitHub Issues adapter or another tracker may implement the same contract.
+
+The configured adapter must provide:
+
+- Search issues by text, state, label, source URL, and date range
+- Read one issue and its links
+- Create an issue with title, body, status, labels, and source URL
+- Update an existing issue without replacing unrelated fields
+- Add a source link and recurrence note
+- Cancel, close, or delete an issue created by this run if the Slack handoff fails
+
+If a required operation is unavailable, fail closed for that write.
+
+Resolve configured team, project, status, and labels at runtime. Do not invent IDs, create labels, assign owners, or set priority unless the config explicitly requires it.
+
+## 7. Dedupe
+
+Always check whether this source permalink is already linked to a tracker issue or a prior triage reply. If so, do not post or create a duplicate.
+
+For bugs and performance reports, search the tracker using:
+
+- Exact error or crash signature
+- Product area
+- Trigger
+- Symptom
+- Version or date window
+- Suspected regression commit
+- Source permalink
+
+Choose one outcome:
+
+- Confident duplicate: same signature, or the same area, trigger, and symptom, or a confirmed shared cause.
+- Possibly related: a shared cause is plausible but not proven.
+- Weak resemblance: similarity is superficial.
+- No match.
+
+For a confident duplicate, update the existing issue with the source permalink and one short recurrence note. Do not reopen, relabel, or reassign it unless the config says to.
+
+For a possible match, link it in the verdict as uncertain and create nothing.
+
+A long-closed issue is a regression lead, not automatically a live duplicate.
+
+## 8. Decide whether to create
+
+Create only when all of these are true:
+
+1. The classification is bug or performance.
+2. The behavior is clearly broken.
+3. The issue is still live or not known to be fixed.
+4. Dedupe found no confident or plausible live match.
+5. The source parent and permalink passed preflight.
+6. The tracker target fields resolved.
+7. The adapter can compensate if the verdict post fails.
+
+Never create for a feature request, question, feedback item, reroute, possible duplicate, confident duplicate, or already-fixed issue.
+
+The new issue must be self-contained:
+
+- Plain title that names the area and symptom
+- Reporter quote
+- Expected and observed behavior
+- Version and environment, or `unknown`
+- Trigger and frequency
+- Source thread permalink
+- Short cause-tracing findings with hypotheses labeled as hypotheses
+- Inline screenshot or representative video frame when supported
+- Links to remaining artifacts
+- Configured intake status and labels
+
+Do not put a guessed root cause in the title.
+
+## 9. Post one verdict
+
+Run a fresh source-parent preflight. Then post exactly one reply with `channel=SOURCE_CHANNEL_ID` and `thread_ts=SOURCE_THREAD_TS`.
+
+Never call a source-channel posting action without a nonempty `thread_ts`.
+
+Keep the reply short:
+
+- Lead with the outcome.
+- Link the existing or new tracker issue when there is one.
+- Mention a reroute or one missing fact when needed.
+- Include at most one allowed owner ping.
+- End with exactly one marker line.
+
+Marker contract:
+
+```text
+[benny:bug]
+[benny:bug] tracker=https://tracker.example/issue/123
+[benny:performance]
+[benny:performance] tracker=https://tracker.example/issue/123
+[benny:other]
+```
+
+Use only the configured marker strings. The repro automation trusts the marker only when it comes from the configured triage identity in this source thread.
+
+After posting, read the same source thread and verify the verdict appears under `SOURCE_THREAD_TS`. If it does not, never retry at the root.
+
+If this run created a tracker issue and the verdict did not land, use the adapter's compensation action. Verify that the issue is canceled, closed, or deleted. If compensation cannot be verified, report the failure only in the automation run output.
+
+## 10. Watch one follow-up window
+
+Watch the source thread for the configured follow-up window, then stop.
+
+- Answer only a direct question to the triage identity.
+- Apply a concrete correction to the tracker issue when safe.
+- Do not emit a second marker in the same run.
+- Stay out of human coordination and side chatter.
+- Stop early if someone asks the automation to stop.
+
+Do not extend the window more than once. A new report should start a new run.

package/pstack/automations/benny/skills/triage-issue-reports/references/routing.example.md

@@ -0,0 +1,61 @@
+# Routing map example
+
+Copy this file outside `.pstack/automations/benny/`, for example to `.pstack/benny/routing.md`, and replace every placeholder. Point `routing.map_path` at the copy. Pack refreshes must not overwrite it.
+
+The triage skill treats this as data. A route needs evidence from the report or cause trace. A keyword match alone is not enough.
+
+```yaml
+routes:
+  - name: "billing-example"
+    match:
+      product_areas:
+        - "billing-area-placeholder"
+      code_paths:
+        - "billing-code-path-placeholder"
+      error_signatures:
+        - "billing-error-placeholder"
+    destination:
+      slack_channel: "billing-channel-placeholder"
+      tracker_team: "billing-team-placeholder"
+    owners:
+      - "billing-owner-placeholder"
+    allow_feature_owner_ping: false
+
+  - name: "desktop-example"
+    match:
+      product_areas:
+        - "desktop-area-placeholder"
+      code_paths:
+        - "desktop-code-path-placeholder"
+      error_signatures:
+        - "desktop-error-placeholder"
+    destination:
+      slack_channel: "desktop-channel-placeholder"
+      tracker_team: "desktop-team-placeholder"
+    owners:
+      - "desktop-owner-placeholder"
+    allow_feature_owner_ping: false
+
+fallback:
+  destination: ""
+  owners: []
+  allow_feature_owner_ping: false
+
+ping_policy:
+  default: "off"
+  allow:
+    - "configured-feature-owner"
+    - "confirmed-regression-author"
+  deny:
+    - "broad-on-call-group"
+    - "unverified-owner"
+```
+
+## Rules
+
+- Leave `fallback.destination` empty unless one team accepts all unmatched reports.
+- Use stable product areas, code paths, and error signatures.
+- Do not include private data in a public copy.
+- Do not paste raw user or channel IDs into an example that will be published.
+- Keep feature-owner pings off until the target team agrees to them.
+- A reroute tells the reporter where to go. The automation never cross-posts.