dsh-pstack 0.1.0 → 0.2.0-beta.3

package/dist/assets/skills/why/references/sources/databricks.md

@@ -1,70 +0,0 @@
-# Databricks Analytics & System Tables
-
-## What this source contains
-
-Databricks is the product-analytics, data-pipeline, and warehouse-telemetry layer. It complements Datadog. Datadog is the *infra/runtime* view, Databricks is the *product/data* view (what users did, which experiments ran, how feature usage evolved, where a threshold constant came from).
-
-- **Product analytics events.** `your_warehouse.events.analytics_track_event` (raw) and typed, deduplicated per-event dbt models in `<your_analytics_db>.<schema>.<table>`. User behavior: feature invocations, clicks, accepts/rejects, submissions, client-reported errors.
-- **Usage & billing events.** `your_warehouse.events.usage_event` / `<your_analytics_db>.<schema>.stg_usage_events`, `your_warehouse.events.raw_model_event` / `<your_analytics_db>.<schema>.stg_raw_model_events`. For cost- or volume-driven decisions.
-- **Experiment / feature-flag data.** Exposure and outcome tables. **Schema is company-specific.** Probe with `SHOW TABLES` before assuming names.
-- **System tables.** `system.query.history`, `system.compute.warehouses`, `system.billing.*`, `system.access.audit`. Answer "was this query expensive?", "how often did anyone run this?", "when did warehouse load spike?"
-- **dbt lineage.** Models in `<your_analytics_db>.<schema>` reveal what pipelines depend on a table/field. Upstream changes frequently motivate consumer-code changes.
-- **Databricks notebooks.** Exploratory analyses engineers wrote before code changes. **Not queryable via the SQL MCP.** If you suspect the rationale lives in a notebook, name it as a gap.
-
-## How to search it
-
-Use the Databricks SQL MCP. Primary tool: `execute_sql_read_only`. If it returns a `statement_id`, poll with `poll_sql_result` rather than re-running.
-
-**Orient before querying.** Schemas are company-specific. Probe before trusting a table name:
-
-```sql
-SHOW TABLES IN <your_analytics_db>.<schema> LIKE '*<keyword>*';
-DESCRIBE TABLE <your_analytics_db>.<schema>.stg_<event>;
-```
-
-**Time-bound every query.** These tables are huge and unconstrained scans time out. Filter on `_timestamp` (events) or `start_time` (`system.query.history`) with a window bracketing the ship date, typically ~30 days before and after, wider only for strong reason.
-
-**Prefer typed dbt models over the raw table.** `<your_analytics_db>.<schema>.<table>` is deduplicated, typed, and liquid-clustered. `your_warehouse.events.analytics_track_event` has duplicates and untyped `properties_json`. Model-name pattern: `stg_<source>_<event_name_with_underscores>`, where `<source>` is `app`, `backend`, `website`, or `cli`. Confirm the exact model name with `SHOW TABLES` when the pattern alone doesn't resolve it. Drop to the raw table only when there's no dbt model yet, or you need events from inside the dbt refresh lag.
-
-**Column conventions on the typed dbt models** (knowing these avoids a `DESCRIBE` round-trip):
-
-- `_timestamp`, `_id`, `_auth_id`, `_request_id`, `event_name`. Standard on every model
-- `properties_<name>`. Typed, underscore-cased event properties (`properties_entrypoint`, `properties_size_bytes`, …)
-- `context_team_id`, `context_client_version`, `context_country`, `context_client_os`. Pre-extracted client context
-
-### Investigation patterns that tend to pay off
-
-Pick the table + column combination that matches the target:
-
-1. **Event usage trajectory.** Daily counts on the relevant `stg_*` model across a ±30d window around the PR merge. A step function from zero to steady volume within a day or two of the merge is strong circumstantial evidence the PR launched the feature. A decay to zero suggests a deprecation or deletion.
-2. **Guard-rail / defensive-check origin.** Distribution (median / p99 / max) of the relevant `properties_<name>` column in the 14 days *before* the PR. A p99 that matches the target's threshold constant suggests the number was chosen from data.
-3. **Experiment / feature-flag lookup.** `SHOW TABLES ... LIKE '*experiment*'` to find the exposure table, then pull exposure counts by variant for the relevant flag key near the PR date.
-4. **Query-history evidence for migrations, backfills, or perf rewrites.** `system.query.history` filtered by `statement_text ILIKE '%<table_or_symbol>%'` with a tight `start_time` window surfaces the expensive queries that likely motivated the change (sort by `total_duration_ms` or aggregate `SUM(read_bytes)`, `COUNT(*)`).
-5. **dbt lineage.** If the target reads from or writes into a `<your_analytics_db>.<schema>` model, the model's own git history (in this repo) often carries the rationale. Hand that lead back to the git investigator rather than chasing it yourself.
-
-## What good evidence looks like here
-
-Beyond the pattern shapes above:
-
-- An error-classifying event's count drops to near zero in the days after a defensive-code PR. Suggests the PR resolved that error class
-- An exposure table row names the target's feature-flag key with a "shipped" / "concluded" decision around the PR ship date
-
-## Common pitfalls
-
-- **Instrumented ≠ caused.** An event's existence means someone cared enough to log it, not that the target code exists *because* of it. Pair with a PR/commit citation from the git investigator before claiming causation.
-- **Silent instrumentation changes.** A step function in event volume may mean a new event started being logged, not that user behavior changed. Check for instrumentation PRs in the same window before reading the ramp as a feature-launch signal.
-- **Schema drift.** Event properties evolve. A column on the typed dbt model today may not have existed when the target was written. Older data may carry the property only inside raw `properties_json`.
-- **dbt refresh lag.** `<your_analytics_db>.<schema>.*` is rebuilt on a schedule (often hourly/daily). For events from the last few hours, fall back to `your_warehouse.events.*` and deduplicate by `_id`.
-- **Company-specific tables.** Experiment, feature-flag, billing, and usage tables vary. Reporting a result from a table whose existence you never confirmed is a classic failure mode. Probe with `SHOW TABLES` / `DESCRIBE TABLE` first.
-- **Retention cliff.** If the relevant window predates the table's retention or the dbt model's creation date, that's a *gap*, not a null result. Name it explicitly so the synthesizer doesn't read "no results" as "no activity."
-- **Notebooks aren't queryable.** The SQL MCP can't see Databricks notebooks. If you suspect the rationale lives in one, return a gap.
-
-## What to return
-
-For each relevant finding:
-- Type (product event / experiment exposure / usage or billing event / system-table row / dbt model)
-- Fully-qualified table name and the exact query you ran
-- Time window queried
-- Compact numeric summary (counts, percentiles, first/last-seen timestamps). **Don't dump raw rows.**
-- Temporal correlation with the target's ship date (e.g., "first row 2024-08-15, PR #49074 merged 2024-08-14")
-- Relevance + strength: direct / circumstantial / weak

package/dist/assets/skills/why/references/sources/datadog.md

@@ -1,97 +0,0 @@
-# Datadog Telemetry
-
-## What this source contains
-
-Datadog holds the runtime record, what actually happened in production, as opposed to what was planned or discussed.
-
-- **Metrics.** Counters, gauges, histograms instrumented by the team. A metric's *presence* is itself evidence that someone thought the number worth watching.
-- **Monitors & alerts.** Conditions the team decided warranted waking someone up. A monitor firing on `rate_limit_hit > 10/min` is direct evidence the team worried about that threshold.
-- **Dashboards.** Curated views of what the team considers important for a subsystem.
-- **APM traces & spans.** Request-level runtime data, for "why is this slow" / "why is there a timeout here" questions.
-- **Logs.** High-volume event records, often holding the error conditions that motivated defensive code.
-- **Incidents.** Formal incident records with timelines and linked postmortems.
-- **Notebooks.** The team's exploratory investigations, often with hypotheses and analyses.
-
-## How to search it
-
-Use the Datadog MCP. Start broad, then narrow.
-
-1. **Identify the owning service(s).**
-
-   ```
-   search_datadog_services (filter by name or team)
-   search_datadog_service_dependencies (see upstream/downstream)
-   ```
-
-2. **Dashboards and monitors first.**
-
-   ```
-   search_datadog_dashboards (query: feature name, service name, symbol)
-   search_datadog_monitors   (same queries)
-   ```
-
-   When a dashboard or monitor covers the target, note its queries and watched thresholds. The threshold is frequently the answer to "why is this clamped at N?"
-
-3. **Metrics around the target.**
-
-   ```
-   search_datadog_metrics (by name pattern, e.g., the feature or symbol)
-   get_datadog_metric_context (metadata: description, units, tags)
-   get_datadog_metric (timeseries; "was there a spike around the PR date?")
-   ```
-
-   Correlating a metric's trajectory with the target's add/change date is strong supporting evidence: "the `payment_timeout` metric spiked 2023-11-03, and the retry logic merged 2023-11-06."
-
-4. **Logs. Narrow, don't dump.**
-
-   ```
-   search_datadog_logs (raw log patterns near the target, set use_log_patterns=true)
-   analyze_datadog_logs (SQL-style aggregations, only when you need counts)
-   ```
-
-   Search with symbols, error strings, or feature names. **Strongly prefer time-bounded queries** (e.g., 30 days before/after the change).
-
-5. **APM spans and traces.**
-
-   ```
-   aggregate_spans    (stats: "how often does this endpoint fail?")
-   search_datadog_spans (inspect individual spans)
-   get_datadog_trace  (a specific trace ID)
-   ```
-
-   Useful for timeouts, retries, slow paths, and cross-service behavior.
-
-6. **Incidents.**
-
-   ```
-   search_datadog_incidents (by title, team, date range)
-   get_datadog_incident     (full detail for a specific incident)
-   ```
-
-   If the target looks defensive, search for incidents around the time it was added. An incident whose timeline includes "added defensive check for X" is near-direct evidence.
-
-## What good evidence looks like here
-
-- A monitor whose query and threshold match the constraint the code enforces (code clamps to 100, monitor alerts when requests exceed 100/min)
-- A dashboard created by the target's author, with widgets that correspond to what the code measures or guards against
-- A metric showing a production spike immediately before the code was merged, and stable values after
-- An incident record referencing the target code, the same symbols, or the same error strings
-- Logs showing a specific error pattern the defensive code would prevent, timestamped in the window before the change
-
-## Common pitfalls
-
-- **Correlation is not causation.** A spike before a PR and stabilization after is suggestive, not definitive, since other changes may have landed in the same window. Check neighboring PRs.
-- **Overfitting to the chart you found.** A chart reflects its maker's framing. A chart named "retry success rate" is evidence the team cared about retry success, not that it's why a specific line of code exists.
-- **Vanished telemetry.** Metrics can be renamed, deleted, or have short retention. If you can't find data from the relevant window, that's a gap, not a null result.
-- **Noise at scale.** Narrow log searches by service, tag, and time window aggressively. Use `analyze_datadog_logs` to aggregate rather than dumping raw logs.
-- **Instrumented != caused.** A metric shows someone cared enough to measure something, not that the code was added *because* of it. Cross-reference with commit/PR dates.
-
-## What to return
-
-For each relevant item:
-- Type (dashboard / monitor / metric / log pattern / trace / incident / notebook)
-- Title or name
-- Link or identifier (dashboard ID, monitor ID, metric name, incident ID)
-- Owner/author and created/modified date
-- The specific condition, query, or quote that bears on the question (verbatim where possible)
-- Relevance: what this suggests about the target code, and how strong the connection is

package/dist/assets/skills/why/references/sources/incident-postmortem.md

@@ -1,5 +0,0 @@
-# Incident & Postmortem Context
-
-- **Linear**: look for tickets labeled `incident`, `sev-*`, `postmortem-action-item`, `reliability`
-- **Slack**: search `#sev-*` and `#incident-*` channels around the dates the target code was added
-- **Git**: commits with messages like "fix for incident", "add defensive check", "revert" followed by "re-apply with..." are strong signals

package/dist/assets/skills/why/references/sources/linear.md

@@ -1,48 +0,0 @@
-# Linear Tickets
-
-## What this source contains
-
-- Issues describing features, bugs, and their motivation
-- Project docs attached to issues (often PRDs or specs)
-- Parent/sub-issue relationships (broader initiative → specific tickets)
-- Comments on issues (clarifications, scope changes, "why we're doing this" rationale)
-- Labels (e.g., `compliance`, `customer-request`, `perf`) that signal the type of motivation
-- Status updates that explain scope changes
-- Attachments and linked GitHub PRs
-
-Linear is where the product/business context often lives: the "we're doing this because customer X asked" or "this is for the Q3 compliance initiative" layer.
-
-## How to search it
-
-Use the Linear MCP.
-
-1. **Start with linked tickets.** If the seed commits or PRs reference ticket IDs (e.g., `ENG-1234`, `[BUG-567]`), fetch those first with `get_issue`. Read the full issue including comments.
-2. **List related issues by keyword.** Use `list_issues` with text search for the feature name, key symbol, or business term. Try multiple phrasings.
-3. **Walk the issue tree.** If you land on a sub-issue, fetch its parent. Sub-issues are tactical. Parents often carry the "why."
-4. **Read project docs.** If the issue belongs to a project, use `get_project` and check attached docs. Project-level documents are where specs and rationale are most often captured.
-5. **Check labels and milestones.** Labels hint at the category of motivation (customer-request, incident-followup, compliance). Milestones tie work to deadlines, which often reveal motivation.
-
-## What good evidence looks like here
-
-- An issue description stating the business problem: "Customer Acme needs X because of their SOC2 audit"
-- A comment recording a decision: "We decided to go with approach B because approach A would require touching the billing service"
-- A parent issue titled like an initiative: "Q3 Enterprise Readiness" or "Reduce Payment Failures"
-- An attached PRD or spec
-- Labels like `customer:acme`, `incident-followup`, `compliance`, `perf-regression`
-
-## Common pitfalls
-
-- **Scope drift.** The ticket the PR references may have been closed and reopened with a different scope. Read the whole history.
-- **Mechanical templates.** Some teams require "Why" sections but fill them with boilerplate. Generic text ("improve user experience") is probably not a real answer.
-- **Stale tickets.** Old tickets often reflect a version of the plan that changed. Check dates and cross-reference with the code's ship date.
-- **Closed-as-duplicate chains.** Follow the duplicate-of relationships back to the canonical ticket.
-- **Private workspace content.** If you can't access an issue, note that as a gap rather than guessing.
-
-## What to return
-
-For each relevant ticket:
-- Ticket ID and title
-- The problem/motivation quoted from the description or comments (not paraphrased. The synthesizer needs the exact text to cite)
-- Labels, parent issue, project
-- Author, created date, closed date
-- Link to the ticket if available

package/dist/assets/skills/why/references/sources/notion.md

@@ -1,55 +0,0 @@
-# Notion Docs
-
-## What this source contains
-
-- PRDs (product requirement documents)
-- Technical specs and RFCs
-- Architectural decision records (ADRs)
-- Meeting notes from design reviews
-- Team pages with domain context
-- Postmortems from incidents
-- Runbooks that may explain defensive code
-- Strategy documents that set priorities
-
-Notion is where "why" often lives in long-form before it becomes code. A significant feature usually has a doc.
-
-## How to search it
-
-Use the Notion MCP.
-
-1. **Keyword searches with `notion-search`.** Try:
-   - The feature name
-   - Key symbols / class names from the target code
-   - Author handles (design docs are often authored before the code lands)
-   - Error strings or user-visible terms
-   - Time-bounded queries if you know when the code shipped
-2. **Fetch candidate pages with `notion-fetch`.** Read the full content, not the preview. Rationale is often buried mid-document.
-3. **Follow backlinks and child pages.** Design docs often have sub-pages for alternatives considered, appendices, or implementation notes.
-4. **Check related databases.** `notion-query-data-sources` and `notion-query-meeting-notes` can surface meeting notes that discussed the decision.
-5. **Search author-specific spaces.** If the PR author has a personal notebook (common at some companies), it may hold exploratory thinking that preceded the code.
-
-## What good evidence looks like here
-
-- A PRD with a "Problem statement" or "Motivation" section that matches the target code's purpose
-- An "Alternatives considered" or "Rejected approaches" section
-- A postmortem that names the target code as the fix for a specific incident
-- Meeting notes that record "we decided X because Y" and tie to the same author/date range as the PR
-- An ADR template filled out non-trivially (status, context, decision, consequences)
-
-## Common pitfalls
-
-- **Outdated docs.** Specs are often written before implementation and not updated. The doc may describe a plan that changed. Cross-check against the actual PR.
-- **Doc vs. reality drift.** A spec may say "we'll do X" but the code actually does Y. Flag the divergence. The synthesizer will surface the contradiction.
-- **Boilerplate templates.** Some orgs require a "Why" section that gets filled with fluff. Look for specificity.
-- **Unlinked docs.** The most relevant doc may not be linked from anywhere. Broad keyword searches help.
-- **Multiple drafts.** If a topic has multiple docs, find the one that was finalized or most recently updated. Check dates.
-- **Access-restricted pages.** If you can't access a page, note it as a gap.
-
-## What to return
-
-For each relevant doc:
-- Title and URL
-- Authors and last-updated date
-- The motivation text (verbatim quote), with page/section location
-- Relevant linked pages (so the synthesizer can cite them)
-- Whether the doc was finalized or draft

package/dist/assets/skills/why/references/sources/sentry.md

@@ -1,66 +0,0 @@
-# Sentry Error History
-
-## How to search it
-
-Use the Sentry MCP.
-
-1. **Orient.** If you don't know the project slug and organization:
-
-   ```
-   find_organizations
-   find_projects
-   ```
-
-2. **Search for issues related to the target.**
-
-   ```
-   search_issues (natural language, e.g., "errors in PaymentService timeout", "unhandled exceptions in uploadFile")
-   ```
-
-   Build queries from the exception class names the target handles, its function or class name, the error message strings it checks for, and its file path.
-
-3. **Narrow by release and time window.**
-
-   ```
-   search_issue_events (filter by release, time, environment, trace ID, tags)
-   get_issue_tag_values (for an issue, see distribution across versions, users, environments)
-   ```
-
-   For a suspected issue, check **first seen** and **last seen** (does the stop line up with the target's ship date?), the **affected releases** (which saw it, and which was the fix?), and the **frequency trajectory** (did it spike, then get resolved?).
-
-4. **Pull the full event for context.**
-
-   ```
-   get_sentry_resource (pass a Sentry URL or type+ID)
-   ```
-
-   Does the stack trace pass through the target code? Do the tags and breadcrumbs match the conditions the target defends against?
-
-5. **Check releases that landed near the target.**
-
-   ```
-   find_releases (around the commit date of the target)
-   ```
-
-   Cross-reference release version with the PR's merge date.
-
-6. **Use Seer sparingly.**
-
-   ```
-   analyze_issue_with_seer
-   ```
-
-   Seer's AI root-cause analyses are a hypothesis generator. Treat them as inference, not authoritative. The actual events and stack traces are the primary evidence.
-
-## What to return
-
-For each relevant issue:
-- Issue ID and title
-- Project and organization
-- First seen / last seen timestamps
-- Event count (and sampling rate if known)
-- Affected releases
-- A representative stack trace snippet showing relevance to the target (verbatim excerpt, not summary)
-- First/last-seen correlation with the target's ship date
-- Link to the issue
-- Any author comments or resolution notes

package/dist/assets/skills/why/references/sources/slack.md

@@ -1,17 +0,0 @@
-# Slack Conversations
-
-## How to search it
-
-Slack MCP tools vary. Check which Slack MCP is available and inspect its tool schema first. It may require `mcp_auth`. If authentication fails, stop and report the gap.
-
-1. **Author-bounded search.** Messages from the PR author around the PR merge date. Limits scope dramatically and often hits gold.
-3. **PR URL search.** Slack often links PRs when they're reviewed or discussed. Search for the PR URL (or just `/pull/<number>`).
-4. **Error string search.** If the code handles a specific error, search for the error string. Incident threads often surface.
-
-## Common pitfalls
-
-- **Channel archaeology limits.** Very old messages may be gone due to retention policies. If you can't find anything before a certain date, note the retention cliff.
-- **Unsearched DMs.** Many decisions happen in DMs that aren't searchable. You'll miss them. That's a known limitation.
-- **Speculative jokes as "decisions."** Slack is casual. "Lol just do the thing" isn't a decision, even if it preceded the commit. Look for considered discussion.
-- **Context collapse in single messages.** Without the thread, a single message often reads differently than in context. Always fetch threads.
-- **Auth failures.** If the MCP isn't authenticated, stop. Don't make up findings. Report that Slack wasn't searchable.

package/dist/assets/skills/why/references/synthesizer-prompt.md

@@ -1,129 +0,0 @@
-# Synthesizer Prompt Template
-
-Fill in the placeholders.
-
----
-
-You are answering a "why" question about a piece of code by synthesizing findings from investigators who searched different historical sources (source control, issue / ticket tracker, long-form documents, real-time team chat, infrastructure observability, error / exception tracking, product analytics warehouse, and code comments). Produce a confidence-weighted, evidence-cited narrative that says honestly what the evidence supports, and just as honestly what it doesn't.
-
-## The Question
-
-> {QUESTION}
-
-## The Code Anchor
-
-**Target files:** {FILES_WITH_LINE_RANGES}
-
-**Key symbols:** {SYMBOLS}
-
-## Investigator Findings
-
-{ALL_INVESTIGATOR_FINDINGS}
-
-## Sources That Weren't Searched
-
-{SKIPPED_SOURCES_WITH_REASONS}
-
-## Epistemics Framework
-
-You MUST follow `references/epistemics.md`. Read it in full before writing. The key rules:
-
-1. Every claim must sit in one tier: **Direct**, **Supported**, **Inferred**, **Speculative**, **Unknown**. The tier sets its section and its phrasing.
-2. Every Direct/Supported claim must have a citation (PR #, ticket ID, doc URL, chat permalink, commit hash, or file:line).
-3. Inferred and Speculative claims must use hedged language ("appears to", "likely", "suggests", "one possibility is").
-4. Never cite code as evidence for its own intent.
-5. Document gaps. Don't fill them with plausible-sounding guesses.
-6. Treat a hypothesis embedded in the user's question as a candidate, not a conclusion. Check it independently.
-
-## Instructions
-
-1. **Read all investigator findings** and weigh the evidence yourself. Investigators gathered raw evidence, not conclusions.
-2. **Merge overlaps.** When several investigators cite the same PR, ticket, or doc, give it one authoritative reference.
-3. **Surface contradictions.** When two items disagree, show both. Don't pick one.
-4. **Calibrate each claim.** Find its evidence and tier. Direct: cite it and state it plainly. Inferred: hedge it and show the inference. Speculative: mark it. No evidence: put it in the gaps.
-5. **Verify citations by spot-checking.** If you're uncertain a cited item exists or says what the investigator claims, check it by reading the codebase or calling MCP tools. Don't propagate errors. Do not write files, commit, or modify external state.
-6. **Don't overreach.** The user will act on this. Leave an open question open rather than fill it with a confident guess.
-
-## Output Format
-
-Write for the user, in this exact structure:
-
----
-
-### The Question
-
-Restate the user's question in one or two sentences.
-
-### The Code in Question
-
-File paths, line ranges, key symbols. Two or three lines to orient a cold reader.
-
-### What We Found
-
-Claims with textual evidence, each quoted or paraphrased and cited precisely:
-
-- **[Direct]** {Claim}. Source: [PR #123](url) / ticket ID / file:line. {Brief quote or paraphrase.}
-- **[Supported]** {Claim}. Evidence: {list of items and what each contributes}.
-
-`[Direct]` is single-source, explicit evidence. `[Supported]` is multiple indirect items converging on a conclusion.
-
-### What We Can Reasonably Infer
-
-Claims stated nowhere but well-supported by indirect evidence. Each bullet must make the inference chain visible ("Given A and B, it's likely that C") and must use hedged language ("appears to", "likely", "suggests", "is consistent with"):
-
-- **[Inferred]** {Hedged claim}. Reasoning: {the specific evidence and the inference step}.
-
-Skip this section if there's nothing to infer.
-
-### Competing Hypotheses
-
-If the evidence fits multiple stories, present each. Don't force a winner the record doesn't support. For each hypothesis:
-
-- **Hypothesis:** {one-sentence statement}
-- **Evidence for:** {specific items}
-- **Evidence against or missing:** {what would need to be true but isn't, or what counter-signals exist}
-
-Skip this section if there's a single clear answer.
-
-### What We Don't Know
-
-Specific gaps: "We searched the issue tracker for [query1], [query2], [query3] and found no issue discussing the rate-limit threshold", not "We don't know why." Include:
-
-- Questions that went unanswered
-- Searches that returned nothing
-- Sources that were unavailable, and why (such as a missing real-time team chat MCP)
-- People who would likely know but whom you can't ask
-
-### Sources Consulted
-
-What was actually searched, so the user can judge coverage and redirect:
-
-- **Source control history**: {file paths}, {number of commits reviewed}, PRs #{numbers}, and code comments searched. Or "Not searched. This should not happen because git and `gh` are always expected."
-- **Issue / ticket tracker**: {ticket IDs and keyword searches}. Or "Not searched. No matching MCP available in this environment."
-- **Long-form documents**: {page titles and search queries}. Or "Not searched. No matching MCP available in this environment."
-- **Real-time team chat**: {channels searched, date ranges, queries}. Or "Not searched. No matching MCP available in this environment."
-- **Infrastructure observability**: {dashboards, monitors, metrics, logs, traces, or incidents searched}. Or "Not searched. No matching MCP available in this environment."
-- **Error / exception tracking**: {issues, events, or releases searched}. Or "Not searched. No matching MCP available in this environment."
-- **Product analytics warehouse**: {fully-qualified tables queried, the time windows, and the numeric summaries (counts, percentiles, first/last-seen timestamps) that bore on the question}. Or "Not searched. No matching MCP available in this environment."
-
-### Confidence Summary
-
-One or two sentences on overall confidence, e.g.:
-
-> "The core rationale (A) is well-supported by direct PR and ticket evidence. The specific threshold value (100) is inferred from the surrounding context but not explicitly documented. The question of whether this was driven by a customer request could not be answered. No relevant issue tracker or long-form doc content surfaced, and real-time team chat search was unavailable."
-
----
-
-## Quality Check Before Returning
-
-Revise if any item fails:
-
-1. Does every claim in "What We Found" have a citation? If not, add one or move it to "Inferred" or "Hypotheses."
-2. Is the phrasing tier-appropriate? (Direct claims can use "because". Inferred claims cannot.)
-3. Did you surface every contradiction you noticed, or quietly pick one?
-4. Does "What We Don't Know" name specific gaps? If it's empty or missing, be suspicious. Historical investigations almost always have gaps.
-5. Did you check any hypothesis embedded in the question against the evidence rather than rubber-stamp it?
-6. Did you cite code as evidence for its own intent? Remove it. Code is mechanics, not motivation.
-7. Is the tone calibrated? A confident-sounding answer on weak evidence is the exact failure this skill exists to prevent.
-
-The value of this output is its honesty, not its authority. A reader who takes it to the original author, an engineering lead, or a product manager should know what's known, what's inferred, and what's missing, so they can ask the right follow-up questions. Optimize for being useful, not for looking decisive.

package/dist/cordis.patch.yml

@@ -1,20 +0,0 @@
-# dsh-pstack bundle patch.
-#
-# Two rows, both installed by this package:
-#   - `pstack` mounts the bundled skill provider. Every pstack skill becomes a
-#     normal DSH skill: model-invocable skills reach the catalog, user-invocable
-#     skills reach the `/` menu.
-#   - `pstack-subagent` mounts the `pstack_subagent` tool, the DSH replacement
-#     for Cursor's `Task` tool. It resolves pstack role lines from
-#     `~/.dsh/pstack-models.md` and delegates through `ctx.subagents`.
-#
-# The `pstack` row requires `ctx.skills`, which `@deepseek-ai/dsh-base` provides.
-# The `pstack-subagent` row requires `ctx.tools` and `ctx.subagents`, also in
-# base-backed profiles. Installing this bundle into a profile that lacks them
-# leaves the rows pending, exactly like any other dependency-driven plugin.
-- insert:
-    - id: pstack
-      name: "dsh-pstack"
-
-    - id: pstack-subagent
-      name: "dsh-pstack/subagent"

package/dist/index.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.mjs","names":[],"sources":["../src/frontmatter.ts","../src/provider.ts"],"sourcesContent":["/**\n * The pstack SKILL.md frontmatter subset: plain scalars, quoted scalars, and\n * folded or literal block scalars. Kept dependency-free so the plugin can be\n * imported at boot before any optional parser is available.\n */\n\nexport interface Frontmatter {\n  data: Record<string, string>;\n  body: string;\n}\n\nconst DELIMITER = \"---\";\n\nfunction unquote(value: string): string {\n  const trimmed = value.trim();\n  if (trimmed.length >= 2) {\n    const first = trimmed[0];\n    const last = trimmed[trimmed.length - 1];\n    if ((first === '\"' && last === '\"') || (first === \"'\" && last === \"'\")) {\n      const inner = trimmed.slice(1, -1);\n      return first === '\"'\n        ? inner.replace(/\\\\\"/g, '\"').replace(/\\\\n/g, \"\\n\").replace(/\\\\\\\\/g, \"\\\\\")\n        : inner.replace(/''/g, \"'\");\n    }\n  }\n  return trimmed;\n}\n\nexport function parseFrontmatter(source: string): Frontmatter {\n  const normalized = source.replace(/\\r\\n/g, \"\\n\");\n  const lines = normalized.split(\"\\n\");\n  if (lines[0]?.trim() !== DELIMITER) return { data: {}, body: normalized };\n\n  let end = -1;\n  for (let index = 1; index < lines.length; index += 1) {\n    if (lines[index]?.trim() === DELIMITER) {\n      end = index;\n      break;\n    }\n  }\n  if (end === -1) return { data: {}, body: normalized };\n\n  const data: Record<string, string> = {};\n  let index = 1;\n  while (index < end) {\n    const line = lines[index] ?? \"\";\n    const match = /^([A-Za-z0-9_-]+):\\s*(.*)$/.exec(line);\n    if (!match) {\n      index += 1;\n      continue;\n    }\n    const key = match[1]!;\n    const rawValue = match[2] ?? \"\";\n    index += 1;\n\n    if (rawValue === \">\" || rawValue === \">-\" || rawValue === \"|\" || rawValue === \"|-\") {\n      const folded = rawValue.startsWith(\">\");\n      const collected: string[] = [];\n      while (index < end) {\n        const next = lines[index] ?? \"\";\n        if (next.trim() !== \"\" && !/^\\s/.test(next)) break;\n        collected.push(next.replace(/^\\s{1,4}/, \"\"));\n        index += 1;\n      }\n      data[key] = folded\n        ? collected.join(\" \").replace(/\\s+/g, \" \").trim()\n        : collected.join(\"\\n\").replace(/\\n+$/, \"\");\n      continue;\n    }\n\n    if (rawValue === \"\") {\n      const collected: string[] = [];\n      while (index < end) {\n        const next = lines[index] ?? \"\";\n        if (next.trim() !== \"\" && !/^\\s/.test(next)) break;\n        collected.push(next.trim());\n        index += 1;\n      }\n      data[key] = collected.join(\" \").trim();\n      continue;\n    }\n\n    data[key] = unquote(rawValue);\n  }\n\n  return {\n    data,\n    body: lines\n      .slice(end + 1)\n      .join(\"\\n\")\n      .replace(/^\\n+/, \"\"),\n  };\n}\n","/**\n * Bundled pstack skill provider.\n *\n * One provider hosts every pstack skill so the catalog stays one entry per\n * skill and the package ships as a single installable bundle. The provider is\n * immutable: `assets/skills/` is generated at build time, so discovery always\n * completes with the same list.\n */\nimport { readdirSync, readFileSync } from \"node:fs\";\nimport type { Context } from \"@deepseek-ai/cordis\";\nimport {\n  BUNDLED_SKILL_RANK,\n  type SkillCandidate,\n  type SkillDefinition,\n  type SkillProvider,\n} from \"@deepseek-ai/dsh-skill\";\nimport { parseFrontmatter } from \"./frontmatter.ts\";\nimport { SKILLS_ROOT, SKILLS_ROOT_URL } from \"./paths.ts\";\n\nexport interface PstackSkillEntry {\n  readonly name: string;\n  readonly description: string;\n  readonly modelInvocable: boolean;\n  readonly userInvocable: boolean;\n  readonly directory: string;\n}\n\nexport const PROVIDER_NAME = \"pstack\";\n\nfunction text(value: string | undefined): string {\n  return (value ?? \"\").trim();\n}\n\n/**\n * Parse one generated SKILL.md into the catalog entry the provider serves.\n * Generated files always carry `name` and `description`; a hand-edit that\n * removes them fails loudly instead of silently dropping the skill.\n */\nexport function toEntry(directory: string, source: string): PstackSkillEntry {\n  const { data } = parseFrontmatter(source);\n  if (!text(data.name) || !text(data.description)) {\n    throw new Error(`pstack skill \"${directory}\" is missing name or description frontmatter`);\n  }\n  return {\n    name: text(data.name),\n    description: text(data.description),\n    modelInvocable: data[\"disable-model-invocation\"] !== \"true\",\n    userInvocable: data[\"user-invocable\"] !== \"false\",\n    directory,\n  };\n}\n\nfunction resourceBase(directory: string) {\n  return { kind: \"directory\" as const, path: `${SKILLS_ROOT}${directory}/` };\n}\n\nexport function toCandidate(entry: PstackSkillEntry): SkillCandidate {\n  return {\n    name: entry.name,\n    description: entry.description,\n    invocation: { modelInvocable: entry.modelInvocable, userInvocable: entry.userInvocable },\n    provider: PROVIDER_NAME,\n    source: \"bundled\",\n    rank: BUNDLED_SKILL_RANK,\n    resourceBase: resourceBase(entry.directory),\n    locator: entry.directory,\n    path: `${SKILLS_ROOT}${entry.directory}/SKILL.md`,\n  };\n}\n\nexport interface PstackProviderOptions {\n  /** Directory names to serve. The build passes the generated list. */\n  readonly directories: readonly string[];\n  /** Reads one skill body. Tests override it to avoid touching the package. */\n  readonly read?: (directory: string) => string;\n}\n\nexport function createProvider(options: PstackProviderOptions): SkillProvider {\n  const read =\n    options.read ??\n    ((directory: string) => readFileSync(`${SKILLS_ROOT}${directory}/SKILL.md`, \"utf8\"));\n  const entries = options.directories.map((directory) => toEntry(directory, read(directory)));\n  const byName = new Map(entries.map((entry) => [entry.name, entry]));\n\n  const load = (entry: PstackSkillEntry): SkillDefinition => {\n    const { body } = parseFrontmatter(read(entry.directory));\n    return {\n      name: entry.name,\n      description: entry.description,\n      invocation: { modelInvocable: entry.modelInvocable, userInvocable: entry.userInvocable },\n      provider: PROVIDER_NAME,\n      source: \"bundled\",\n      resourceBase: resourceBase(entry.directory),\n      path: `${SKILLS_ROOT}${entry.directory}/SKILL.md`,\n      content: body,\n    };\n  };\n\n  return {\n    name: PROVIDER_NAME,\n    list: async () => entries.map(toCandidate),\n    get: async (candidate) => {\n      const entry = byName.get(candidate.name);\n      return entry ? load(entry) : undefined;\n    },\n  };\n}\n\nexport const name = \"pstack\";\n\nexport interface Config {\n  /** Extra skill directories to serve in addition to the bundled set. */\n  readonly extraSkillDirectories?: string[];\n}\n\nexport const inject = [\"skills\"];\n\nexport function listBundledSkillDirectories(): string[] {\n  return readdirSync(SKILLS_ROOT, { withFileTypes: true })\n    .filter((entry) => entry.isDirectory())\n    .map((entry) => entry.name)\n    .sort();\n}\n\nexport function apply(ctx: Context, config: Config = {}): void {\n  const directories = [\n    ...new Set([...listBundledSkillDirectories(), ...(config.extraSkillDirectories ?? [])]),\n  ];\n  ctx.skills.registerProvider(() => createProvider({ directories }));\n}\n\n/** Absolute root of the generated skill tree, exported for doctor checks. */\nexport const skillsRoot = SKILLS_ROOT;\nexport const skillsRootUrl = SKILLS_ROOT_URL;\n"],"mappings":";;;;AAWA,MAAM,YAAY;AAElB,SAAS,QAAQ,OAAuB;CACtC,MAAM,UAAU,MAAM,KAAK;CAC3B,IAAI,QAAQ,UAAU,GAAG;EACvB,MAAM,QAAQ,QAAQ;EACtB,MAAM,OAAO,QAAQ,QAAQ,SAAS;EACtC,IAAK,UAAU,QAAO,SAAS,QAAS,UAAU,OAAO,SAAS,KAAM;GACtE,MAAM,QAAQ,QAAQ,MAAM,GAAG,EAAE;GACjC,OAAO,UAAU,OACb,MAAM,QAAQ,QAAQ,IAAG,CAAC,CAAC,QAAQ,QAAQ,IAAI,CAAC,CAAC,QAAQ,SAAS,IAAI,IACtE,MAAM,QAAQ,OAAO,GAAG;EAC9B;CACF;CACA,OAAO;AACT;AAEA,SAAgB,iBAAiB,QAA6B;CAC5D,MAAM,aAAa,OAAO,QAAQ,SAAS,IAAI;CAC/C,MAAM,QAAQ,WAAW,MAAM,IAAI;CACnC,IAAI,MAAM,EAAE,EAAE,KAAK,MAAM,WAAW,OAAO;EAAE,MAAM,CAAC;EAAG,MAAM;CAAW;CAExE,IAAI,MAAM;CACV,KAAK,IAAI,QAAQ,GAAG,QAAQ,MAAM,QAAQ,SAAS,GACjD,IAAI,MAAM,MAAM,EAAE,KAAK,MAAM,WAAW;EACtC,MAAM;EACN;CACF;CAEF,IAAI,QAAQ,IAAI,OAAO;EAAE,MAAM,CAAC;EAAG,MAAM;CAAW;CAEpD,MAAM,OAA+B,CAAC;CACtC,IAAI,QAAQ;CACZ,OAAO,QAAQ,KAAK;EAClB,MAAM,OAAO,MAAM,UAAU;EAC7B,MAAM,QAAQ,6BAA6B,KAAK,IAAI;EACpD,IAAI,CAAC,OAAO;GACV,SAAS;GACT;EACF;EACA,MAAM,MAAM,MAAM;EAClB,MAAM,WAAW,MAAM,MAAM;EAC7B,SAAS;EAET,IAAI,aAAa,OAAO,aAAa,QAAQ,aAAa,OAAO,aAAa,MAAM;GAClF,MAAM,SAAS,SAAS,WAAW,GAAG;GACtC,MAAM,YAAsB,CAAC;GAC7B,OAAO,QAAQ,KAAK;IAClB,MAAM,OAAO,MAAM,UAAU;IAC7B,IAAI,KAAK,KAAK,MAAM,MAAM,CAAC,MAAM,KAAK,IAAI,GAAG;IAC7C,UAAU,KAAK,KAAK,QAAQ,YAAY,EAAE,CAAC;IAC3C,SAAS;GACX;GACA,KAAK,OAAO,SACR,UAAU,KAAK,GAAG,CAAC,CAAC,QAAQ,QAAQ,GAAG,CAAC,CAAC,KAAK,IAC9C,UAAU,KAAK,IAAI,CAAC,CAAC,QAAQ,QAAQ,EAAE;GAC3C;EACF;EAEA,IAAI,aAAa,IAAI;GACnB,MAAM,YAAsB,CAAC;GAC7B,OAAO,QAAQ,KAAK;IAClB,MAAM,OAAO,MAAM,UAAU;IAC7B,IAAI,KAAK,KAAK,MAAM,MAAM,CAAC,MAAM,KAAK,IAAI,GAAG;IAC7C,UAAU,KAAK,KAAK,KAAK,CAAC;IAC1B,SAAS;GACX;GACA,KAAK,OAAO,UAAU,KAAK,GAAG,CAAC,CAAC,KAAK;GACrC;EACF;EAEA,KAAK,OAAO,QAAQ,QAAQ;CAC9B;CAEA,OAAO;EACL;EACA,MAAM,MACH,MAAM,MAAM,CAAC,CAAC,CACd,KAAK,IAAI,CAAC,CACV,QAAQ,QAAQ,EAAE;CACvB;AACF;;;;;;;;;;;ACjEA,MAAa,gBAAgB;AAE7B,SAAS,KAAK,OAAmC;CAC/C,QAAQ,SAAS,GAAA,CAAI,KAAK;AAC5B;;;;;;AAOA,SAAgB,QAAQ,WAAmB,QAAkC;CAC3E,MAAM,EAAE,SAAS,iBAAiB,MAAM;CACxC,IAAI,CAAC,KAAK,KAAK,IAAI,KAAK,CAAC,KAAK,KAAK,WAAW,GAC5C,MAAM,IAAI,MAAM,iBAAiB,UAAU,6CAA6C;CAE1F,OAAO;EACL,MAAM,KAAK,KAAK,IAAI;EACpB,aAAa,KAAK,KAAK,WAAW;EAClC,gBAAgB,KAAK,gCAAgC;EACrD,eAAe,KAAK,sBAAsB;EAC1C;CACF;AACF;AAEA,SAAS,aAAa,WAAmB;CACvC,OAAO;EAAE,MAAM;EAAsB,MAAM,GAAG,cAAc,UAAU;CAAG;AAC3E;AAEA,SAAgB,YAAY,OAAyC;CACnE,OAAO;EACL,MAAM,MAAM;EACZ,aAAa,MAAM;EACnB,YAAY;GAAE,gBAAgB,MAAM;GAAgB,eAAe,MAAM;EAAc;EACvF,UAAU;EACV,QAAQ;EACR,MAAM;EACN,cAAc,aAAa,MAAM,SAAS;EAC1C,SAAS,MAAM;EACf,MAAM,GAAG,cAAc,MAAM,UAAU;CACzC;AACF;AASA,SAAgB,eAAe,SAA+C;CAC5E,MAAM,OACJ,QAAQ,UACN,cAAsB,aAAa,GAAG,cAAc,UAAU,YAAY,MAAM;CACpF,MAAM,UAAU,QAAQ,YAAY,KAAK,cAAc,QAAQ,WAAW,KAAK,SAAS,CAAC,CAAC;CAC1F,MAAM,SAAS,IAAI,IAAI,QAAQ,KAAK,UAAU,CAAC,MAAM,MAAM,KAAK,CAAC,CAAC;CAElE,MAAM,QAAQ,UAA6C;EACzD,MAAM,EAAE,SAAS,iBAAiB,KAAK,MAAM,SAAS,CAAC;EACvD,OAAO;GACL,MAAM,MAAM;GACZ,aAAa,MAAM;GACnB,YAAY;IAAE,gBAAgB,MAAM;IAAgB,eAAe,MAAM;GAAc;GACvF,UAAU;GACV,QAAQ;GACR,cAAc,aAAa,MAAM,SAAS;GAC1C,MAAM,GAAG,cAAc,MAAM,UAAU;GACvC,SAAS;EACX;CACF;CAEA,OAAO;EACL,MAAM;EACN,MAAM,YAAY,QAAQ,IAAI,WAAW;EACzC,KAAK,OAAO,cAAc;GACxB,MAAM,QAAQ,OAAO,IAAI,UAAU,IAAI;GACvC,OAAO,QAAQ,KAAK,KAAK,IAAI,KAAA;EAC/B;CACF;AACF;AAEA,MAAa,OAAO;AAOpB,MAAa,SAAS,CAAC,QAAQ;AAE/B,SAAgB,8BAAwC;CACtD,OAAO,YAAY,aAAa,EAAE,eAAe,KAAK,CAAC,CAAC,CACrD,QAAQ,UAAU,MAAM,YAAY,CAAC,CAAC,CACtC,KAAK,UAAU,MAAM,IAAI,CAAC,CAC1B,KAAK;AACV;AAEA,SAAgB,MAAM,KAAc,SAAiB,CAAC,GAAS;CAC7D,MAAM,cAAc,CAClB,mBAAG,IAAI,IAAI,CAAC,GAAG,4BAA4B,GAAG,GAAI,OAAO,yBAAyB,CAAC,CAAE,CAAC,CACxF;CACA,IAAI,OAAO,uBAAuB,eAAe,EAAE,YAAY,CAAC,CAAC;AACnE;;AAGA,MAAa,aAAa;AAC1B,MAAa,gBAAgB"}

package/dist/paths-Bbai4CaT.mjs

@@ -1,16 +0,0 @@
-import { fileURLToPath } from "node:url";
-//#region src/paths.ts
-/**
-* Locate one pstack skill directory inside this package.
-*
-* The provider registers candidates from an explicit file list, so this helper
-* resolves the directory the built entry point and the tests share.
-*/
-const SKILLS_ROOT_URL = new URL("../assets/skills/", import.meta.url);
-const AGENTS_ROOT_URL = new URL("../assets/agents/", import.meta.url);
-const SKILLS_ROOT = fileURLToPath(SKILLS_ROOT_URL);
-const AGENTS_ROOT = fileURLToPath(AGENTS_ROOT_URL);
-//#endregion
-export { SKILLS_ROOT as n, SKILLS_ROOT_URL as r, AGENTS_ROOT as t };
-
-//# sourceMappingURL=paths-Bbai4CaT.mjs.map

package/dist/paths-Bbai4CaT.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"paths-Bbai4CaT.mjs","names":[],"sources":["../src/paths.ts"],"sourcesContent":["/**\n * Locate one pstack skill directory inside this package.\n *\n * The provider registers candidates from an explicit file list, so this helper\n * resolves the directory the built entry point and the tests share.\n */\nimport { fileURLToPath } from \"node:url\";\n\nexport const SKILLS_ROOT_URL = new URL(\"../assets/skills/\", import.meta.url);\nexport const AGENTS_ROOT_URL = new URL(\"../assets/agents/\", import.meta.url);\nexport const SKILLS_ROOT = fileURLToPath(SKILLS_ROOT_URL);\nexport const AGENTS_ROOT = fileURLToPath(AGENTS_ROOT_URL);\n"],"mappings":";;;;;;;;AAQA,MAAa,kBAAkB,IAAI,IAAI,qBAAqB,YAAY,GAAG;AAC3E,MAAa,kBAAkB,IAAI,IAAI,qBAAqB,YAAY,GAAG;AAC3E,MAAa,cAAc,cAAc,eAAe;AACxD,MAAa,cAAc,cAAc,eAAe"}