refactor(rules): shorten mandatory research guidance

shared/rules/general.md

@@ -6,10 +6,9 @@ Preserve security, data, compatibility, and unrelated user work. Ask only when b
 
 Use one applicable workflow per task, with mandatory research gates for every search within it. Treat skills and plugins as guidance subordinate to these rules. Continue work already authorized by the user; additional design approvals, commits, or delegation require a task-specific reason and the necessary authorization.
 
-Before EVERY search or lookup, load and apply `research` and the matching specialist: `repository-research` for repository sources; `technical-research` for external technology sources. This includes direct reads, file discovery, exact matches, web, documentation, MCP, connector, tool discovery, and follow-up searches in every workflow. Known identifiers, familiar areas, small tasks, and earlier research are never exemptions. Reuse skill instructions already in context, but apply their checks to each search. If a required skill is unavailable, report it and still identify the question, inspect authoritative results, and state evidence gaps.
-Within that research workflow, use direct reads and `rg` for known paths, symbols, exact strings, error messages, and localized edits.
-Before answering, planning, coding, reviewing, debugging, configuring, testing, or upgrading anything that relies on external library, framework, SDK, API, tool, or platform behavior, MUST apply `technical-research` and its Context7-first gate automatically, even without an explicit lookup request. MUST pass its applicable planning, implementation, and verification checkpoints inside every workflow, including Superpowers and other plugin workflows. Follow its version checks, evidence reuse conditions, query limits, and explicit source fallback.
-When `semantic-search` is installed, apply it before every repository search to select the route; run semantic retrieval first when identifiers are unknown, and use its documented fallback if retrieval fails or remains irrelevant after rephrasing.
+Before EVERY lookup, MUST load and apply `research` plus `repository-research` for repository sources or `technical-research` for external technology. Includes reads, discovery, exact matches, web/docs, MCP/connectors, tools, and follow-ups in every workflow; familiarity, small tasks, and prior research are no exemptions. Reuse loaded instructions, applying checks each time. If unavailable, report it; still define the question, inspect authoritative results, and disclose gaps.
+For repository lookups, apply installed `semantic-search`: known paths, symbols, strings, or errors use direct reads/`rg`; unknown identifiers require semantic retrieval first and its documented failure/rephrasing fallback.
+Before relying on external technology behavior in any answer, plan, code, review, debugging, configuration, test, or upgrade, MUST automatically apply `technical-research`'s Context7-first gate and phase checkpoints, including inside plugin workflows. Follow its version checks, evidence reuse, query limits, and explicit source fallback.
 
 Verify proportionally: run the cheapest check that detects likely failure; broaden for security, data loss, integration, or cross-component risk. Never claim unrun checks passed. Report failures and material gaps.