Refiners Update

The update-mode counterpart to lattice-init. Where lattice-init detects missing standards and routes you to refiners to create them, this molecule detects existing standards and routes you to each refiner's revise mode to update them after a significant change — then records what changed and why.

It orchestrates the refiners; it never reimplements their interviews. Versioning is git-native: history lives in commits, and each revised document gets a one-line change note. No version numbers are introduced.

Required Skills

Read, apply:

1. framework:knowledge-priming -- Load project context. Understand what the project is and how the code has drifted from the current standards (always).

What This Does (and does not)

• Does: coordinate revising one or more existing standards documents after a change, and append a change note to each.
• Does not: create standards that do not exist yet (that is lattice-init + the relevant refiner), reimplement any refiner's interview, or introduce version numbers.

If the change requires a standard that does not exist yet (e.g. the team just adopted DDD but there is no ddd-principles.md), that is creation — direct the user to /lattice-init or the relevant refiner to create it, and note it in the summary.