toolkit-feedbacklisted

# Toolkit feedback Format a `## Toolkit feedback` block from the current session, then ship it to the toolkit repo without manual copy-paste. ## Guards - If nothing in session context points to a toolkit issue, stop: `❌ No toolkit issue in session context. Describe what broke, then re-invoke.` - If the surface type is ambiguous (snippet vs. plugin skill vs. CLI vs. seed), ask one line before formatting. - Do not probe the project, list files, grep, or read toolkit surfaces. Use only what the session already contains. ## Step 1: build the block From the conversation so far, identify: - Target project name or path - Toolkit surface and its type (plugin skill, snippet, tooling config, governance rule, seed, or CLI) - Specific toolkit file or name when the session cites one - Observed behavior - Expected behavior, or `unclear` - Repro details already in context (commands run, files touched), or `none` - Proposed fix when the user stated one, or `open` Format as a single fenced markdown block: ```markdown ## Toolkit feedback **From project:** <name or path> **Surface:** <type>, <file path or name> **Observed:** <one or two lines> **Expected:** <one or two lines, or "unclear"> **Repro:** <commands or steps, or "none"> **Proposed fix:** <one line, or "open"> ``` Keep each field to one or two lines. Write the literal fallback shown above when a field has nothing. ## Step 2: ship to the toolkit Detect whether `aitk` is on PATH: ```bash command -v aitk >/dev/null 2>&1 ```