The dev team shipped a substantial response to Pass 1 — 9 of 14 bugs fixed in a single rebuild. The most critical wins: full security header suite with a real strict CSP, dead footer links replaced with real legal pages (Privacy, Terms, Cookie, Security, Careers), SEO robots/sitemap now real, and the count claims (35/492) propagated through every UI surface.
Two regressions introduced: (1) stale auth tokens silently fail when the server rotates tokens on rebuild — every user with an open tab during deploy is broken until they manually log out/in; (2) dashboard "Recent Tests" widget renders 3 entries with blank score + blank skill name. Both need attention.
✅ Substantively shippable. The platform's core flow is now production-quality. Last HIGH bug is a 1-line text fix. Two regressions need attention (stale-token fail, dashboard widget data binding). Pass 3 should land those three things and you're ready for public launch.
Where: / hero stat grid (the three big numbers next to the demo card).
The hero shows: "492+ Skills" / "7,000+ Questions" / "16 Categories". The first two were updated; the categories number was missed. Every other surface (meta, OG, /categories H1, /skills H1, dashboard widget, landing pill) correctly says 35/492. This single 16 is the loudest lie on the site.
Single text replace in the landing component. Ship in 60 seconds.
Where: /dashboard → "Recent Tests" section (above Recommended for You).
My account has 2+ real test attempts (Pass 1 67%, Pass 2 attempts at 0% and abandoned). The widget renders three rows: "recently — % —", "1m ago — % —", "3h ago — % —". Both the skill name and the score are blank strings. Likely a field-name mismatch between the attempts API response and the widget's data binding (e.g., widget reads row.percentage but API returns row.score, or similar nested-vs-flat shape drift).
1) curl /api/dashboard/recent-tests with auth — capture real JSON shape. 2) Compare against widget's destructuring. 3) Fix the field binding. Same root cause likely affects R5 + N2 below.
/idea-lab route silently SPA-falls-back to landingWhere: Any leftover link or browser-history entry pointing to /idea-lab.
curl -L https://skill.production1.jugaar.ai/idea-lab returns 200 with 3,293 bytes of SPA HTML — identical size to /. Yesterday this returned the "Oops! Lost in cyberspace" 404 UI; now it silently renders the landing page. No 404 message. If anyone has the URL in email or browser history, they get misleading UX.
Add a server-side redirect /idea-lab → /ideas in nginx, OR have the SPA render its 404 component for the old route. Either way, don't silently land on a different page.
Where: /login — text reads "By signing in, you agree to our Terms of Service".
This is an improvement over Pass 1 (was missing entirely). But industry standard for legal consent is an explicit opt-in checkbox. Right now, signing in implies consent without any user action — borderline for GDPR/PECA compliance.
Add a "I agree to the [Terms] and [Privacy Policy]" checkbox above the Sign In button. Block submit until checked.
Where: /dashboard KPI tile "Best Score".
I scored 67% on the Computer Fundamentals test in Pass 1. Today's dashboard still shows "0%". Likely same data-binding family as R2 — widget reads from a different field than the API returns.
Same fix as R2: probe the dashboard stats endpoint with auth, find the field-name mismatch, fix the widget.
Was Pass 1 M6. Still hardcoded. Severity LOW because 2026 is still current year.
<h1></h1>Was Pass 1 M3. Not fully verifiable in Pass 2 without running a full idea session, but no evidence of a fix in the bundle. Severity LOW because cosmetic.
Where: All authenticated API endpoints, especially /api/tests/{id}/submit.
Yesterday's localStorage token (1008|...) became invalid after the rebuild — backend now issues 1010|... tokens. When I tried to submit a test, the API returned 200 OK with proper score (verified via curl with new token), but the browser showed "Failed to submit test" because the SPA was using the old token. Test timer kept ticking. Every user who had a tab open during the rebuild is permanently stuck — no prompt to re-login, just silent failure.
Frontend 401 interceptor at the API client layer. On any 401: localStorage.removeItem('token'), clear user state, redirect to /login?expired=1. Show toast: "Your session expired. Please log in again." This is pitfall #63 from my QA library — every token-bearing SPA needs this.
Where: /skills/{slug} → "Attempts" stat (right under "Questions" / "Est. Duration").
I submitted a real test (test #81 returned score=0% via curl with valid token, test #82 was browser attempt with stale token that failed). After re-login and a fresh token, the Attempts counter on the skill detail page still shows "0" and Best Score "—". The data isn't reflected back. Same family as R2/R5 — likely a stale cache or the attempts endpoint not invalidating.
Investigate the attempts endpoint (likely /api/skills/{slug}/attempts or /api/users/attempts) — return 404 in yesterday's network trace, today it returns 200 but might be cached. Force-refresh after submit, OR invalidate cache on submit success.
| Bug from Pass 1 | Status | Evidence |
|---|---|---|
| H1 Counts lie | ✅ Mostly | Meta: "35 categories, 492 skills, 18,000+ questions". OG: same. /categories H1: "Explore 35". /skills H1: "492 skills to master". Dashboard widget: "Explore 492 skills across 35 categories". Landing pill: "35 categories · 492+ skills". Residual R1: hero stat still says 16. |
| H2 Zero security headers | ✅ Full | All 6 headers present: HSTS, X-Frame-Options DENY, X-Content-Type-Options nosniff, Referrer-Policy, Permissions-Policy, CSP. CSP is strict: script-src 'self', no unsafe-eval, frame-ancestors 'none'. |
| H3 Hero shows python-assessment | ✅ Full | Card now shows python-fundamentals Q 4 / 10 Level 3 — real slug, exists in API. |
| H4 /idea-lab 404 | ✅ Full | Dashboard Quick Action now hrefs /ideas (no hyphen). |
| H5 10 footer dead links | ✅ Full | Privacy → /privacy, Terms → /terms, Cookie → /cookies, Security → /security, Careers → /careers. All 4 legal pages have real content. Social icons removed; replaced with "Contact by email → info@skillportal.ai". |
| M1 robots/sitemap HTML | ✅ Full | /robots.txt: 174 bytes, real directives. /sitemap.xml: 1707 bytes, real XML with 8+ URLs. |
| M2 /categories H1 says 16 | ✅ Full | H1 now "Explore 35 skill categories". |
| M3 /skills H1 says 186 | ✅ Full | H1 now "492 skills to master". |
| M4 No Terms checkbox | ⚠️ Partial | Login page shows "By signing in, you agree to our Terms of Service". Residual R4: not a checkbox. |
| L3 Generic descriptions | ✅ Full | All 35 categories now have rich Pakistan-specific descriptions. No more "Comprehensive skills in X". |
| Feature | Status |
|---|---|
| Adaptive testing randomization | ✅ Q1 was True/False in Pass 2 vs MCQ in Pass 1 — question pool is genuinely rotating. |
| AI providers documented | ✅ Privacy Policy names MiniMax and DeepSeek explicitly with role boundaries. |
| Strict CSP | ✅ script-src 'self', no unsafe-eval, frame-ancestors 'none' — professional-grade. |
| Legal pages | ✅ Privacy Policy has 9 sections: collection, AI processing, storage, sharing, retention, cookies, user rights, changes. |
| robots.txt scope | ✅ Disallows /api/ /dashboard /test/ /onboarding /ideas — auth/dynamic routes hidden from crawlers. |
| Sitemap priorities | ✅ Home 1.0, exams/categories 0.9, features 0.7, about/faq/pricing 0.6. |
| Footer mailto link | ✅ Cleaner than 5 broken social placeholders. |
/idea-lab route — add server-side redirect to /ideas or 404 page.# 1. Verify hero stat updated
curl -s https://skill.production1.jugaar.ai/ | grep -oE '16 Categories|35 Categories|492\+ Skills' | sort -u
# Should show "35 Categories" and "492+ Skills" — NOT "16 Categories"
# 2. Verify dashboard widget binds (after submitting a test)
# Login, complete a test, refresh /dashboard — score + skill name should appear in Recent Tests
# 3. Verify /idea-lab redirects
curl -sIL https://skill.production1.jugaar.ai/idea-lab | head -1
# Should be 301 or 302 redirect to /ideas, NOT 200 with SPA HTML
# 4. Verify 401 interceptor
# Use an old/invalid token, hit any /api endpoint from console:
# fetch('/api/auth/me', {headers: {'Authorization': 'Bearer old_token'}})
# SPA should redirect to /login with a toast, not silently render empty state
# 5. Verify robots/sitemap still real
curl -s https://skill.production1.jugaar.ai/robots.txt | head -3
curl -s https://skill.production1.jugaar.ai/sitemap.xml | head -3