The Library and Storybook update after a merge
When a change merges, the same command that runs in your CI rebuilds the Library from the records in your repository. Each component page shows its contract, its rules, its owner and when not to use it. Storybook stories are generated from the same contracts, so a story cannot drift from the contract it shows.
Both passed their acceptance test in a suite run on 1 November 2026. A real commit landed on a cloned repository, and the Library and Storybook rebuilt from it with no manual step.
This site works the same way. Its own Library is built from its records on every release.
See the run This site's Library
Drift is reported against the repository
Loom compares what the repository says with what the Library and Storybook show. When a page was built from an older commit, or a component in the repository is missing from the Library, the report names it. This part has run between the repository, the Library and Storybook.
What the run does not cover
The Figma library update and the full drift report, which includes Figma, have not run against a real Figma file. Updating Figma variables needs a Figma token and an explicit opt-in, and is never automatic without one. Until that run passes, Sync passes in part.
Coming next
- The Figma library from the repository. Variables and components in Figma update from the repository after a merge, through Figma's API and Loom's plugin.
- One drift report across all four. Repository, Library, Storybook and Figma, with each difference turned into an accept-or-revert decision for its owner.