[ROSETTA] Make research source tooling capability-aware

[isolomatov-gd]

instructions/r3/core/skills/research/SKILL.md unconditionally requires DeepWiki and Context7 even though supported plugin-only targets do not guarantee either integration. Require available authoritative sources with capability checks and explicit vendor-documentation or web fallbacks, then update the skill README and regenerate all plugins.

[github-actions]

Rosetta Triage

Classification: task; instructions, documentation — correct a core R3 skill contract and its maintainer guidance.
Priority assessment: High. The current mandatory-tool rule can block systematic research for plugin-only targets that do not provide either named integration.

Findings:

• instructions/r3/core/skills/research/SKILL.md unconditionally puts MUST use DeepWiki and Context7 into each generated research prompt. This conflicts with the plugin delivery model, where instructions run locally and integrations are not provisioned by the plugin.
• The R3 README repeats the named-tool mandate. Generated Codex and Copilot standalone skill copies contain the same rule; the generic generator must regenerate all standard and lightweight outputs after the source correction.
• Preserve the existing grounding, evidence, self-validation, and explicit anecdotal-source warning. The defect is the unconditional tool requirement, not the quality bar.

Caveats:

• R2 has an equivalent rule, but R3 is the current release. Handle an R2 backport as a separate release-policy decision.

Suggestions:

• Define a capability-aware source contract: use available authoritative integrations when relevant; otherwise use available official vendor or project documentation through web or URL retrieval; if no authoritative source is reachable, report the limitation and do not invent evidence.
• Update the R3 skill README, regenerate plugin outputs rather than editing them directly, and add coverage for all three cases: both integrations, one integration, and neither integration with official documentation reachable. Also test the transparent no-authoritative-source path.

Next steps: update the two R3 source files, regenerate standard and lightweight plugins, then run the plugin-generator typecheck and tests.

Automated triage by Rosetta agent