Linter Fix (clang-format): The second force-push was made to wrap a long string literal in src/main.c that exceeded the maximum line length check, which was causing the CI formatting job (lint-format) to fail. No logic changes were introduced.

Hey @DeusData shall i close the PR or should i wait for you to merge it first?

Hey @sahil-mangla, a bit of patience please. At the moment there is a lot of "background work" happening. Coming back to you ASAP :)

Thanks @sahil-mangla — the UI error-banner half is good and we'd like it.

The blocker is the src/main.c change: it removes the CBM_EMBEDDED_FILE_COUNT > 0 guard, so the HTTP server now starts whenever --ui is set, even in the standard binary with no embedded assets. The server binds loopback only (so it's local-only, not a network exposure), but it still turns a documented no-op into a live listener — a behavior-contract change.

Could you split this PR: keep the UI error-handling, and gate the always-start-server behavior behind an explicit opt-in (e.g. a --dev-api flag) rather than removing the asset guard? The UI half can merge as soon as it's separated. 🙏

@DeusData
Thanks for the review and for clarifying the concern.

I agree that removing the CBM_EMBEDDED_FILE_COUNT > 0 guard changes the existing behavior contract for --ui, even if the listener is loopback-only.

I’ll split the changes and update this PR to keep only the UI error-handling improvements. I’ll revert the src/main.c change from this PR and keep the development-server behavior as a separate follow-up, potentially behind an explicit opt-in flag such as --dev-api.

Thanks @sahil-mangla — the StatsTab.tsx error-banner fix itself is good and we'd like it. But the PR currently contains 709 changed files / +3022 lines: ~706 are graph-ui/.npm-cache-local/ npm-cache blobs that got committed, plus scratch/generate_stress_repo.py (which is gitignored and shouldn't be pushed) and some unrelated package-lock.json churn.

Could you reduce this to just the StatsTab.tsx change — remove the .npm-cache-local/ tree and the scratch script, add graph-ui/.npm-cache-local/ to .gitignore so it can't recur, and drop the lock-file churn? Once it's down to the single file, it's good to go. 🙏

@DeusData Can you check and verify if any other changes or something looks off to you i will fix them right away or is it all good.

Thanks @sahil-mangla — the frontend fix is a real bug: StatsTab.tsx treated an error status as "done" (data.every(j => j.status !== "indexing")), silently dismissing failures, and splitting "still indexing" from "has errors" is the right fix.

Two things before it lands:

1. Title/diff mismatch: the title says "...and enable dev mode API hosting", but the diff only touches graph-ui/src/components/StatsTab.tsx and .gitignore — there's no backend/dev-mode/API-hosting change here. Please update the title to match what the PR actually does (the error-handling fix + the npm-cache .gitignore entry) so the merge commit doesn't record a feature that isn't present. If the hosting change was meant to be included, it's missing from the diff.
2. Test: a small vitest/RTL test for the error path (status error renders the banner and doesn't call onDone) would lock this in.

The .gitignore npm-cache line is unrelated to the fix — fine to keep, just noting. Thanks!