@hegemonart/get-design-done 1.57.2 → 1.57.3

package/dist/claude-code/.claude/skills/quick/SKILL.md

@@ -1,44 +0,0 @@
----
-name: gdd-quick
-description: "Run the pipeline with optional agents skipped for speed. Skips: phase-researcher, design-assumptions-analyzer, design-integration-checker. Keeps: planner, executor, verifier, auditor. Activates for requests involving a lightweight design pass, a fast iteration, or a quick low-ceremony change."
-argument-hint: "[--skip <agent-name>] [stage]"
-tools: Read, Task
-disable-model-invocation: true
----
-
-# /gdd:quick
-
-Fast pipeline run. Skips optional-quality agents for speed while keeping the core decision chain (planner → executor → verifier → auditor) intact.
-
-## Default skipped agents
-
-- `design-phase-researcher` - no external research step
-- `design-assumptions-analyzer` - no assumption surfacing
-- `design-integration-checker` - skipped (verifier still runs)
-
-## Default kept agents
-
-- `design-planner`, `design-executor`, `design-verifier`, `design-auditor`
-
-## Steps
-
-1. Parse args:
-   - Optional stage name (defaults to full pipeline from the current STATE.md position).
-   - `--skip <agent-name>` (repeatable) adds to the skip list.
-2. Read `.design/STATE.md` to determine entry stage if none was passed.
-3. For each stage to execute, spawn the stage skill with a `quick_mode: true` flag and the effective skip list in the spawn context. Stage skills read this flag and route around the listed agents.
-4. After each stage, print: "Stage <name> done. Skipped: <list>."
-5. Final summary prints which agents were skipped across the full run.
-
-## Use When
-
-- You trust the problem scope (no need for fresh research).
-- The project has a mature DESIGN-CONTEXT.md (assumptions already surfaced).
-- You want verify + audit coverage without integration-checker overhead.
-
-## Do Not Use When
-
-- First pipeline run in a new project - use the full pipeline.
-- Large or cross-cutting changes - skip risks are higher.
-
-## QUICK COMPLETE

package/dist/claude-code/.claude/skills/reapply-patches/SKILL.md

@@ -1,32 +0,0 @@
----
-name: gdd-reapply-patches
-description: "Reapply user modifications to reference/ files after a plugin update. Detects customizations via git diff against pristine baseline."
-argument-hint: "[--dry-run]"
-tools: Read, Write, Bash
-disable-model-invocation: true
----
-
-# gdd-reapply-patches
-
-Re-applies user customizations to `reference/*.md` files after `/gdd:update` resyncs the plugin. Customizations are detected by diffing each `reference/` file against a pristine baseline stored in `.gdd-baseline/`.
-
-## Steps
-
-1. **Detect baseline** - check for `.gdd-baseline/reference/`. If it does not exist, warn the user and offer to initialize it from the current `reference/` state (no diffs will be generated on this run; the next `/gdd:update` will use the new baseline).
-2. **Generate diffs** - for each `reference/*.md`, run `git diff --no-index .gdd-baseline/reference/<file> reference/<file>` (or plain `diff -u`). Non-empty diffs are candidate user patches.
-3. **Review patches** - for each non-empty diff, print the hunk and ask: `Apply this customization to the updated reference/<file>? (yes/no/view)`. `view` shows the full diff; `yes` queues the patch; `no` skips it.
-4. **Apply** - for each confirmed patch, apply it with `patch -p0` or with a targeted `Edit` call. Log every applied patch.
-5. **Refresh baseline** - after applying, copy the current `reference/*.md` tree into `.gdd-baseline/reference/` to record the new pristine-for-this-user state.
-6. **Dry-run** - if `--dry-run` is passed, perform steps 1–3 but do not apply patches or refresh the baseline.
-
-## Design note
-
-`.gdd-baseline/` is per-install and user-local. It must be gitignored by the host project - it is never committed to the plugin repo.
-
-## Output
-
-End every invocation with:
-
-```
-## REAPPLY-PATCHES COMPLETE
-```

package/dist/claude-code/.claude/skills/recall/SKILL.md

@@ -1,75 +0,0 @@
----
-name: gdd-recall
-description: "Search cross-cycle memory: decisions, learnings, experience archives. Returns ranked matches."
-argument-hint: "<query> [--reindex]"
-tools: Read, Write, Bash
-disable-model-invocation: true
----
-
-@reference/retrieval-contract.md
-
-# /gdd:recall
-
-Searches `.design/archive/`, `.design/learnings/LEARNINGS.md`, `.design/CYCLES.md`, and `STATE.md` decision blocks for the given query and returns ranked matches. Uses FTS5 when `better-sqlite3` is available, ripgrep next, Node fs scan as universal fallback.
-
-## Steps
-
-1. **Parse argument**: extract `<query>` and optional `--reindex` flag.
-   - If no query and no `--reindex`: print usage and exit.
-   - If `--reindex` only: rebuild the index (see step 3), then exit.
-
-2. **Check backend**: run
-   ```bash
-   node -e "const {backendName}=require('./scripts/lib/design-search.cjs');console.log(backendName())"
-   ```
-   Print a one-line notice: `Search backend: fts5 | ripgrep | node-grep`.
-
-3. **Reindex if requested**: run
-   ```bash
-   node -e "require('./scripts/lib/design-search.cjs').reindex(process.cwd())"
-   ```
-   Print: "Index rebuilt."
-
-4. **Search**: run
-   ```bash
-   node -e "
-   const s=require('./scripts/lib/design-search.cjs');
-   const r=s.search(process.argv[1], process.cwd(), {limit:20});
-   console.log(JSON.stringify(r));
-   " -- "<query>"
-   ```
-   Parse the JSON array of `{file, line, text}` objects.
-
-5. **Format results**: print in this shape:
-   ```
-   ## Recall: "<query>"  (N matches, backend: fts5)
-
-   ### 1. .design/archive/cycle-2/EXPERIENCE.md:42
-   > Decided to skip dark-mode token layer in cycle 2 — cost–benefit did not clear threshold
-
-   ### 2. .design/learnings/LEARNINGS.md:18
-   > L-03 · color · cited:4 · Color contrast failures cluster around interactive states, not surfaces
-   ```
-   Group by file. Truncate text at 120 chars. Cap at 20 results.
-
-6. **Signal relevance**: for every result whose text contains an `L-NN` learning ID, record a `surfaced` signal:
-   ```bash
-   node -e "
-   const rc=require('./scripts/lib/relevance-counter.cjs');
-   rc.record('L-NN','surfaced','.design');
-   "
-   ```
-
-7. **Empty result**: if no matches, print:
-   ```
-   No matches for "<query>" in cross-cycle memory.
-   Tip: run /gdd:recall --reindex if the archive has been updated since last index build.
-   ```
-
-## Do Not
-
-- Do not modify any source file.
-- Do not run git commands.
-- Do not write `.design/STATE.md`.
-
-## RECALL COMPLETE

package/dist/claude-code/.claude/skills/reflect/SKILL.md

@@ -1,85 +0,0 @@
----
-name: gdd-reflect
-description: "Run design-reflector on demand - produces .design/reflections/<cycle-slug>.md with improvement proposals. Review proposals with /gdd:apply-reflections."
-argument-hint: "[--dry-run] [--cycle <slug>]"
-tools: Read, Write, Task
----
-
-@reference/retrieval-contract.md
-
-# /gdd:reflect
-
-Run `design-reflector` on demand against the current (or specified) cycle. Produces `.design/reflections/<cycle-slug>.md` with numbered improvement proposals. Every proposal requires explicit user review - nothing is auto-applied.
-
-## Steps
-
-1. **Parse args**: extract `--dry-run` flag and `--cycle <slug>` value.
-
-2. **Resolve cycle slug**:
-   - If `--cycle <slug>` given: use that slug directly
-   - Else: read `.design/STATE.md`, extract the active `cycle:` ID from the `<position>` block
-   - If STATE.md not found: abort with "No .design/STATE.md found. Run `/gdd:new-project` first."
-
-3. **Build required-reading list**:
-   ```
-   .design/STATE.md
-   .design/DESIGN-VERIFICATION.md
-   .design/learnings/*.md (glob)
-   .design/telemetry/costs.jsonl
-   .design/agent-metrics.json
-   .design/learnings/question-quality.jsonl
-   .design/cycles/<slug>/CYCLE-SUMMARY.md
-   .design/authority-report.md
-   ```
-   Use the resolved slug where `<slug>` appears.
-
-3.5. **Optional: capability-gap pre-scan** (Phase 29 Plan 02; runs only if `.design/config.json.reflector.capability_gap_scan_enabled !== false`):
-   See @skills/reflect/procedures/capability-gap-scan.md for the full procedure.
-   The `design-reflector` agent runs the scan automatically as part of its reflection pass; this step lets users dry-run it independently with:
-   ```
-   node scripts/lib/reflector/capability-gap-scan.cjs --dry-run
-   ```
-   The scan emits `capability_gap` events (`source: "reflector_pattern"`) for recurring patterns lacking a dedicated executable owner; Plan 29-03 aggregates these for `/gdd:apply-reflections`.
-
-4. **Spawn design-reflector**:
-   ```
-   Task("design-reflector", """
-   <required_reading>
-   @.design/STATE.md
-   @.design/DESIGN-VERIFICATION.md
-   @.design/agent-metrics.json
-   @.design/telemetry/costs.jsonl
-   @.design/learnings/question-quality.jsonl
-   </required_reading>
-
-   Cycle slug: <slug>
-   Dry-run: <true|false>
-
-   Produce .design/reflections/<slug>.md with all reflection sections and proposals.
-   If dry-run is true, print proposals to stdout only — do not write the file.
-   """)
-   ```
-
-5. **After completion**:
-   - If `--dry-run`: print the agent output directly; skip steps below
-   - Else: read `.design/reflections/<slug>.md`
-   - Count proposals by type (scan for `[FRONTMATTER]`, `[REFERENCE]`, `[BUDGET]`, `[QUESTION]`, `[GLOBAL-SKILL]`)
-   - Print summary:
-     ```
-     Reflection complete — cycle: <slug>
-     Proposals: N total
-       [FRONTMATTER] N
-       [REFERENCE] N
-       [BUDGET] N
-       [QUESTION] N
-       [GLOBAL-SKILL] N
-
-     Review and apply: /gdd:apply-reflections
-     ```
-
-## Do Not
-
-- Do not auto-apply any proposal.
-- Do not modify agent files, reference files, or budget.json.
-- Do not run the full audit pipeline - this is a standalone reflection run.
-- Do not bypass the threshold knob. The default `reflector.capability_gap_threshold: 3` exists to suppress noise; do NOT lower it below 1.

package/dist/claude-code/.claude/skills/reflect/procedures/capability-gap-scan.md

@@ -1,120 +0,0 @@
-# Procedure: reflector pattern-detection capability-gap scan
-
-Run during the reflection pass to detect recurring patterns lacking a dedicated executable owner; emit `capability_gap` events with `source: "reflector_pattern"` (Phase 29 Plan 02) for Plan 29-03 to aggregate.
-
-## Inputs
-
-Three signal sources are scanned. All paths are repo-relative; the scan tolerates absent sources (returns `[]` from that source, no error):
-
-- `.design/intel/*.md` - Phase 11 intel-store slice files. The scan extracts `Touches:` lines, tokenizes the comma-separated value, and clusters slices that share the same canonical `(sortedTouches, agent_type)` signal.
-- `.design/telemetry/posterior.json` - Phase 23.5 bandit posterior file written by `scripts/lib/bandit-router.cjs`. The scan reads `arms[]` and flags arms whose `count >= threshold` AND whose `agent` is in `GENERIC_AGENT_FALLBACKS` (`general-purpose`, `default-executor`, `fallback`, `generic`) OR is not in the project's specialized-agent set.
-- `.design/gep/events.jsonl` - Phase 22 typed-causal event chain via `scripts/lib/event-chain.cjs`. The scan filters rows to the last `windowDays` (default 30), groups by `(sortedDecisionRefs, agent)`, and flags sequences that recur ≥ threshold times.
-
-## Outputs
-
-For each qualifying cluster:
-
-- One `capability_gap` event appended to `.design/gep/events.jsonl` via `appendChainEvent` from `scripts/lib/event-chain.cjs`.
-- The event's `payload` carries exactly the 7 fields documented in CONTEXT D-02: `event_id` (UUIDv4), `parent_event_id` (nullable), `source` (`"reflector_pattern"`), `context_hash` (sha256 of normalized signal), `intent_summary` (≤256 chars), `suggested_kind` (`"agent"` | `"skill"`), `evidence_refs[]` (TrajectoryRef pointers with `sha256:` content hash).
-- The orchestrator returns `{findings, emittedEventIds, skippedBelowThreshold}` to the caller (the `design-reflector` agent), which cites the event IDs in its run summary under `## Capability gaps emitted`.
-
-## Algorithm
-
-The orchestrator `runCapabilityGapScan(opts)` in `scripts/lib/reflector/capability-gap-scan.cjs` follows four phases:
-
-1. **Load threshold.** Resolve in priority order: `opts.threshold` → `.design/config.json` field `reflector.capability_gap_threshold` → `DEFAULT_THRESHOLD` (=3). Throws if the resolved value is non-integer or < 1.
-2. **Build agent inventory.** Read `agents/*.md` frontmatter `name:` fields; partition into specialized vs generic.
-3. **Three scans (parallel-safe in concept; sequential in code for simplicity).** Call `scanIntelTouchesClusters`, `scanPosteriorArms`, `scanTrajectorySlices` and concatenate findings.
-4. **Emit.** For each finding, call the injected `opts.emit` spy (tests) or the default emitter (`defaultEmitCapabilityGapEvent`, which calls `appendChainEvent` from `scripts/lib/event-chain.cjs`). Collect returned `event_id`s.
-
-Key entry points (all exported from the module):
-
-- `computeContextHash({touches, agent_type})` - pure deterministic hash (sha256 of normalized JSON; touches are sorted ASCII-asc).
-- `scanIntelTouchesClusters({intelDir, existingAgents, threshold, baseDir})`
-- `scanPosteriorArms({posteriorPath, specializedAgents, threshold, baseDir})`
-- `scanTrajectorySlices({chainPath, windowDays, threshold, specializedAgents, baseDir})`
-- `runCapabilityGapScan(opts)` - orchestrator.
-
-The `context_hash` is the join key for Plan 29-03's aggregation: the same signal across runs produces the same hash regardless of touches-list ordering.
-
-## Threshold configuration
-
-The scan honors `reflector.capability_gap_threshold` in `.design/config.json`. Default `N = 3` (must be integer ≥ 1). Override knob documented in `.design/config.example.json`.
-
-To raise the threshold (suppress noise):
-
-```json
-{
-  "reflector": {
-    "capability_gap_threshold": 5
-  }
-}
-```
-
-To dry-run with an injected threshold without writing the config file:
-
-```bash
-node -e "console.log(JSON.stringify(require('./scripts/lib/reflector/capability-gap-scan.cjs').runCapabilityGapScan({threshold: 5, emit: () => 'DRY'}), null, 2))"
-```
-
-## Hard exclusions (D-08)
-
-MCP-probe failures MUST NOT contribute to any scan. Connection observability is Phase 22's separate surface; mixing those signals into the capability-gap stream would pollute Plan 29-03's clustering.
-
-The scan filters rows matching ANY of the following three shapes (liberal exclusion):
-
-- `outcome === 'connection-error'`
-- `agent === 'mcp-probe'`
-- `mcp_probe: true`
-
-The exclusion is enforced in `scanTrajectorySlices` via the internal `isMcpProbeRow` predicate (also exported for tests). Tests assert all three exclusion shapes regress separately.
-
-## Evidence-refs contract (D-07)
-
-Each event's `evidence_refs[]` is a list of POINTERS to source slices, never duplicated content. The scan emits items in the schema's `TrajectoryRef` shape:
-
-```typescript
-interface TrajectoryRef {
-  trajectory_path: string;   // repo-relative path
-  byte_start:      number;   // inclusive byte offset
-  byte_end:        number;   // exclusive byte offset
-  content_hash:    string;   // "sha256:" + 64-hex
-}
-```
-
-Internally, the scan carries a line-based `{path, lineStart, lineEnd, sha256}` shape on each `Finding.evidence_refs`. The `lineRefToTrajectoryRef` translator converts to the schema shape at emit time. The sha256 algorithm: read lines `[lineStart..lineEnd]` (1-based inclusive), join with `'\n'` (no trailing newline - stable across OSes), sha256 the UTF-8 bytes.
-
-Consumers (Plan 29-03 + audit tooling) re-read the slice and recompute the hash; mismatch = chain mutation; abort + warn.
-
-## CLI dry-run
-
-```bash
-node scripts/lib/reflector/capability-gap-scan.cjs --dry-run
-```
-
-Runs all three scans against the current working directory and prints findings (and would-be event payloads) without writing to `.design/gep/events.jsonl`. Useful for operator-side inspection of what the design-reflector agent would emit on the next reflection pass.
-
-Without `--dry-run`, the CLI writes events to the chain file and prints a one-line summary: `emitted N capability_gap event(s); skipped M below threshold`.
-
-## Testing
-
-Tests live at `tests/reflector-capability-gap.test.cjs` and run on synthetic in-tmpdir fixtures only (D-11 - no live writes to real `.design/`). Each test passes an injected `emit` spy so no real `appendChainEvent` calls occur. The hash-pin mutation-detection regression is enforced by a dedicated test: re-read the pointed-to slice, recompute the sha256, and assert mismatch after the source file is mutated.
-
-Run the tests directly:
-
-```bash
-node --test tests/reflector-capability-gap.test.cjs
-```
-
-Run the full suite to verify no regressions in `tests/reflection-proposal.test.cjs` or `tests/reflector-cross-runtime.test.cjs`:
-
-```bash
-npm test
-```
-
-## See also
-
-- `reference/schemas/events.schema.json` - the `capability_gap` event class shipped by Plan 29-01 (the 7-field shape + `TrajectoryRef` definition).
-- `scripts/lib/event-chain.cjs` - `appendChainEvent` (the real emitter API; 29-01 did NOT ship a separate helper file).
-- `scripts/lib/bandit-router.cjs` - Phase 23.5 posterior file producer (the source for scan #2).
-- `.planning/phases/29-capability-gap-self-authoring/CONTEXT.md` - phase decisions (D-02 7-field shape, D-07 hash-pinning, D-08 MCP carve-out, D-11 tmpdir tests).

package/dist/claude-code/.claude/skills/report-issue/SKILL.md

@@ -1,53 +0,0 @@
----
-name: report-issue
-description: "Consent-gated GitHub issue reporter for /gdd. Triages locally against `reference/known-failure-modes.md`, layers Phase 22 secret-redaction with Phase 30 pseudonymization, drafts the payload to `.design/issue-drafts/`, opens `$EDITOR` for inspection, and submits via the user's `gh` CLI to a hardcoded repo only after explicit per-issue consent. Use when the user runs `/gdd:report-issue`, hits a failure on a whitelisted command with the `--report` flag, or asks to file a bug against get-design-done."
-argument-hint: "[<command-name>] [--force-report]"
-tools: Read, Write, Grep, Bash
----
-
-# /gdd:report-issue
-
-Local-first, consent-gated GitHub issue reporter. No auto-mode. Destination repo is hardcoded. The full step-by-step lives in [report-issue-procedure.md](./report-issue-procedure.md); this file is the entry contract.
-
-## Pre-flight
-
-If invoked without an error context (the user just typed `/gdd:report-issue` cold), ask in one round-trip: *"What command failed and what was the error?"* Capture command name + a paraphrase of the error. Don't interrogate - one short answer is enough to feed the triage matcher.
-
-## Steps
-
-0. **Kill-switch** (D-08). Call `isDisabled()` from `scripts/lib/issue-reporter/kill-switch.cjs` FIRST. Either env (`GDD_DISABLE_ISSUE_REPORTER=1`) OR config (`.design/config.json` with `{ "issue_reporter": false }`) makes the command unavailable. Surface the disable line via `getDisableReason()` ('env' wins when both set) and stop. No draft, no triage, no payload. `/gdd:health` mirrors the same line for at-a-glance verification.
-1. **Triage**. Call `matchKnownFailure(errorContext)` from `scripts/lib/issue-reporter/triage-matcher.cjs` (Plan 30-03). If `matched === true` and `--force-report` is NOT set: print the suggested diagnosis + remedy, stop. Do NOT write a draft. (D-07)
-2. **Assemble**. Call `assemble(commandName, errorContext, trajectoryRef?, capabilityGapEvent?)` from `scripts/lib/issue-reporter/payload-assembly.cjs` (Plan 30-02). This layers Phase 22 redact → Phase 30 pseudonymize, computes the fingerprint, and renders bilingual disclaimer + sections.
-3. **Draft**. Call `writeDraft({title, body, fingerprint})` from `scripts/lib/issue-reporter/draft-writer.cjs`. Print the absolute path: `Draft written to .design/issue-drafts/<timestamp>-<fp8>.md`. The file persists across decline - the user keeps their work either way. (D-04)
-4. **Dedup** (D-06). Call `searchByFingerprint(fingerprint, {destination})` from `scripts/lib/issue-reporter/dedup.cjs`. If `degraded === true` show a one-line warning and fall through to Step 5. If `matches.length === 0` fall through to Step 5 unchanged. If `matches.length >= 1` render the dedup UI listing each `{number,title,url}` with three actions per match: **`+1`** → `react(n, {destination})` (no new issue, D-06), **`me-too`** → `commentMeToo(n, {destination, errorContext, runtime, pluginVersion})` body is EXACTLY 3 fields (last error line, runtime, plugin version) from the ALREADY-pseudonymized 30-02 pipeline (D-01), **`new`** → fall through to Step 5 with the prepared draft despite the match.
-5. **Edit**. If `$EDITOR` is set, the consent prompt opens it on the draft and blocks until exit. Otherwise the path is printed and the user can open it manually. `EDITOR` is the only env var the report flow reads.
-6. **Consent**. Call `promptConsent({draftPath})` from `scripts/lib/issue-reporter/consent-prompt.cjs`. Re-reads the (possibly edited) draft from disk, prints a summary, asks `Submit this issue to hegemonart/get-design-done? [y/N]`. Anything other than `y`/`yes` declines. (D-03)
-   - Throws if `process.stdin.isTTY` is false (no auto-mode).
-   - Throws if any `process.env` key matching `/REPORT|ISSUE|AUTO_REPORT/i` is set to a truthy value.
-7. **Submit**. On `y`, call `submitViaGh({title, body})` from `scripts/lib/issue-reporter/gh-submit.cjs`. This spawns `gh issue create --repo hegemonart/get-design-done --title <title> --body-file <tmp>`. Destination is hardcoded; no env var or flag can redirect it. (D-02 + D-05)
-8. **gh-absent fallback** (D-10). If `detectGh()` from `scripts/lib/issue-reporter/gh-absent-fallback.cjs` returns false BEFORE Step 7 runs: call `runFallback(consent.finalBody)` to copy the (already-pseudonymized) payload to the clipboard via the platform's clipboard command (`pbcopy` on macOS, `wl-copy`/`xclip` on Linux, `clip.exe` on Windows) and print the message `gh CLI not found; payload copied to clipboard, paste into the link below.` followed by the issue-template URL. The draft persists on disk for re-submission once `gh` is installed.
-
-## Use through `--report`
-
-Whitelisted to specific commands via `scripts/lib/issue-reporter/cli-flag-report.cjs`. Only `gdd:plan-phase`, `gdd:execute-phase`, and `gdd:report-issue` itself install the flag - and only when `reference/known-failure-modes.md` has at least one `propose_report: true` entry. Non-whitelisted commands silently do not see the flag. (D-11)
-
-## Use through `--force-report`
-
-Available on `/gdd:report-issue`. Overrides the triage gate (Step 1) but does NOT override consent. The user still gets the draft + consent prompt. There is no path to submit without an explicit `y`.
-
-## Privacy contract
-
-- **Pseudonymization, not anonymization.** Disclaimer (Russian + English) is rendered at the top of the payload by Plan 30-02. Side-channel content (writing style, code patterns) may still re-identify. The user reviews the exact bytes before consenting.
-- **No auto-mode, no env-var bypass.** Static tests (`tests/report-issue-no-auto-submit-static.test.cjs`) fail the build if anyone adds a `process.env.*REPORT*`/`*ISSUE*`/`*AUTO_REPORT*` read here or under `scripts/lib/issue-reporter/`. Runtime check in `consent-prompt.cjs` is the second layer.
-- **Hardcoded destination.** `scripts/lib/issue-reporter/destination.cjs` is the only file that contains the literal repo string; it exports a frozen object so runtime tampering throws. Static tests enforce both invariants.
-- **No HTTPS, no fetch.** Submission goes through the user's `gh` CLI only. Plan 30-07 ships a CI gate that fails the build if any network primitive is added here.
-
-## Troubleshooting
-
-- **`gh` not authenticated.** The submission step fails with a clear error pointing to the draft path. Run `gh auth login` and re-invoke `/gdd:report-issue` - the draft survives.
-- **No `EDITOR` set.** The path is printed; open it in whatever editor you prefer, save, then return to the consent prompt.
-- **Triage matched something irrelevant.** Pass `--force-report` to bypass the gate. Consent is still required.
-- **`gh` not installed (D-10).** After consent, the payload is copied to your clipboard and an issue-template URL is printed. Paste into the URL to file manually. Install `gh` later and the existing draft can be re-submitted.
-- **Command unavailable / disabled (D-08).** Run `/gdd:health`. The `issue reporter:` line shows the active disable surface - either `disabled by env (GDD_DISABLE_ISSUE_REPORTER=1)` or `disabled by config (.design/config.json: issue_reporter=false)`. Unset the env var or flip the config key to re-enable.
-
-See [report-issue-procedure.md](./report-issue-procedure.md) for the full procedure with rationale per decision (D-02, D-03, D-04, D-05, D-07, D-11).

package/dist/claude-code/.claude/skills/report-issue/report-issue-procedure.md

@@ -1,120 +0,0 @@
-# `/gdd:report-issue` - Full Procedure
-
-Long-form companion to [SKILL.md](./SKILL.md). Phase 28.5 keeps SKILL.md ≤100 lines; step-by-step + rationale live here.
-
-## Architecture
-
-The report flow is the only outbound path the plugin offers. Every byte leaving the user's machine via this surface:
-
-1. has been redacted for secrets (Phase 22 `redact.cjs`),
-2. has been pseudonymized for identity (Plan 30-01 `pseudonymize.cjs`),
-3. has been written to disk where the user can read it,
-4. has cleared a pre-submit dedup check against the destination repo (Plan 30-05) - `+1` and `me-too` on a matching existing issue NEVER spawn a duplicate (D-06),
-5. has been read back from disk after the user closed the editor, and
-6. has cleared an explicit per-issue `y/N` prompt.
-
-No environment variable, command-line flag, or build configuration bypasses any of these steps. Two test layers enforce this:
-
-- **Static** (`tests/report-issue-destination-static.test.cjs`, `tests/report-issue-no-auto-submit-static.test.cjs`) - fail the build on any forbidden code pattern in `skills/report-issue/` or `scripts/lib/issue-reporter/`.
-- **Runtime** (`tests/report-issue.test.cjs`) - 26 cases proving the orchestrator threads consent + persistence + edit-before-submit + triage + hardcoded destination + flag whitelist.
-
-## Steps
-
-### Step 1 - Triage gate (D-07)
-
-`matchKnownFailure(errorContext)` regex-matches `error.message + error.stack` against `reference/known-failure-modes.md`. If matched, prints diagnosis + remedy and exits without writing a draft. `--force-report` overrides the gate but does NOT override consent.
-
-### Step 2 - Assemble payload (D-01)
-
-`assemble(commandName, errorContext, trajectoryRef?, capabilityGapEvent?)` returns markdown. Order is locked: redact → pseudonymize (Case 9 of 30-02 enforces). Bilingual disclaimer at top: "Это псевдонимизация, не анонимизация" / "This is pseudonymization, not anonymization." Fingerprint computed on the scrubbed stack so the same bug from different cwd's hashes the same.
-
-### Step 3 - Write draft (D-04)
-
-`writeDraft({title, body, fingerprint})` writes to `.design/issue-drafts/<YYYYMMDDTHHMMSSZ>-<fp8>.md`. The file has a small HTML-comment header (timestamp, destination, full fingerprint) so a future maintainer with a corrupted-looking draft can reconstruct provenance. The file is NOT deleted on decline - the user keeps their work.
-
-### Step 4 - Pre-submit dedup (D-06)
-
-`scripts/lib/issue-reporter/dedup.cjs` exports `searchByFingerprint(fingerprint, {destination})` which spawns `gh issue list --search "fingerprint:<hash>" --json number,title,url --repo <destination>` (read-only). Resolves `{matches: [...], degraded?, reason?}` - NEVER throws on gh failure.
-
-Routing:
-
-- `matches.length === 0` (no existing issue) **or** `degraded === true` (search unavailable; surface a one-line warning) → fall through to Step 5 with the prepared draft.
-- `matches.length >= 1` → render the dedup UI listing each `{number, title, url}` with three actions per match:
-
-  - **`+1`** → `react(n, {destination})` spawns `gh api -X POST /repos/<destination>/issues/<n>/reactions -f content=+1`. Resolves `{ok:true}`; exits the report flow on success ("reaction recorded on #<n>"). **NO new issue is created** (D-06).
-  - **`me-too`** → `commentMeToo(n, {destination, errorContext, runtime, pluginVersion})` spawns `gh issue comment <n> --repo <destination> --body <body>`. The body contains EXACTLY three fields (`Last error:`, `Runtime:`, `Plugin version:`) - nothing more (negative-presence tested). `errorContext.lastErrorLine` is the ALREADY-pseudonymized last error line from 30-02's payload pipeline (D-01); dedup.cjs does NOT re-derive raw stderr. Exits the report flow on success ("comment added to #<n>"). **NO new issue is created** (D-06).
-  - **`new`** → fall through to Step 5 with the prepared draft despite the match (user explicitly opted to force a new issue).
-
-`+1` and `me-too` failures (auth/network/rate) propagate as rejected promises with annotated `.reason` so the caller can offer retry/cancel - they do NOT silently fall back to creating a new issue (that would defeat dedup intent).
-
-Wiring: `runReportFlow` calls `options.dedupCheck({fingerprint, title})` BEFORE the consent prompt (`report-flow.cjs` STEP 4). The skill drives the `+1`/`me-too`/`new` UI by passing a `dedupCheck` callback that wraps `searchByFingerprint` + the `react`/`commentMeToo` calls. Returning truthy `existing` from the callback short-circuits `runReportFlow` to `{submitted:false, reason:'duplicate'}`. Returning falsy continues to Step 5.
-
-### Step 5 - Edit (optional)
-
-If `$EDITOR` is set, `promptConsent` spawns it on the draft path and blocks until exit. Otherwise the user opens it manually. `EDITOR` is a POSIX convention (git, crontab, gh all use it); the static-grep test only forbids env-var reads matching `/REPORT|ISSUE|AUTO_REPORT/i`.
-
-### Step 6 - Consent prompt (D-03)
-
-The single submission gate for the new-issue path. Three preconditions must hold:
-
-1. `process.stdin.isTTY === true`.
-2. No env var matches `/REPORT|ISSUE|AUTO_REPORT/i` with a truthy value (`rejectBypassEnv` throws otherwise, naming the offender).
-3. The draft file exists and is readable.
-
-The function prints a summary (destination, draft path, title, first 10 body lines), asks `Submit this issue to hegemonart/get-design-done? [y/N]` via `readline`, treats anything other than `y`/`yes` (case-insensitive, trimmed) as decline, and **re-reads the draft from disk** so user edits in Step 5 are picked up.
-
-(The `+1` / `me-too` paths from Step 4 do NOT pass through this consent prompt - selecting either action in the dedup UI IS the explicit consent for that minimal interaction. The new-issue path always passes through this prompt.)
-
-### Step 7 - Submit via `gh` (D-05 + D-02)
-
-`submitViaGh({title, body})` spawns:
-
-```bash
-gh issue create --repo hegemonart/get-design-done --title <title> --body-file <tmp/body.md>
-```
-
-Body is written to a tmp file to avoid arg-length and shell-escaping. URL parsed from stdout. No HTTPS, no fetch, no third-party packages - only the user's `gh` CLI with their credentials.
-
-## The `--report` flag (D-11)
-
-`cli-flag-report.cjs` whitelists three commands today: `gdd:plan-phase`, `gdd:execute-phase`, `gdd:report-issue`. The whitelist intersects with `listProposeReportModes()`; if the catalogue has zero `propose_report: true` entries, the flag disables everywhere. `installReportFlagOn(parser, commandName)` is a no-op for non-whitelisted commands; `parseReportFlag` returns `{report: false}` regardless of argv.
-
-## Privacy guarantees
-
-| Layer | Guarantee | Enforced by |
-|---|---|---|
-| Static code | No `process.env.*REPORT*`/`*ISSUE*`/`*AUTO_REPORT*` reads in the report tree | `report-issue-no-auto-submit-static.test.cjs` |
-| Static string | Only `destination.cjs` may contain the literal repo string | `report-issue-destination-static.test.cjs` |
-| Static flag | No `--yes` / `--no-confirm` / `--auto-confirm` / `--auto-submit` strings | `report-issue-no-auto-submit-static.test.cjs` |
-| Runtime frozen | `DESTINATION_REPO` reassignment throws | static test S3 + behavioural H2 |
-| Runtime env | `rejectBypassEnv` throws on truthy forbidden env var | `report-issue.test.cjs` B1, U1 |
-| Runtime TTY | `promptConsent` throws on `!stdin.isTTY` | C5 |
-| Runtime consent | Only `y`/`yes` accepted | C1..C3, U3 |
-| Runtime re-read | `promptConsent` re-reads draft before returning final body | E1, E2 |
-| Runtime destination | `submitViaGh` always passes `--repo hegemonart/get-design-done` | H1 |
-| Dedup destination | `dedup.cjs` accepts `destination` only as a parameter - no env/config lookup (D-02) | `issue-reporter-dedup.test.cjs` test 11 |
-| Dedup body shape | `buildMeTooBody` returns EXACTLY 3 lines (`Last error:` / `Runtime:` / `Plugin version:`) - no stack/path/env/cmd (D-06) | tests 5 + 6 (verbatim + negative-presence) |
-| Dedup network | `dedup.cjs` imports only `child_process`; no outbound URL literals, no global fetch primitive, no third-party HTTP client libraries (D-05) | 30-07 static-grep gate |
-| Dedup test hermeticity | No live `gh` calls in CI; injected spawn spy + traced `child_process.spawnSync` counter assert 0 real invocations (D-13) | `issue-reporter-dedup.test.cjs` test 10 |
-| Dedup pseudonymization | `me-too` body uses the ALREADY-pseudonymized `errorContext.lastErrorLine` from 30-02's pipeline; dedup.cjs does NOT re-derive raw stderr (D-01) | dedup test "commentMeToo passes pseudonymized lastErrorLine through to gh body" |
-
-## Troubleshooting
-
-- **`gh` not authenticated**: submission throws with status + stderr; draft path preserved. Run `gh auth login`, retry. (T-30-04-08 accepted)
-- **`EDITOR` spawns wrong tool**: set `EDITOR=<your-editor>` in shell rc.
-- **Triage matched something irrelevant**: pass `--force-report`. Consent still required.
-- **TTY refused (CI / non-interactive)**: by design - run locally. (T-30-04-05 mitigated)
-- **No `--report` flag on a command you expected**: not on the whitelist; file an issue via this flow describing the use case.
-
-## Forward-looking hooks
-
-- **Plan 30-05** *(landed)* - `scripts/lib/issue-reporter/dedup.cjs` wires `options.dedupCheck` to `gh issue list --search "fingerprint:<hash>"`. The skill drives the `+1` / `me-too` / `new` UI by passing a `dedupCheck` callback that wraps `searchByFingerprint` + `react` + `commentMeToo`. The hook in `runReportFlow` now runs BEFORE consent (per D-06).
-- **Plan 30-06** *(landed)* - `scripts/lib/issue-reporter/kill-switch.cjs` adds the D-08 dual-surface disable check (`GDD_DISABLE_ISSUE_REPORTER=1` env OR `.design/config.json: { "issue_reporter": false }` config). `runReportFlow` calls `isDisabled()` as **Step 0**, BEFORE triage and any draft writing - when disabled, returns `{ submitted:false, reason:'disabled', surface:'env'|'config', message }`. `scripts/lib/issue-reporter/gh-absent-fallback.cjs` adds the D-10 clipboard+URL path (pbcopy / wl-copy → xclip / clip.exe) - invoked after consent when `detectGh()` returns false. `scripts/lib/gsd-health-mirror/index.cjs` mirrors the disable surface as a 5th health check; output is exactly one of: `issue reporter: enabled` / `issue reporter: disabled by env (GDD_DISABLE_ISSUE_REPORTER=1)` / `issue reporter: disabled by config (.design/config.json: issue_reporter=false)`. Tests at `tests/issue-reporter-fallback.test.cjs` (15 cases). Env wins precedence when both flags are set (matches gsd-health display).
-- **Plan 30-07** ships the network-isolation CI gate. Plans 30-04 and 30-05 already meet the invariant (no outbound URL literals, no global fetch primitive, no third-party HTTP client libraries - see `tests/issue-reporter-network-isolation.test.cjs` for the enforced forbidden-token list); the gate locks it in.
-
-## References
-
-- [SKILL.md](./SKILL.md) - entry contract.
-- `reference/pseudonymization-rules.md` - full R1..R8 rule catalog (Plan 30-01).
-- `reference/known-failure-modes.md` - triage catalogue (Plan 30-03).
-- `.planning/phases/30-issue-reporter/CONTEXT.md` - phase decisions D-01..D-15.

package/dist/claude-code/.claude/skills/resume/SKILL.md

@@ -1,93 +0,0 @@
----
-name: gdd-resume
-description: "Restore session context from a numbered checkpoint. Lists available checkpoints when no argument given."
-argument-hint: "[<N>]"
-tools: Read, Write, Bash, Glob, AskUserQuestion, mcp__gdd_state__get, mcp__gdd_state__set_status, mcp__gdd_state__resolve_blocker, mcp__gdd_state__checkpoint, mcp__gdd_status, mcp__gdd_phase_current, mcp__gdd_plans_list, mcp__gdd_decisions_list
-disable-model-invocation: true
----
-
-@reference/retrieval-contract.md
-@reference/cycle-handoff-preamble.md
-
-# /gdd:resume
-
-Inverse of `/gdd:pause`. Reads a checkpoint file, prints a clear "you were here" summary, and routes to the next command.
-
-## Step 0 - Prime cycle context
-
-Two paths - MCP preferred when available, file-read fallback otherwise. This runs BEFORE checkpoint restoration so the "you were here" summary has full cycle context (phase, plans, decisions).
-
-### MCP path (preferred)
-
-When `mcp__gdd_status` is exposed (Phase 27.7+, registered via `npx @hegemonart/get-design-done --register-mcp`):
-
-1. Call `mcp__gdd_status` (no args) → `{phase, branch, last_decisions, last_completed_plans, blocker_count}`. One call replaces reading STATE.md + parsing frontmatter + extracting decisions.
-2. Call `mcp__gdd_cycle_recap` (no args) → diff vs last cycle snapshot. Critical for session-restoration context: what changed since you paused?
-3. Call `mcp__gdd_decisions_list` (no args) → full D-XX list with rationale. Use for the "decisions you made" line in the resume summary.
-4. (Optional) Call `mcp__gdd_plans_list` (no args) → current phase plans + status, to identify next incomplete plan.
-
-Three to four MCP calls = full resume priming (~5s, ~32k tokens - Storybloq benchmark). Proceed to Step 1.
-
-### File-read path (fallback)
-
-When MCP tools are not available:
-
-1. `Read .design/STATE.md` and parse the frontmatter + `<position>`, `<decisions>`, `<plans>` sections. Extract `cycle`, `branch`, `last N decisions`, `completed plans`.
-2. Also `Read .design/CYCLES.md` (if present) to see prior cycle state for the recap.
-3. Proceed to Step 1.
-
-This path loads the same context in 3–5 file reads (~60s, ~46.5k tokens - file-reading baseline).
-
-## Steps
-
-1. **Parse argument**:
-   - If argument is a number N → restore checkpoint N.
-   - If no argument → list available checkpoints and ask which to restore (see step 2).
-
-2. **List mode** (no argument):
-   ```bash
-   ls .design/checkpoints/ 2>/dev/null | sort -n
-   ```
-   If empty, fall back to reading `.design/HANDOFF.md` (legacy single-slot format).
-   If checkpoints exist, present the list and ask (AskUserQuestion):
-   "Which checkpoint would you like to restore? (enter number, or press Enter for the latest)"
-   Use the answer (or latest if Enter pressed) as N.
-
-3. **Read checkpoint**: load `.design/checkpoints/NN-*.md`. If not found, try `.design/HANDOFF.md` as legacy fallback.
-
-4. **Check paused status via MCP**: call `mcp__gdd_state__get` and inspect `status`. If it does **not** start with `paused:`, print "No pause to resume" and exit - the prior session was not paused via `/gdd:pause`, so there is nothing to restore.
-
-5. **Restore prior status via MCP**: parse the prior status from the `paused:<prior>` prefix. Call `mcp__gdd_state__set_status` with `status: <prior>` to restore the pre-pause state.
-
-6. **Clear the pause blocker**: optionally call `mcp__gdd_state__resolve_blocker` to clear the pause-related blocker (match by text containing "paused"). Skip if no such blocker exists.
-
-7. **Stamp last_checkpoint via MCP**: call `mcp__gdd_state__checkpoint`.
-
-8. **Print summary** in this exact shape:
-   ```
-   Checkpoint NN restored.
-   Saved: <timestamp>
-   You were: <in-progress description>
-   Next step: <next>
-   Active sketch: <path or none>
-   Open todos: <N>
-   ```
-
-9. **Staleness check**: compare mtime of `.design/` artifacts vs `src/` via Bash `stat` when available. If `src/` has commits newer than the checkpoint timestamp, warn:
-   "Source has changed since checkpoint NN - consider re-running explore or verify."
-
-10. **Route recommendation** based on checkpoint `Stage:` field:
-    - `brief` → "Run `/gdd:brief`"
-    - `explore` → "Run `/gdd:explore`"
-    - `plan` → "Run `/gdd:plan`"
-    - `design` → "Run `/gdd:design` to continue"
-    - `verify` → "Run `/gdd:verify`"
-
-## Do Not
-
-- Do not delete checkpoint files.
-- Do not mutate STATE.md directly - all STATE.md writes go through the `gdd-state` MCP tools above.
-- Do not auto-execute the next command - just recommend.
-- Do not call `mcp__gdd_state__transition_stage` - resume restores prior status without moving the pipeline.
-
-## RESUME COMPLETE