Penpot Sync and Design Drift Review Wired Up
Photo by Andrey Matveev on Unsplash
The bidirectional Penpot sync path is validated and the design review prompt in run_arm_c.py now outputs a drift report against the design.md spec. Token and component sync workflows are next.
Two items closed in Phase 5b today. Both live inside the existing hermes-ab-test project — no new repos, no new services.
penpot-sync validated
run_arm_c.py in ~/projects/hermes-ab-test/ is the only confirmed working path for Penpot sync as of the 2026-05-30 spot-check. Other approaches tested during Phase 4B either stalled on auth or produced incomplete frame output. This is the one that ships.
- ~/projects/hermes-ab-test/run_arm_c.py (penpot-sync validated)
Design review prompt updated
The prompt in run_arm_c.py now reads: compare current page against design.md spec, output drift report. Previously it was running a generic critique pass. The new prompt gives the qwen2.5-coder:14b model via mcphost a concrete reference document and a concrete output format — drift report, not free-form notes.
What this unblocks
With sync validated and drift reporting in place, the next two workflows — Penpot Token Sync and Penpot Component Sync — have a stable base to build on. The drift report output also gives the design agent something structured to act on rather than a narrative it has to parse.