- SKILL.md: confirm type/pattern/size/cuts with the user before rendering; checklist hooks for the checkpoint and the packaged self-check - scripts/verify-docs-sync.py: CI now fails when the frontmatter description loses a type's lexical hook, the gallery can't reach a shipped example, or the README tree names a missing file - skills/diagram-design/scripts/self_check.py: distilled output checker that ships with the skill so installed agents can verify their own diagrams; adversarial suite in scripts/test-self-check.py - assets/index.html: six new tabs (OAuth sequence + five single-variant examples with a data-single variant lock) so every shipped example is browsable - docs/adr/0001-0004: settled policies recorded (pinned controller, taxonomy freeze, reveal-only autoplay, byte cap + trigger-rich description) - README: It's-working-if section, new gates documented; CONTRIBUTING: gate table, ADR guidance, type-addition invariants; CI: two new steps
1.4 KiB
ADR 0001 — Static by default; one pinned controller for motion
Status: accepted (v2.3)
Context
Diagrams are shared as single HTML files and embedded in posts, decks, and docs. Arbitrary inline JavaScript in a shareable artifact is both a security surface and a review burden: every generated file would need its script audited. Motion, however, genuinely clarifies ordered change (queues filling, policy traces diverging).
Decision
Output is static and script-free by default (data-motion-mode="none"). When motion is requested, the file may carry exactly one <script data-diagram-controls> block whose body must byte-match the reviewed controller in assets/template-motion.html. The match is enforced twice: SHA-256 in lint-skin.py and string equality in verify-motion.py; the packaged scripts/self_check.py repeats the check for installed agents.
Consequences
- Any behavior change to motion is a change to
template-motion.html, reviewed once, and re-propagated verbatim; hand-edited controllers fail every gate. - The controller cannot be extended per-diagram. A diagram needing bespoke interaction is out of scope for this skill.
- The check anchors to the template in the same commit, so a PR that weakens template and copies together still passes the identity check — reviewer attention on
template-motion.htmldiffs is the real gate.