feat(ui): integrate v0/Lovable export + proxy API routes

[ctol3r]

• Integrates v0/Lovable pages/components
• Adds Next.js API proxy to backend (:4000) eliminating CORS
• Scrubs hard-coded localhost API URLs → uses /api/*
• Frontend build succeeds

[chatgpt-codex-connector]

💡 Codex Review

chai-vc-platform/frontend/pages/api/_proxy.ts

Lines 13 to 21 in 56a778b

	const pathParam = req.query.path;
	const suffix = Array.isArray(pathParam)
	? pathParam.join('/')
	: typeof pathParam === 'string'
	? pathParam
	: '';
	const targetUrl = `${BACKEND}${suffix ? (suffix.startsWith('/') ? suffix : `/${suffix}`) : ''}`;

[P0] Preserve API path when proxying to backend

The new proxy only builds the upstream URL from req.query.path, so the leading route segments (such as issuer, verifier, healthz, etc.) are never forwarded. For flat routes like /api/healthz path is undefined, and for /api/issuer/credential it contains only credential, meaning the request is forwarded to http://localhost:4000/credential instead of /issuer/credential. Every frontend call through these API pages will therefore hit the wrong backend endpoint and return 404s, defeating the purpose of the proxy.

---

chai-vc-platform/src/blockchain/blockchain_integration.ts

Lines 1 to 2 in 56a778b

	export * from '../../src/blockchain/blockchain_integration';
	export { default } from '../../src/blockchain/blockchain_integration';

[P1] Fix self-referential blockchain module export

The new src/blockchain/blockchain_integration.ts re-exports from '../../src/blockchain/blockchain_integration', which resolves back to the same file. As a result the module exposes no checkCredentialStatus implementation, so resolveCheckFn in src/controllers/verifier_controller.ts always falls back to the hard‑coded 'valid' stub. In non-test environments this means credential status checks will never call the real backend integration and every credential will be reported as valid.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback