chore(env): add Cloud Agent environment config

[seonghobae]

Pull Request

Summary

• Add .cursor/environment.json so the BandScope Cloud Agent development environment follows the checked-out branch.
• Make the agent dependency bootstrap reproducible: pin the Astral uv installer to the repository CI version (0.8.6), restrict curl transport to HTTPS with a TLS 1.2 minimum, use unmanaged installation, install Node dependencies with npm ci, and sync Python dependencies from uv.lock with --frozen.
• Add a focused supply-chain regression test for the Cloud Agent bootstrap contract.
• Start the desktop Vite development server as a managed terminal on port 5173.

Ownership boundary

The dependency-security delta that had been added to this branch was reverted in a990aa8a07d4ade8334b21240339a3730322722d. pdfjs-dist, nanoid, undici, npm-generator and lockfile security remediation remain owned by canonical BandScope PR #783. This PR does not duplicate that authority and does not inherit #783's checks, reviews, or merge evidence.

Protected-base dependency-lifecycle checkout credential hardening is separately owned by canonical BandScope PR #894. Exact-head security-audit evidence for this PR still exercises the protected-base workflow and therefore shows persist-credentials: true; this environment-config lane must not duplicate #894's workflow mutation.

The effective PR diff is .cursor/environment.json plus services/analysis-engine/tests/test_cloud_agent_environment.py.

Verification

• The focused regression requires the exact versioned Astral installer, --proto '=https', --tlsv1.2, UV_UNMANAGED_INSTALL, npm ci without npm install, and frozen uv sync.
• The pre-hardening environment lacked the HTTPS-only/TLS assertions' required flags; exact current head b0972c5ad01c506e24566433e8dbf9008c91c4a9 contains the narrow transport fix.
• On that unchanged head, ci run 32079563512, release 32079563534, build-baseline 32079563482, sbom 32079563524, bandit 32079563536, SAST Semgrep 32079563584, and secret-scan-gate 32079563535 are terminal-success.
• Exact security-audit run 32079563455, job 95539717817, checks out merge tree 5953062fd569a4824af8a6d2c0684f1b832371dc and fails first at npm audit --workspaces --audit-level=high on protected-base nanoid <3.3.18, pdfjs-dist >=5.6.83 <6.2.108, and undici 7.0.0-7.28.0; later Python/Rust audit stages are skipped and are not counted as success. The same exact log also confirms the inherited security-audit checkout persists credentials, which is fix(security): drop persisted credentials before dependency lifecycle code #894-owned rather than an excuse for a leaf workaround here.
• Aggregate Security Scan run 32079563607 has successful dependency-review, OSV, and Scorecard jobs; its failed trivy-fs job 95539718743 reports the protected-base HIGH CVE-2026-16633 finding for pdfjs-dist at package-lock.json:6370 and directs remediation to the shared base.
• There are no unresolved inline review threads at the latest exact-head inspection.
• Any inherited npm HIGH findings from protected develop remain a fix(security): establish canonical npm, PDF.js, Nanoid, and Undici baseline #783 dependency gate and must not be suppressed here.

Security notes

Attack surface

.cursor/environment.json runs package installation in Cursor's isolated Ubuntu-based Background Agent environment and starts the existing local Vite development server. It introduces no product runtime API, filesystem authority, credential, or production network path.

Trust boundary and mitigations

• The committed environment setup follows Cursor's documented install/terminals model.
• The uv installer URL is version-specific and aligned with BandScope CI; curl is restricted to HTTPS and TLS 1.2+ for the installer transfer; UV_UNMANAGED_INSTALL prevents installer-driven shell profile mutation and self-update behavior in the ephemeral agent bootstrap.
• Node dependencies are installed from the committed npm lock with npm ci; Python dependencies are synced from the committed uv lock with --frozen.
• The focused regression rejects floating transport/toolchain behavior, npm install, and non-frozen Python sync from returning to this config.
• No secrets are embedded or referenced.
• The terminal starts only the existing desktop development command.

i18n impact

No user-visible product string changes.

Merge boundary

Target remains protected develop@acdbea6344fe1231c39535b575f4de35e4c607c9. Keep this PR Draft until canonical #783 and #894 dependencies are integrated/revalidated as applicable and the unchanged then-current head satisfies every required repository and central gate plus a qualifying independent non-author approval. Do not treat queued, skipped, failed inherited-base, predecessor, protected-base, dependency-owner, or model-only evidence as success; do not suppress or duplicate another owner's failure merely to make this leaf green.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}