MeshCommand MeshCommand

Spaces

A task lives in one project. Huly has no project-to-task junction at all — membership is Doc.space — and this corpus models that as project_and_task with a partial unique index on (task_id) WHERE is_primary = 1. So these rows are built from the tasks themselves and then enriched from mc_project.db, never the other way round: a project_code with no project row is the interesting case, and an INNER JOIN would have hidden it.

0 spaces 0 open tasks 0 not in the project registry 0 where the edge count differs

No rows