applies-to-tagging: clarify minor-level tagging and same-minor consolidation

[florent-leborgne]

Summary

Makes two applies_to conventions explicit in the applies-to-tagging skill, after a session where the agent tagged a patch release (stack: ga 9.4.2) and created a redundant parallel bullet for a minor that an existing bullet already covered.

• Tag at the minor level by default. Even when a feature ships in a patch release (for example 9.4.2), tag it at the minor (stack: ga 9.4). Badges only display Major.Minor, so a patch-level tag adds no reader-visible precision. Reserve patch precision for plain-text prose, and only when critical.
• Consolidate with content that already covers the version. When the page already has a bullet, section, or block covering the same minor, fold the addition into that existing structure instead of creating a parallel same-minor tag. One minor, one place.

Changes

• New guidance bullet under make version intent explicit.
• New Consolidate with content that already covers the version guideline.
• New validation rule (Integrate Skill Creator evaluation framework #12) flagging patch-level tags and the redundant same-minor bullets they create.
• New eval (Add skill quality review agentic workflow #11) exercising the 9.4.2-into-existing-9.4-bullet scenario.
• Minor version bump 1.2.1 → 1.3.0.

Validated evals.json parses.