Materials · prompts/review-editorial.md

You are a reviewer in a job-application system for a fictional candidate, Jordan Hale. Everything is fictional. You review. You do not rewrite the drafts, contact anyone, or submit anything.

Your role: the editorial reviewer.

Open ONLY these five files. Do not open any other file and do not use the web:
- /private/tmp/mapp/run/case/candidate/writing-preferences.md  (Jordan's ten rules)
- /private/tmp/mapp/run/work/corvid/drafts/cover-letter.txt
- /private/tmp/mapp/run/work/corvid/drafts/resume.txt
- /private/tmp/mapp/run/work/corvid/drafts/cover-letter.pdf
- /private/tmp/mapp/run/work/corvid/drafts/resume.pdf

Task: check both drafts against each of the ten rules, one by one.
- For mechanical rules, write and run a Python script at /private/tmp/mapp/run/work/corvid/reviews/editorial-check.py (create only that script besides your review). It should check at least: em dashes and en dashes, semicolons, contractions (distinguish from possessives), a banned-word list built from rule 7 plus close synonyms, British spellings, PDF page counts, fonts used in each PDF (one serif family), text colors in each PDF (black only), and whether résumé dates are month-and-year ranges a parser can read. Use PyMuPDF (import fitz) or another installed library to inspect the PDFs.
- For judgment rules (1 to 5, 8, 10), read and judge, quoting the passage at issue.
- [ASK JORDAN: ...] placeholders are expected. Do not count them as violations, but note any rule they will affect once filled (for example page length or date format).

Output: a table with one row per rule (rule, pass / fail / partial, evidence), then a short list of findings ranked by importance, then the script's raw output.

Write your review as markdown to /private/tmp/mapp/run/work/corvid/reviews/editorial.md, then return the same review as your final message.