feat: refresh shared skills catalog

skills/junior-to-senior/references/research-playbook.md

@@ -4,7 +4,7 @@ Reference for Phase 1 of the `junior-to-senior` skill: how the senior earns expe
 
 ## Track 1: Code research
 
-Goal: know what is *true here* before judging the plan against it. Prefer a context-isolated explore subagent for broad sweeps; bring back conclusions, not file dumps.
+Goal: know what is *true here* before judging the plan against it. Use focused searches and return conclusions with evidence rather than file dumps. Delegate only when the task or repository instructions authorize it.
 
 Checklist per plan:
 
@@ -29,7 +29,7 @@ For each load-bearing decision, run the subset that applies:
 - `<library> security advisory` / check the project's GitHub security tab — non-negotiable for auth, crypto, parsing, and anything touching user input.
 - `site:github.com <library> issues <feature>` — maintainer-stated direction and known footguns.
 
-Always pin the current year or "latest" into queries — undated queries return the same era the model was trained on, which defeats the point.
+Query the installed version first; include dates when freshness matters. Latest-version guidance may not apply to the pinned dependency.
 
 ### Source quality ranking
 
@@ -51,7 +51,7 @@ Every cited source gets a date check. A "best practices" article from before the
 ### When to stop
 
 - Each load-bearing decision has either one primary source confirming/refuting it, or two independent secondary sources agreeing.
-- Two consecutive searches on a decision return nothing newer than what you knew — the world likely didn't move; mark it confirmed-by-absence and move on.
+- If searches yield no useful evidence, mark the decision unverified and move on; absence of results is not confirmation.
 - Diminishing returns: research budget belongs on blockers and majors, not minors. If a finding would be minor either way, don't research it.
 
 ### No web access