Finish the #680 label rename: audit-report 'Layout flags' heading and CLAUDE.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation, frontend
Research direction
Start with src/lib/pdf/render-audit-report.ts around lines 193 and 268, then inspect CLAUDE.md at line 54 and search for tests pinning these headings. Done means the exported report and repository guidance use the current labels, with grep finding only renamed-from history comments.
Written by the indexing model from the issue text.
Description
Problem
PR #1010 (#680 item 4) renamed pipeline-stage labels on /: "Raw text & flags" → "How your resume was read", "Layout flags" → "Layout warnings". Two places still carry the old names:
- Exported audit report —
src/lib/pdf/render-audit-report.ts:193drawssectionHeading(layout, "Layout flags")(and the section marker comment at:268). A user reads "Layout warnings" on screen, exports the audit report fromExportDialog, and gets a "Layout flags" section: one concept, two names. #1010 scoped this out explicitly (text inside an exported file, not a label on/), which is fair for that PR, but the inconsistency is now real. - Repo guidance — root
CLAUDE.md:54(product overview,/lane) still saysResultDetailhas "Raw text & flagsas a collapsedDisclosuresection". An agent or contributor grepping that label finds only "renamed from" comments.
Fix
render-audit-report.ts: heading → "Layout warnings" (and the marker comment). Check any test pinning the heading text.CLAUDE.md:54: "Raw text & flags" → "How your resume was read".
Acceptance criteria
- Audit-report PDF section heading reads "Layout warnings"
-
CLAUDE.mdnames the current disclosure label -
grep -rn "Raw text & flags\|Layout flags" src CLAUDE.mdreturns only "renamed from" history comments
Provenance: review of #1010.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from offlinecv/OfflineCV
-
fix(heuristics): unit number before a Saint-named city drops "St." from the locationPossibly taken @gaal-agent claimed this 10 days ago. Openbug gaal ux:parsing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Migrate Gaal implement/review/revise to the local gaal watch; keep mechanical workflows on ActionsOpenarchitecture chore github_actions needs-human ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
Parser: achievement year lost on re-import when '· YYYY' wrapped to its own linePossibly taken @gaal-agent claimed this 5 days ago. Openbug gaal ready-for-agent ux:parsing
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Export: auto-bolded metric bullets extract one word per line in stream-order parsers (pypdf/Drive)Possibly taken @gaal-agent claimed this 5 days ago. Openbatch:export-standards bug gaal ready-for-agent ux:edit-export
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
bug duplicate improvement
Difficulty 3/5 Half a day Newbie friendliness 66/100
All issues in offlinecv/OfflineCV
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
iptv-org/iptv#55821 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/wterm#246 ·
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nearform/lastlight#452 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
fix(console): include PARTITIONED BY in generated table DDLPossibly taken @aubdiy claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/polaris-tools#291 ·
Maintainers usually reply within 6 days