Version-condition the washr 1.0.1 caveats, retire after two clean releases on washr >= 1.0.2

[larnsce]

Successor to #23 (closed: it added the workarounds; this issue retires them). Identified as the top finding of the 2026-07-12 cross-repo coherence review (openwashdata/washr, dev/review-2026-07/cross-repo-coherence.md on branch claude/washr-review-premortem-5idwlc): washr v1.0.2 fixes the root causes of all four caveats (washr #57, #58, #59, #60 plus #63, #64), but nothing open in either repo owned removing the workarounds, which would have silently defeated the patch's purpose.

Do NOT delete the caveats outright (premortem R6 in the washr review: CRAN binary lag, cached libraries, and renv locks mean old washr keeps resolving downstream after the release). Version-condition them instead.

Tasks:

• skills/create-release/SKILL.md, skills/add-doi/SKILL.md, skills/pkgreview-core/references/standards.md: wrap each washr 1.0.1 caveat in a version condition: run packageVersion("washr") first; apply the caveat steps only when < 1.0.2, skip them when >= 1.0.2 (on a fixed washr the old surgery is harmful: it deletes correct DOI badges and "restores" fields that were never stripped)
• checklists/metadata.md: same conditioning where caveats appear
• Bump skills/pkgreview-core/VERSION and record the change in docs/checklist-reconciliation.md (repo rules 1 and 3); if this lands in the same window as the v1.1.0 standard release (Release v1.1.0: gate run, standards update, version bump, tag #32), fold it into that release so standards.md is edited once and the standard bumps once
• Verify against fixtures/pkgreviewtest with both washr versions if practical, at minimum with the installed one
• Remove the caveat text entirely only after two consecutive clean downstream releases on washr >= 1.0.2

Timing: blocked on washr v1.0.2 reaching CRAN (openwashdata/washr#66). Implementation of both plans starts September 2026; recommended sequence is the washr release branch first, this issue folded into #32 during the CRAN wait.

[larnsce]

Unblocked: washr 1.0.2 was accepted on CRAN and v1.0.2 is tagged at the tip of release/1.0.2 (openwashdata/washr#66 is closed).

The version-conditioning work here can start. Per the body above, if it lands in the same window as the v1.1.0 standard release (#32), fold it into that release so standards.md is edited once. The two-clean-releases retirement clock counts downstream releases made with washr >= 1.0.2.

[larnsce]

Superseded by #57: with washr 1.1.0 on CRAN, v1.5.0 (on dev, be5cb26 and 5ee498d) floors both release skills at washr >= 1.1.0 with a preflight and deletes every caveat instead of version-conditioning it. Close on the v1.5.0 release merge (#68).

[larnsce]

Superseded by #57 and shipped in pkgreview v1.5.0 (PR #70, merge be4d23c, tag v1.5.0): both release skills floor washr at 1.1.0 with a preflight and carry no caveat text.