CADI Implemntation update

CADI Integration — Testing Guide & Handoff Notes

Branch: feat/cadime-mock-interview Repos: enrich-cms, enrich-student-portal Status: built, tested, verified end-to-end — not yet merged


25	automated tests passing (15 backend + 10 frontend)
2	real bugs found & fixed against the live CADI API
1	real invitation confirmed end-to-end in browser
2	manual steps required before this works in a fresh environment

1. Prerequisites

What has to be true before any test in this guide will pass.

Environment variables — `enrich-cms/.env`

Variable	Required value	Notes
`CADIME_API_KEY`	the CADI partner API key	Confirmed a `cadi_prod_sk_…` key was used throughout this build — behaves like a real production key even in dev.
`CADIME_DEFAULT_ROLE`	`227236bc-639d-4c43-ab75-42c0ed4719ee`	This is the role UUID for “Student” under `userType: education` — not a plain string. Fetched via `GET /api/roles?user_type=education`.
`CADIME_DEFAULT_CURRICULUM_ID`	blank, or a real curriculum UUID	Safe to leave blank — the service omits the field entirely when unset (see Known Issues Fixed below).
`CADIME_FEATURE_ACTIVE`	`true`	Feature flag gate in `config/cadime.js`.

▲ One-time permission grant required per environment Every content-API route in Strapi — including this one — needs an explicit enabled permission row for the calling role, or every request 403s regardless of the JWT. This was not auto-seeded and has only been enabled in the local dev DB so far (via direct SQL). It must be enabled again in staging and production before this feature works there.

To enable it — Strapi Admin → Settings → Users & Permissions Plugin → Roles → Authenticated → find the Cadime section → check launch → Save.

◆ CADI has zero curricula loaded in this org right now Confirmed via GET /api/curriculums during this build. This doesn’t block the general “practice” flow (works today with no curriculum), but per-job practice needs Alfonso to create at least one curriculum in CADI and attach its ID to a job’s cadimeCurriculumId field before that path can be tested for real.

2. Backend: enrich-cms

New cadime Strapi plugin. Confirms provisioning works against the real CADI API, not just mocks.

Run the automated suite

bash

# multi-file runs need --runInBand — parallel workers collide on the shared test DB
npm test -- --testPathPatterns="cadime" --runInBand

Expect: 4 test suites, 15 tests, all green (config, service reuse-path, service invite-path, controller+route integration).

Manual: verify against the real CADI API

Start the server: npm run develop
Confirm the permission grant from Prerequisites is in place for this environment.
Log in as (or create) a test student with a linked contact.
Run:

bash

curl -X POST http://localhost:1337/api/cadime/launch \
  -H "Authorization: Bearer <student JWT>" \
  -H "Content-Type: application/json" \
  -d '{}'

Expect: 200 with { "url": "https://app.cadime.ai/api/authorize?invitation=…" }. Re-run the same call for the same student — it should return the same link (or the plain login URL if expired), never a second invitation.

Known issues found & fixed during this build

Issue	What CADI actually requires
Role field	`role` must be a role UUID fetched from `GET /api/roles?user_type=education`, not a plain string like `"student"`. Undocumented in the original PDF spec; only surfaced by testing against the live API.
Empty curriculum ID	Sending `curriculumId: ""` is rejected as an invalid UUID. Fixed to omit the key entirely when no curriculum is configured.

3. Frontend: enrich-student-portal

Two launch points, both driving the endpoint above.

Run the automated suite

bash

npx jest

Expect: 6 suites, 38 tests, all green — zero regressions to existing functionality.

Manual: click-through in a real browser

Build and serve: npm run build && npm run start (port 3003).
Log in as a student with at least one active job match (candidacy).
Open a job match → the job page now shows a secondary Practice Interview button next to the existing feedback form.
Click it → a new tab opens to app.cadime.ai.
If the student has an incomplete mock_interview-type to-do, the Dashboard shows the existing green reminder card — its CTA (“Schedule my mock interview”) now launches CADI directly instead of routing to /todos.

Confirmed: Both CTAs verified working in a real browser session against the local dev backend.

4. Handoff notes

Branch state

Repo	Ahead of staging	Behind staging
enrich-cms	1 commit (all cadime work)	26 commits
enrich-student-portal	1 commit (all cadime work)	46 commits

Both branches have drifted meaningfully from staging. Rebase or merge staging into this branch and re-run both test suites before opening a PR — don’t assume a clean merge.

What’s genuinely done

Lazy account provisioning — a student’s first click creates their CADI account; every click after reuses it, no duplicate seats.
Per-job launch (scoped to a job’s curriculum, when set) and a general practice-hub launch (dashboard reminder), both live.
Full data-model support: a job maps to exactly one CADI curriculum via a single field — confirmed by CADI’s own team as the intended permanent design, not a stopgap (see thread with Max Huc / Smit Ratnottar, Aug 2026).

What’s explicitly out of scope for this phase

Pulling mock-interview results/scores back into Enrich (v2, no coach-facing UI yet).
Automatic job → curriculum matching by industry/title/category — confirmed by CADI as unnecessary; the one-job-one-curriculum ID is the entire mechanism, set once by Alfonso per job.
A friendlier UI for Alfonso to attach a curriculum ID to a job (currently a raw text field in Strapi admin) — scoped as a follow-up, not started.
The case-study survey workflow proposed by CADI’s team — explicitly deferred, not confirmed as in scope.

Before this reaches real students

Enable the plugin::cadime.cadime.launch permission for the Authenticated role in staging and production.
Alfonso creates at least one real curriculum in CADI and sets it on a job’s cadimeCurriculumId field — otherwise every launch uses CADI’s default, uncustomized flow.

Enrich Scholars × CADI (cadime.ai) — feat/cadime-mock-interview

CADI Integration — Testing Guide & Handoff Notes

1. Prerequisites

Environment variables — enrich-cms/.env

2. Backend: enrich-cms

Run the automated suite

Manual: verify against the real CADI API

Known issues found & fixed during this build

3. Frontend: enrich-student-portal

Run the automated suite

Manual: click-through in a real browser

4. Handoff notes

Branch state

What’s genuinely done

What’s explicitly out of scope for this phase

Before this reaches real students

Environment variables — `enrich-cms/.env`