start-vibing 4.4.8 → 4.4.10

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "start-vibing",
-	"version": "4.4.8",
+	"version": "4.4.10",
 	"description": "Setup Claude Code with 9 plugins, 6 community skills, and 8 MCP servers. Parallel install, auto-accept, superpowers + ralph-loop. e2e-audit 0.2.0 refactor (skill-only, no agents): SessionStart hook + slash command make the skill keyword-invokable (\"e2e audit\", \"roda o e2e\", \"integration test\", \"test coverage gaps\"). Source-first discovery via detect-stack, discover-routes (Next app/pages/Remix/SvelteKit/Nuxt/Astro), discover-api-surface (HTTP handlers, tRPC procedures, GraphQL, server actions, middleware auth), inventory-existing-tests (preserve prior corpus + sha256 drift hash), and detect-uncovered (branch-diff vs origin/main finds changes not covered by existing specs). Report-then-ask between mapping and Playwright run; post-run-feedback report before writing findings. SHOT+TRACE+ASSERT+SOURCE evidence quad per non-meta finding; meta rules (coverage-gap-*, uncovered-*, test-drift, stack-detect, post-run-feedback) exempt. verify-audit.sh enforces schema + quad. Generic (no project leakage). super-design 0.7.0 carries over.",
 	"type": "module",
 	"bin": {

package/template/.claude/agents/research-scout.md

@@ -1,6 +1,6 @@
 ---
 name: research-scout
-description: MUST BE USED at the start of every research run to produce scout-plan.json. Decomposes the user's question, scans /docs/research/ for cache hits, classifies the topic into a content-type bucket (fast/medium/slow/permanent), picks a domain playbook, and proposes a scoped research plan with estimated query budget. Stops before any web query so the orchestrator can run the report-then-ask gate.
+description: MUST BE USED at the start of every research run to produce scout-plan.json. Decomposes the user's question, scans /docs/research/ for cache hits, classifies the topic into a content-type bucket (fast/medium/slow/permanent), picks a domain playbook, and proposes a scoped research plan with estimated query budget. Returns scout-plan.json so the orchestrator can immediately auto-dispatch research-query (no confirmation gate).
 tools: Read, Write, Glob, Grep, Bash
 model: haiku
 color: cyan
@@ -113,7 +113,8 @@ Write to `$SESSION_DIR/scout-plan.json`:
 
 Return to the orchestrator a short text with: slug, decomposition count,
 estimated queries, cache strategy, and any blockers. The orchestrator
-will run the report-then-ask gate with the user.
+prints a one-line summary and immediately dispatches research-query (no
+confirmation gate — user can interrupt mid-run).
 
 # Hard rules
 

package/template/.claude/hooks/research-session-start.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 cat <<'EOF'
-{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"When the user mentions research, investigate, find info, search for, look up, evaluate, compare, audit literature, competitor analysis, market research, library evaluation, prior art, pesquisar, pesquisa, pesquise, investigar, buscar info, procurar info, comparar, avaliar biblioteca, análise de mercado, análise de concorrentes — or asks to evaluate/compare/understand any technology, framework, vendor, methodology, or domain — you MUST invoke the research skill. Do not improvise a search plan, do not start WebSearch blind, do not skip the cache check. Read .claude/skills/research/SKILL.md first, then follow its entry flow precisely. The skill uses source-first scout (cache check + scoped plan) BEFORE touching the web, and emits a report-then-ask gate after scouting. Every non-meta claim must carry the URL+QUOTE+ACCESSED-AT+VERIFY-METHOD evidence quad. Output goes to /docs/research/<topic>.md, never to .claude/skills/research-cache/. Triangulation follows Denzin's 4 types — republication chains count as one source, not three. Content-type freshness has 4 buckets (fast/medium/slow/permanent); do not apply fast-bucket aging to slow-bucket topics. Hand off to super-design for UX audits and e2e-audit for test audits — research does not replace either."}}
+{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"When the user mentions research, investigate, find info, search for, look up, evaluate, compare, audit literature, competitor analysis, market research, library evaluation, prior art, pesquisar, pesquisa, pesquise, investigar, buscar info, procurar info, comparar, avaliar biblioteca, análise de mercado, análise de concorrentes — or asks to evaluate/compare/understand any technology, framework, vendor, methodology, or domain — you MUST invoke the research skill. Do not improvise a search plan, do not start WebSearch blind, do not skip the cache check. Read .claude/skills/research/SKILL.md first, then follow its entry flow precisely. The skill uses source-first scout (cache check + scoped plan) BEFORE touching the web, then auto-dispatches research-query immediately (no confirmation gate — user can interrupt mid-run). Every non-meta claim must carry the URL+QUOTE+ACCESSED-AT+VERIFY-METHOD evidence quad. Output goes to /docs/research/<topic>.md, never to .claude/skills/research-cache/. Triangulation follows Denzin's 4 types — republication chains count as one source, not three. Content-type freshness has 4 buckets (fast/medium/slow/permanent); do not apply fast-bucket aging to slow-bucket topics. Hand off to super-design for UX audits and e2e-audit for test audits — research does not replace either."}}
 EOF

package/template/.claude/skills/research/SKILL.md

@@ -27,7 +27,8 @@ Four-phase pipeline with 4 specialist agents:
 1. **Scout** (research-scout, Haiku) — decomposes the user's question, checks
    `/docs/research/` for existing fresh findings (content-type-calibrated
    freshness — fast/medium/slow/permanent buckets), proposes a scoped research
-   plan + estimated query budget. Stops here for `report-then-ask` gate.
+   plan + estimated query budget. Hands directly to Query — NO confirmation
+   gate (auto-proceed). User can interrupt mid-run if needed.
 2. **Query** (research-query, Sonnet) — executes web/library searches in
    parallel, fetches pages via WebFetch + context7 (for library docs),
    extracts atomic claims with URL+QUOTE+ACCESSED-AT evidence, dumps to
@@ -84,20 +85,18 @@ Pass `cache-check.json` + the user question. Scout returns
 }
 ```
 
-### Step 3 — Report-then-ask (HARD STOP)
+### Step 3 — Auto-proceed (no confirmation gate)
 
-Present a ≤6-line summary to the user:
+Print a ≤4-line summary for visibility, then immediately dispatch Query.
+Do NOT wait for user confirmation. The user can `/cancel` or interrupt
+mid-run if scope is wrong.
 
 ```
-Topic: react-server-components-data-fetching
-Domain: software-engineering · Playbook: library-evaluation
-Plan: 3 sub-questions, ~12 queries, ~8 min
-Cache: delta-update of /docs/research/react-server-components-data-fetching.md (47d old)
-Proceed? (y / scope-down / cancel)
+Topic: <slug> · Plan: <N> sub-questions, ~<Q> queries, ~<M> min
+Cache: <strategy> · Proceeding to query...
 ```
 
-Do NOT proceed to Step 4 without an explicit reply. Mirror the e2e-audit
-report-then-ask gate.
+Exception: if `--dry-run` flag is set, stop here and return scout-plan.json.
 
 ### Step 4 — Query (Task tool → research-query)
 
@@ -253,7 +252,7 @@ fingerprints + ownership trees.
 ## Hard rules
 
 1. **Cache first**. Never burn query tokens on a fresh cache hit.
-2. **Report-then-ask**. After scout, STOP for user confirmation before query.
+2. **Auto-proceed after scout**. Print summary, immediately dispatch query. NO confirmation gate. User can interrupt mid-run.
 3. **Every claim has URL+QUOTE+ACCESSED-AT+VERIFY-METHOD**. Verify gate fails closed on violations.
 4. **No fabricated citations, ever**. If a quote cannot be greppped in the fetched page, the claim is dropped.
 5. **Triangulate by Denzin type, not raw count**. 3 republications of one wire story = 1 source.