fix: surface server JSON error message on failed server connection

[Asm3r96]

Summary

Fixes #158

• server-connection.ts: On non-ok responses, parse the JSON body and use body.error as the error message, falling back to HTTP status text if parsing fails.
• api.ts: Expand the 404 error message to also hint at restarting the server after running gitnexus analyze.

Problem

When gitnexus serve has no indexed repo, GET /api/repo returns a 404 with a helpful JSON body but the client was discarding it, showing the user a cryptic Server returned 404: Not Found instead of the actionable message.

Result

User now sees: No repository indexed. Run gitnexus analyze in your project directory first, then restart the server.

[vercel]

@Asm3r96 is attempting to deploy a commit to the NexusCore Team on Vercel.

A member of the Team first needs to authorize it.

[magyargergo]

⚠️ Upcoming Prettier formatting — rebase instructions

PR #563 adds Prettier as the code formatter for the repo. When it merges, the bulk format commit will touch ~350 files (style-only: whitespace, quotes, trailing commas). Your branch will likely conflict.

After #563 merges, rebase your branch:

git fetch origin
git checkout <your-branch>
git rebase origin/main

# Conflicts will be formatting-only — accept your version:
git checkout --theirs .
git add .
git rebase --continue

# Then re-format your branch to match the new style:
npx prettier --write .
git add -A
git commit -m "style: apply prettier formatting"
git push --force-with-lease

New setup step: Run npm install at the repo root (not just in gitnexus/) to get prettier + activate the pre-commit hook. The hook auto-formats staged files on every commit going forward.

[magyargergo]

Please submit a new PR if this is still relevant