fix: parse prose bodies, redacted dates, role-comma split (#158)

[s-annam]

Summary

Fixes the three defects the chanchal-sharma-sample.pdf referred-resume fixture (a Word/Office template with redacted 20XX placeholder years and glyph-less prose descriptions) surfaced, plus the score-readout render collapse:

• Render — AtsScoreReadout score row no longer collapses when the completeness hint is long; the 3 dimension cards keep full width.
• Parser — redacted years — DATE_ANCHOR/MONTH_YEAR_ANCHOR admit 20XX (and XXXX/#### only when month-anchored), so March 20XX – December 20XX parses as a date range. All 3 roles now parse with correct title/company/dates.
• Parser — prose bodies — bullet-less prose descriptions are captured as the role body (R1 hybrid y-gap split on the PDF path, isProseLine fallback for flat-y DOCX/markdown), and a wrapped paragraph folds into one body unit.
• Parser — R2 — guarded "Role, Company" single-line headers split into title + company (guarded against Acme, Inc and location tails), making all three roles map consistently.
• Scoring — pool per-role descriptions as a fallback bullet source when the accomplishment sections yield no marker bullets (glyph-less templates), mirroring the authed scorer. Specificity/Structure now grade the prose and the bullets render per role. chanchal-sample goes 1→3 roles, overall 24→79.
• cascade.ts counts the experience team field in countExtractedChars so the better field mapping doesn't trip the low-extraction-ratio hard-fail.

5 corpus snapshots re-baked — all improvements or negligible drift (chanchal-sample/-bulleted-skills 0→0.9; single-word-name-mononym 0→0.86; weasyprint-two-column 0→0.64; awesome-cv 0.9→0.89).

Closes #158

Test plan

• npm run typecheck clean
• npm run test green (718 pass)
• npm run lint clean
• Manually verified in npm run dev on the target fixture (3 roles, descriptions render as bullets, score breakdown no longer collapses)

[rohithgollapalli]

Review

Solid parser PR — the entry-block rewrite, the top-origin y-gap math (sectionLineHeight/startsBodyByGap), and the redacted-year regex all check out. One real regression and one minor note.

1. src/lib/heuristics/extract/experience.ts:97-99 — splitRoleComma misattributes a city as the company for "Title, Location" headers (regression)

The guard only checks that the part before the comma looksLikeTitle and the part after isn't a bare legal suffix. It has no guard against a location tail when a title keyword is present before the comma — the documented location-tail defense ("no title keyword before the comma") only covers the "Company … City, ST" shape, not "Title, City".

Trace for Marketing Manager, San Francisco (a common header form):

• before="Marketing Manager" (looksLikeTitle ✓), after="San Francisco" (not a legal suffix) → splits.
• Downstream neither part looksLikeCompany, so the else-branch hits firstLooksTitle && !secondLooksTitle → company = "San Francisco".

Before this PR the line stayed unsplit and company was left undefined — so the change actively introduces a wrong company field (a city). No corpus fixture exercises "Title, City", which is why tests stay green; it's a latent regression. Consider requiring looksLikeCompany(after) (or rejecting a known location shape) before splitting.

Minor — src/lib/score/score.ts:673-680

poolExperienceDescriptions only pools experience[].description, but the comment says it "mirrors the authed scorer," which also pools project (#95) and achievement (#96) descriptions. A glyph-less template whose prose lives only in a projects/achievements section (and whose accomplishment-section pool comes back empty) still grades 0. Low impact — worth a one-line note in the comment if intentional.

🤖 Generated with Claude Code

[s-annam]

Both findings addressed in 8107a8f:

1. splitRoleComma "Title, Location" regression — added a looksLikeLocationTail veto (bare-city set + US_LOCATION_RE/INTL_LOCATION_RE) so "Marketing Manager, San Francisco" and "Product Designer, Austin, TX" no longer split a city into company, while real suffix-less "Role, Company" headers (Nod Publishing, Southridge Video) still split. New experience.role-comma.test.ts covers both directions.
2. Pool-scope comment — documented that poolExperienceDescriptions pools experience descriptions only, not project (Projects dropped as a section — not extracted, bullets leak to "Other" #95) / achievement (Achievements section dropped — demoted to "other" sink, never extracted #96) ones.

Typecheck clean, 721/721 green.