fix(freehire-search): keep the salary period so a yearly figure isn't read as monthly (#504)

formatSalary printed only the currency and amounts, although freehire's
enrichment records the pay period. `detail software-developer-trainee-codifi-fra635ux`
printed `INR 300000–300000` while the API returns `salary_period: "year"`
for that posting, so a yearly salary screened against a monthly figure
read as twelve times its real monthly value.

Append the period when freehire records one (`INR 300000–300000/year`,
`INR 12000/month`); a record without a period prints exactly as before.
Two new parsing.test.ts cases pin it; both fail on the old formatter.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Sahil Kumar SahuandClaude Opus 5.5 authored and GitHub committed 2026-09-29 20:22:04 +02:00
1 parent 9bc71de5f8
commit 9187f894a5
4 files changed
+33 -4

No files matched your search

+10
View File
@@ -105,6 +105,16 @@ per-file diff commands.
### Fixed
- **`freehire-search detail` keeps the salary period, so a yearly figure no longer reads as
monthly** (`.agents/skills/freehire-search/cli/src/helpers.ts`, `SKILL.md`) - `formatSalary`
printed only the currency and amounts, although freehire's enrichment records the period:
`detail software-developer-trainee-codifi-fra635ux` printed `INR 300000–300000` while the
API returns `salary_period: "year"` for that posting, so anyone screening pay against a
monthly figure read a yearly salary as a monthly one, twelve times its real monthly value.
The period is now appended when freehire records one (`INR 300000–300000/year`,
`INR 12000/month`); a record without a period prints exactly as before. Pinned by two new
`parsing.test.ts` cases, both failing on the old formatter.
- **`robots_check` decodes curl output as UTF-8, so a non-ASCII response no longer reads as
UNCONFIRMED on Windows** (`tools/robots_check.py`, `tests/test_robots_check.py`) -
`_fetch()` ran curl with `text=True` and no encoding, so Python decoded the response with