lamina-initlisted

# /lamina-init Before any evidence or graph mutation, read and apply `../lamina/orchestrator/prerequisites/cli-required.md`. Read `../lamina/orchestrator/audit-profiles.yaml`. Load the `init.always` references, then only those `init.conditional` references whose `when` signal is present. For each selected entry, open the named capability `SKILL.md` and then its exact reference; do not load sibling topics. For a directory that is not yet a Git project, initialize Git metadata as specified by that prerequisite before writing evidence. Do not ask for or create an initial commit. Init writes evidence files only under `.lamina/` and canonical knowledge through graphd. It never edits application source. ## Evidence artifacts Write `.lamina/business-context.md` with frontmatter containing `lamina.maturity`, `platform`, and `last_updated`, followed by exactly these non-placeholder sections: Problem statement, Business goals, Success metrics, Scope, Users & market, Product posture, Constraints, Stakeholders, Risks & unknowns, Research posture, Triad check. Write `.lamina/personas.json` as evidence-source JSON with evidence-grounded personas. Goals, constraints, and evidence are arrays. Do not invent demographics. These files are indexable evidence, not canonical graph state. Run the shipped init/persona validators when available, then `lamina graph observe` so CocoIndex produces explicit source Observation envelopes. The CLI automatically replaces an incompatible graphd and re