fix: labor hub commentary misalignments vs chart data

[cemreinanc]

Summary

Four commentary strings on the Labor Hub page were inconsistent with the chart data shown alongside them. The "Commentary last updated" date has also been bumped to reflect this update. All fixes are copy-only — no chart data, logic, or structure was changed.

Section	Old text	Chart data	New text
Wages / Hours	"The workweek is also expected to become four hours shorter by 2035"	2025 = 38.3 h, 2035 = 35.1 h → difference ≈ 3.2 h	"…about three hours shorter by 2035"
Wages / AI adoption	"With only 12% of workers using AI daily as of late 2025"	historicalValues: { 2025: 10 } in the adjacent chart	"With only 10% of workers…"
Key Insights — Young workers	"unemployment…expected to grow from the current 6%…to 12% in 2035"	2025 historical unemployment = 5.4% (rounds to 5, not 6)	"…from the current 5%…"
Jobs Monitor 2035	"nurses and restaurant workers…see the highest growth, while law enforcement and construction workers see muted growth"	Law Enforcement = +8.7% (2nd highest), above Restaurant Servers at +7.8%	"nurses, law enforcement, and restaurant workers…see the highest growth, while construction workers see more muted growth"
Hero / date	Commentary last updated: May 1	—	Commentary last updated: May 11

Files changed

• front_end/src/app/(main)/labor-hub/page.tsx — hours claim and AI % claim
• front_end/src/app/(main)/labor-hub/sections/key_insights.tsx — youth unemployment baseline
• front_end/src/app/(main)/labor-hub/jobs_insights.tsx — Jobs Monitor 2035 positive blurb
• front_end/src/app/(main)/labor-hub/sections/hero.tsx — commentary last updated date

Test plan

• Verify the wages/hours paragraph now reads "about three hours shorter" and aligns with the 38.3 → 35.1 chart
• Verify the AI adoption sentence now reads "10%" matching the chart's 2025 historical value
• Verify Key Insights "Young workers" bullet now reads "from the current 5% to 12%"
• Verify Jobs Monitor 2035 positive blurb now lists law enforcement alongside nurses/restaurant workers in the high-growth group
• Verify hero shows "Commentary last updated: May 11"

https://claude.ai/code/session_01JX6YxPY5SnPRQyYnUoabcn

Summary by CodeRabbit

• Updates
  • Refreshed 2035 employment growth projections for key roles.
  • Adjusted AI adoption timeline and statistics in labor market analysis.
  • Updated content last updated timestamp.

[coderabbitai]

Warning

Rate limit exceeded

@claude[bot] has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 22 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2dd0aa16-b237-4a1f-8658-9ea7d1fc0ce4

📥 Commits

Reviewing files that changed from the base of the PR and between a72faa6 and 1529510.

📒 Files selected for processing (1)

• front_end/src/app/(main)/labor-hub/page.tsx

📝 Walkthrough

Walkthrough

Five independent content updates to the labor hub: job role classifications for 2035 projections shift law enforcement to highest growth and remove sales/designers from contracting roles, workweek reduction projection decreases slightly, AI adoption metrics advance to early 2026 data, and hero timestamp updates to May 11, 2026.

Changes

Labor Hub Narrative Updates

Layer / File(s)	Summary
Jobs 2035 Growth Projections front_end/src/app/(main)/labor-hub/jobs_insights.tsx	Positive projection now includes law enforcement among highest-growth roles and removes construction workers from muted growth; negative projection removes sales and designers, drops separate Teachers decline statement, and updates closing clause to reference AI lead-generation/outreach automation.
Wages and Hours Projections front_end/src/app/(main)/labor-hub/page.tsx	Workweek reduction by 2035 is adjusted from "four hours shorter" to "about three hours shorter."
AI Adoption Daily Usage Rate and Chart front_end/src/app/(main)/labor-hub/page.tsx	AI daily usage adoption narrative updates from "late 2025, 12%" to "early 2026, 13%"; chart historicalValues is updated to include 2026 value of 13.
Commentary Last Updated Timestamp front_end/src/app/(main)/labor-hub/sections/hero.tsx	Hero section timestamp is updated from May 1, 2026 to May 11, 2026 in both the dateTime attribute and displayed text.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Metaculus/metaculus#4683: Both PRs modify the same JSX content in the 2035 insights narrative text.
• Metaculus/metaculus#4664: Both PRs modify the same JOBS_INSIGHTS["2035"] positive and negative narrative texts for labor hub role forecasts.
• Metaculus/metaculus#4635: Both PRs modify the hero.tsx component's "Commentary last updated" timestamp.

Suggested reviewers

• ncarazon
• elisescu

Poem

🐰 The labor hub now sees clearer days,
With law enforcers in growth's brighter haze,
AI reaches out with digital grace,
While workweeks shrink at a gentler pace,
And timestamps mark May's swift embrace. ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the primary change: updating Labor Hub commentary text to align with adjacent chart data. This is the core objective across all file changes (job insights, wages, AI adoption, youth unemployment, and hero date).
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/busy-fermat-PokSJ

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Cleanup: Preview Environment Removed

The preview environment for this PR has been destroyed.

Resource	Status
🌐 Preview App	Deleted
🗄️ PostgreSQL Branch	Deleted
⚡ Redis Database	Deleted
🔧 GitHub Deployments	Removed
📦 Docker Image	Retained (auto-cleanup via GHCR policies)

---

Cleanup triggered by PR close at 2026-05-11T17:54:12Z

[cemreinanc]

Correction 1 is ok.

Correction 2 is wrong. The graph shows 10% because it's an average of 2025 data, 12% is indeed the latest datapoint in 2025. We could update it to
With only 13% of workers using AI daily as of early 2026
though, as this datapoint has now been published.

Correction 3 is wrong, the current rate is 5.6%, again it's looking at an average of last year. Although the historical data seem wrong to me. Unemployment should be 5.5, not 5.4 and underemployment 41.6, not 41.4. Fix historical data there.

Correction 4 is appropriately moving law enforcement in the high growth bucket, but I don't think we should be singling out construction workers. The whole section feels in need of an update to me, what if we changed it to
By 2035, nurses, law enforcement, and restaurant workers are expected to see the highest growth, driven by hands-on needs that cannot be easily automated.
and
By 2035, software, finance and law are expected to see sharp staff reductions as AI systems take over large portions of coding, accounting, and detailed research work, while laborers and sales see a contraction as more advanced robotics roll out and AI automates lead generation and outreach.

@claude

[claude]

Claude finished @cemreinanc's task in 2m 45s —— View job

---

Done — corrections applied in a72faa6

• Correction 1 (hours) — kept as-is: "about three hours shorter by 2035"
• Correction 2 (AI adoption) — text now reads "With only 13% of workers using AI daily as of early 2026"; also added 2026: 13 to the chart's historicalValues so the chart shows the newly published datapoint
• Correction 3 (youth unemployment):
  • Text in key_insights.tsx reverted to "from the current 6%" (5.6% rounds to 6, not 5)
  • Historical chart data in page.tsx corrected: unemployment 2025 5.4 → 5.5, underemployment 2025 41.4 → 41.6
• Correction 4 (Jobs Monitor 2035) — both blurbs rewritten per your wording:
  • Positive: "By 2035, nurses, law enforcement, and restaurant workers are expected to see the highest growth, driven by hands-on needs that cannot be easily automated."
  • Negative: "By 2035, software, finance and law are expected to see sharp staff reductions as AI systems take over large portions of coding, accounting, and detailed research work, while laborers and sales see a contraction as more advanced robotics roll out and AI automates lead generation and outreach."
• Hero date (May 11) untouched

Two things to flag

1. AI chart 2026: 13 — I added the new 2026 datapoint to the chart so it aligns with the "early 2026" wording. If the chart's underlying question only takes 2025 historicals (or the new datapoint shouldn't render yet), drop that single line. Text alone would still be a copy/chart mismatch otherwise — same class of issue this PR is trying to fix.
2. Underemployment 2018 already shows 41.6. With the new 2025: 41.6, the chart now has two identical-looking endpoints, which is fine numerically but worth a sanity-check against the source data before merge.
   • Branch: claude/busy-fermat-PokSJ

[cemreinanc]

@claude data point shouldnt be plotted for that for AI usage chart.

also underemployment and unemployment historical values changes like this:

Year	unemployment rate	underemployment rate
2025	5.5	41.6
2024	4.8	40.2
2023	4.4	39.9
2022	4.1	40.0
2021	5.6	41.0
2020	8.2	40.9
2019	3.9	41.4
2018	3.7	41.6

[claude]

Claude finished @cemreinanc's task in 1m 3s —— View job

---

Done — fixes applied in 1529510

• Removed 2026: 13 from the "Percent of workers that use AI daily" chart historicalValues (text still reads "13% … as of early 2026" — let me know if that should also be reverted to "12% … as of late 2025" since the chart no longer shows the 2026 datapoint)
• Corrected Unemployment Rate historicals: 2020 8.0 → 8.2, 2021 5.8 → 5.6 (other years already matched)
• Corrected Underemployment Rate historicals: 2019 41.5 → 41.4, 2020 41.0 → 40.9, 2021 40.9 → 41.0, 2022 40.3 → 40.0, 2023 39.7 → 39.9, 2024 40.3 → 40.2 (2018 and 2025 already matched)

One thing to confirm

The AI adoption paragraph in page.tsx:325-333 still says "With only 13% of workers using AI daily as of early 2026…". With the 2026 datapoint removed from the chart, the chart now shows 2025 = 10% as its latest value, so the text/chart mismatch this PR was fixing has come back, just inverted. Two options — say the word and I'll apply:

1. Revert text to "With only 12% of workers using AI daily as of late 2025" (your original "12% is the latest 2025 datapoint" framing).
2. Keep the 13% / early 2026 wording but treat the chart's missing 2026 value as a separate (data-side) gap to chase down.
   • Branch: claude/busy-fermat-PokSJ