build-applicationlisted

# build-application One role, one pack. **There is no master CV and there should not be one** — each CV is assembled on demand from the wiki, which is the persistent raw material. A master CV is a document that is wrong for every application instead of right for one. ## Step 0 — is the posting still open? **Check before building anything.** Roles close. Twenty minutes of work on a dead requisition is twenty minutes gone, and it happens more often than it should. If a fetch fails, say what failed rather than concluding. **A 403 is not evidence of closure**, and a careers site that will not render for an automated browser tells you nothing about the role. If you cannot resolve it, ask the user to check while logged in. 🟢 **If the posting was archived by the radar, re-read it — this is the moment the expensive pass is for:** ```bash python3 tools/radar/refresh.py "vault/postings/<Employer> - <Title>.txt" ``` **The radar is bounded to the delta and never re-reads anything**, so the text and the date behind an assessment are however old the assessment is. Re-reading answers three things at once: | | | |---|---| | **Still readable?** | `GONE` means filled, withdrawn or moved. **Do not build from the archived copy without checking** | | **Has the description moved?** | A band added, a requirement softened. **A salary appearing is called out by name** — it changes the PAY row and the screening-call question | | 🔴 **How old is it really?** | **A listing censors the posting d