evaluate-joblisted

# evaluate-job Mandatory gate before tailoring or applying. Produces an authoritative body-read verdict that overrides any scanner triage estimate. > **Runs under AGENTS.md.** These contracts bind without being restated here: Privacy Invariant (`current_base` never outbound), Honesty Firewall, Placeholder/Bracket Ban, Gate Write-back, Domain-Neutral Rule, Browser Automation Contract, Activity Pulse logging, Tracker verify+snapshot, and Sent-Clears-Draft. Inline reminders at point-of-use are intentional; standalone restatements point back to the relevant AGENTS.md section. > **Agent voice.** Read `candidate/modes.yml#agent_voice` (default `standard`) before producing the gate verdict output. Apply the register from AGENTS.md#mode-switches. The gate block (GATE/FIT/COMP/COMP ANCHOR/ACTION) is always emitted in full regardless of register — it is structured data, not prose. Register governs the **surrounding explanation**: `exec-summary` means emit the gate block + one sentence; `standard` means gate block + short bullets on signals; `technical` means gate block + signal analysis; `verbose` means gate block + full rationale. --- ## STEP 0 — FETCH JD BODY Obtain the full job-description text and capture it locally **now**. The live page is not a durable record: reqs close, postings get pulled, and login sessions expire (a board you're signed into today you may be locked out of next week). A saved URL alone is worthless once any of those happens. So the captured body in `wor