Skip to content

Verification Report

This report audits the quantitative and narrative claims in this subtree against the actual repo state.

Summary

Category Count
Claims verified ✅ 11
Claims with drift 🔧 0
Claims requiring follow-up ⚠ 3

A. Verified claims

Claim Where claimed How verified
Repo has 9 HTTP endpoints (all GET, all under /dashboard) API-inventory.md grep -cE "router\.(get\|post\|put\|delete)\(" routes/index.js → 9; grep -oE … shows all 9 are router.get
routes/index.js is 974 lines architecture-overview.md wc -l routes/index.js → 974
services/job_account_insights.js is 528 lines architecture-overview.md wc -l services/job_account_insights.js → 528
services/job_growth_insights.js is 40 lines architecture-overview.md wc -l services/job_growth_insights.js → 40
services/job_post_insights.js is 520 lines architecture-overview.md wc -l services/job_post_insights.js → 520
Production copy at someli-api/dashboard/routes/index.js has an additional /leaderboard/:pId endpoint API-inventory.md, CODE-OVERLAP-MATRIX.md diff routes/index.js ../someli-api/dashboard/routes/index.js \| head -30 shows the leaderboard handler is added in the production copy
server.js is 17 lines architecture-overview.md wc -l server.js → 17
conf.js is 8 lines architecture-overview.md wc -l conf.js → 8
conf.js is not required by server.js in standalone mode configuration.md grep "conf" server.js returns no match
mock/ contains 5 files architecture-overview.md find mock -type f returns 5 paths
10 npm dependencies; 0 devDependencies dependencies-inventory.md jq '.dependencies \| length' package.json → 10; jq '.devDependencies' package.json → null

B. Drifted claims

None.

C. Follow-up needed

Item Why deferred
[VERIFY-1] Are services/job_*_insights.js byte-identical to their counterparts in someli-api/dashboard/services/? Verified one-paragraph diff exists; full file diff not produced for this report. Spot-check shows the public function shape matches.
[VERIFY-2] Production HTTP path of these endpoints The CLAUDE.md for someli-api says dashboard is mounted at /auth. If the dashboard router itself mounts at /dashboard, the full path would be /auth/dashboard/getAccountInsights/.... nginx config not inspected.
[VERIFY-3] Does someli-platform consume mock responses during local dev, or always hit a real someli-api? Need to look at the FE's dev-time API_URL and the team's actual workflow.

D. Notes for next re-verification

When this subtree is re-verified (recommend every 6 months):

  1. Re-run diff -rq someli-dashboard-be someli-api/dashboard to detect new drift.
  2. Re-count endpoints and line counts; update the "At a glance" section of README.md if changed.
  3. Re-check package.json dependency list against actual require() usage; remove anything that becomes unused.
  4. Confirm the runtime branch in routes/index.js still uses NODE_ENV === "development" as the discriminator (could change to a more explicit env var).