weichenandCursor 3d6de0c4ac Wire the layered Python environment into service startup ...

Why: The dependency layer already existed in the backend, but service startup never passed it, so the sandbox could not import the packages the host already had.
Evidence: SELF go tests recorded on the backend commit. svc.sh only exports the env root after env ensure leaves a current base layer, and a failed download does not block startup.
Impact: Instances share runtime/envs. Existing exec= lines are left as stored. Proposal, backend, and frontend gitlinks move to this branch.
Refs: .task/feature-layered-python-env.md
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-10-15 13:53:00 +00:00

..

backend @ b85a1e1ca3

Wire the layered Python environment into service startup

2026-10-15 13:53:00 +00:00

core @ 1a5ef6b75c

Integrate the nonblocking workbench and its display rules

2026-10-15 07:05:57 +00:00

documents @ 945db355fc

Wire the layered Python environment into service startup

2026-10-15 13:53:00 +00:00

frontend @ e33d17e1a6

Wire the layered Python environment into service startup

2026-10-15 13:53:00 +00:00

ui @ c9187473fb

Fix the remaining workbench failure and question-handling boundaries

2026-10-15 07:37:10 +00:00