Set up Cursor Cloud dev environment for CodeChecker

[gamesh411]

Summary

Sets up the CodeChecker development environment for Cursor Cloud agents and documents durable, non-obvious caveats in AGENTS.md.

CodeChecker is a static-analysis infrastructure: Python CLI/analyzer + Thrift web server + Vue 3 web UI, orchestrated by GNU Make.

What was done

• Installed system deps: clang-tidy, cppcheck, python3-venv/python3-dev, libstdc++-14-dev (fixes clang++ not finding iostream), and libldap2-dev/libsasl2-dev (for python-ldap).
• Created the dev virtualenv (make venv_dev) plus auth deps (python-ldap) needed by the web server unit tests.
• Built the package with BUILD_LOGGER_64_BIT_ONLY=YES make package (avoids 32-bit ldlogger libs) — includes the Vue UI build.
• Configured the startup update script (venv + dev deps + auth deps).
• Added AGENTS.md ## Cursor Cloud specific instructions.

Verification

• ✅ make pycodestyle and cd web/server/vue-cli && npm run test:lint
• ✅ make test_unit (130 analyzer + 41 server + 3 client passed)
• ✅ End-to-end: CodeChecker check on a sample buggy C file found 3 defects (null deref, division by zero), stored to CodeChecker server (SQLite), and viewed in the Vue web UI.

codechecker_web_ui_walkthrough.mp4

Reports list for hello-cc run
Report detail with highlighted null-pointer bug path

Note for future agents

Use the non-*_in_env test targets with the root venv_dev activated. The *_in_env targets create isolated per-component venvs that omit auth deps, causing test_ccldap.py to fail with ModuleNotFoundError: No module named 'ldap'.

_{To show artifacts inline, enable in settings.}