docs(documents): add postings/ drop folder for bot-blocked job postings (#187)

Manual fallback for postings that block automated fetches: paste the text into documents/postings/<Job Title>.txt. Gitignored so posting text stays local; README documents the convention as a scratch inbox, with applications/<company>_<role>/job_posting.md remaining the archive.

documents/README.md

@@ -12,6 +12,8 @@ documents/
 ├── linkedin/                    # LinkedIn profile export (PDF)
 ├── diplomas/                    # Degree certificates and transcripts
 ├── references/                  # Reference letters
+├── postings/                    # Raw job posting text, pasted manually for pages Claude can't fetch
+│   └── <Job Title>.txt          # Filename = job title, content = full posting text
 ├── applications/                # Past job applications
 │   └── <company>_<role>/
 │       ├── job_posting.md       # The original job posting (paste as text)
@@ -95,6 +97,16 @@ Reference letters from former managers, supervisors, or collaborators.
 
 ---
 
+## postings/
+
+A drop folder for raw job posting text when Claude can't fetch a page directly (bot-blocked ATS platforms like Lever, Greenhouse behind Cloudflare, JS-heavy SPAs that return empty content, etc.). You open the posting yourself and paste the full text into a `.txt` file here.
+
+**Naming:** File name is the exact job title, e.g. `Front End Engineer - React.js.txt`. Content is the full posting text, pasted as-is.
+
+**Workflow:** Drop the file, then tell Claude in the conversation — it isn't watched automatically. Once a posting has been evaluated or applied to, it can be deleted from here or left as a record; it's a scratch inbox, not an archive (use `applications/<company>_<role>/job_posting.md` for that once you actually apply).
+
+---
+
 ## applications/
 
 A record of past job applications. Each subfolder is one application.