cursus.mcp.tools.project

cursus.mcp tools for the project.* namespace.

Scaffold a NEW Cursus pipeline project — the phase-0 package skeleton every project shares, regardless of framework, DAG, or features. project.init writes the fixed, knowable-at-t=0 files (a region-agnostic run_pipeline.py, the @MODSTemplate deployment class that loads pipeline_config/dag.json, a shared generate_config.py skeleton with project_root_folder filled and a TODO per-node value-init block, an empty dag.json stub, the folder tree with per-folder READMEs) and a root README.md action-item ledger that hands every context-dependent piece — authoring the DAG, copying scripts/handlers, filling the config values — to its owning downstream workflow (/cursus-author-step, /cursus-configure-pipeline).

This is a deterministic tool: it emits versioned package templates with the project name and framework substituted in, so it works fully offline over the stateless JSON tool boundary (no sub-agents, no engine import). The source-grounded generation variant (adapting the templates to a live reference project as it drifts) lives in the cursus-init-project dynamic workflow; project.bring_up points a caller at the cursus-new-project orchestrator that chains scaffold -> DAG -> config end-to-end. See FZ 31e1d3f5c / c1 / c2 / c3 in the Cursus Simplification Trail for the design.