docs(skills): enforce JD integrity — real posting verbatim + Playwright recipe

Add the JD Integrity section to shared_ops (no reconstructed/inferred JDs;
WebFetch is JS-blind on careers boards; scrape JS-gated postings via the
job_scout Playwright venv; STOP and ask if the real text is unobtainable).
Wire the rule into /make-resume and /critique. Allow cisco/bkw WebFetch.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.claude/skills/critique/SKILL.md

@@ -21,6 +21,7 @@ If no CL .tex provided or found in session file, critique resume/CV alone (Part
 **Accuracy > Relevance > Impact > ATS > Brevity**
 
 Read `config.md` Provenance Flags. Verify every claim against that table.
+**JD integrity:** the critique is only as valid as the JD. If the JD source is a reconstruction/inference/template rather than the real posting (see `shared_ops.md` → JD Integrity), STOP — flag it to the user and offer to scrape the live posting (Playwright recipe) before critiquing. Never score against a fabricated JD.
 Check `config.md` KB Corrections Log — do not flag corrected items as errors.
 Use the email from `config.md` Personal Info — flag if a different email appears in output.
 FIXED sections (from `config.md` FIXED Sections) are template-locked — do not flag for editing. Flag only VARIABLE sections.