origin-project-update

Select the meeting records explicitly, then run the bootstrap workflow: the helper preflights that no project note or list row exists for the key, an LLM drafts sections with source links from only the selected records, and you review before writing. The script never creates the note body itself.

Run scripts/project_update.py with --mode backfill, --project-key, and --record paths. It defaults to a dry-run showing diffs; add --apply only after review. It adds the YAML project key and a single relative backlink immediately after the frontmatter.

No. If a record already has YAML or a backlink pointing to a different project, the script raises a conflict and stops without changing any file. Reassignment or explicit overwrite is a separate operation outside bootstrap and backfill.

The script requires Python 3 and PyYAML for parsing note frontmatter. If PyYAML is missing, it exits with an error rather than falling back to manual parsing, since hand-editing YAML risks corrupting the contract.

Validation fails if the YAML project key mismatches, the client field is empty, required headings like overview or minutes are missing, or local absolute paths appear in the note. It also fails when list_project.md has a duplicate or missing row for the key.

Do not use it for newly recorded meetings that the recorder already routes to an existing project automatically; re-running the same LLM update would double-apply changes. Use it only for bootstrap, backfill, or audit with explicitly named targets.