Doc system test

Project lifecycle

The user's folder - the templates stacked in it, its state file, and how create and update change it. All project state lives here.

Meta block front matter of this doc
namespaces
  • durian.cloud/cyanprint/project-lifecycle

What this context owns. Everything that happens to a target folder: which templates are stacked in it, the state file that records them, and the batch run behind cyanprint create and cyanprint update that rebuilds the last run, makes the new one, and merges both with the user's edits.

What it does not own. How one template version and its dependencies are run and layered (composition), how questions are asked (prompting), containers and sessions (coordinator), versions and pinning (registry), and what a template is (authoring).

Start here: client-side state and determinism, the design every doc below hangs off, and the shop example, the one project every doc uses.

Docs, in reading order

DocTypeOne line
State fileformatthe only record of a project: records, history, managed files, clashes
Createfeatureone command, three modes: new template, upgrade, rerun
Updatefeatureevery stacked template to a newer version, saved answers reused
Managed filesformat (stub)the paths the templates make, per template and as a union
File clash recordformat (stub)one file_conflicts entry
Template stackingflowmany templates in one folder, replayed and laid oldest first
Batch runflowrun twice, stack, merge once, write, save, run commands
Three-way mergealgorithmmerge base (rebuilt), local set, incoming set, one git merge
Post-template commandsalgorithmshell commands after the write, interactive and headless
Created folder cleanupguarda stopped headless run leaves the disk as it was
Output pathsguardkept off this public page (security-related)
Git dirty checkguard (stub)update stops or asks on uncommitted changes