[dckaratas]

Six lessons from two weeks of runs on Turkish job boards, one commit each.

• --json accepts a UTF-8 byte-order mark. Windows PowerShell 5.1 writes one, and every add/move from that shell was refused. A test covers it.
• Talentics (new ATS file): no account, autofill from the CV, but the parsed work history comes back with every month as January.
• Recruitcrafts: the email is checked only on Continue, so an address that already has an account turns a filled form into a hand-off. A bank careers site with a password wall goes in the identify table too.
• Peoplise: the first step differs per tenant; read each consent label before you decide to hand it off.
• Kariyer.net: replies show only at /tum-basvurular, never by mail; a mandatory question can have no truthful option; the cover-letter step's mechanics.
• freehire: tr.whatjobs.com returns NXDOMAIN, so whatjobs records are leads only.

tailor_cv is taken out, per review: the first commit is reverted by the last one, together with the two sentences that pointed to it, so nothing about it lands. It will come back as a proposal issue first.

A leak scan against the candidate profile and the email, phone and postcode patterns found nothing. node --test tests/seekter.test.mjs: 106 pass.

🤖 Generated with Claude Code

[selfishprimate]

Thanks for this one, and for the measurements; most of it is exactly what reference/ is for.

Ready to merge as they are

• --json accepting the UTF-8 byte-order mark, with its test. A real bug for anyone on Windows PowerShell 5.1.
• Talentics (new ATS file), Recruitcrafts, Peoplise per-tenant first step, the Kariyer.net notes (replies only at /tum-basvurular, the question with no truthful option, the cover-letter step), the Garanti BBVA account wall, and the whatjobs NXDOMAIN note. Measured, dated and person-independent.

tailor_cv needs a proposal issue first
tailor_cv is a new feature, and it changes how /seekter-run behaves (§4). CONTRIBUTING asks for a proposal issue before anything of that size, and before a change to a skill's behaviour: see "Propose before you build", and the proposal template under New issue. Please open one so we can agree on the direction before it lands. A few points the discussion needs to settle:

1. It bypasses the resume engine. Resumes are kept as data in resume.json, printed by scripts/resume.mjs, and held to the profile by validate. The tailored CV is hand-written HTML printed with Chrome, and the only number check is a manual look at the fact bank. Neither resume.mjs validate nor claims.mjs runs on it, so the kit's guarantee that no invented number reaches a form doesn't hold on this path. If tailoring goes in, it should be a per-posting variant of resume.json, printed and validated by resume.mjs like the other resume types.
2. It adds an outside dependency. The verification step relies on pdftotext (poppler), which isn't installed by default on macOS and goes against the kit's Node-only, no-packages rule.
3. It contradicts the documented behaviour. The Resumes docs say Seekter does not tailor resumes per posting, so this is a product decision rather than a reference note.
4. Small one: the record step says to put the file name in --notes; records are now written through --json, so it's the notes field.

Could you split this PR? Everything except tailor_cv (the skill line, tailored-cv.md, the settings key and its check, and the Kariyer.net sentence that points to it) can be merged now, and tailoring can come back as its own PR once the proposal issue has settled the approach.

[selfishprimate]

Thanks for splitting it. The remaining changes (the BOM fix with its test, and the Talentics, Recruitcrafts, Peoplise, Kariyer.net and whatjobs notes) are good to go. Tailoring can come back through a proposal issue.