Module project 

The project a dev session works on: the one state tree its builds, runs, and editor sessions address, opened by the binary at startup. The project a dev session works on.

Every tier below this one takes its paths as arguments: the cook is handed the tree it builds into, the engine’s App carries the one it runs against, and the two content-addressed caches are told which files they are. What remains is that a dev session works on exactly one project for the length of a process, and that the editor’s panels, the hot-reload passes, and the background workers all reach for it from places with no caller to thread it down from.

So the session holds it, and the concinnity binary [open]s it once at startup from whatever directory it decided the project lives in. Nothing here resolves a root: open is given one.

Functions

close

Close the session’s project, leaving it with none.

open

Open tree as this session’s project, and point the build cache at the segment it names. Until a host calls this the session has no project: every build resolves no assets/, has nowhere to write blobs, and warms nothing.

tree

The session’s project, or None when nothing opened one.