[JacobStephens2]

Summary

 Two shifts
-  Day shift:   grill → spec → issues
+  Day shift:   /grill-with-docs → /to-spec → /to-tickets
-  Third shift: implement → review → pull request
+  Third shift: /implement → /code-review → /pr   (each links to its job sheet)
+  "Read every prompt and skill the agents get →"

 How a Run works (stepped)
   lit unit
+    rollers and drum turn; Pause stops them; off under reduced motion
   click a unit in the drawing
+    goTo(step)            # same as the 1·C…4·K buttons
+    static version: scroll to that unit's column
   Factory skill chips
-    implement, code-review, …
+    /implement, /code-review, …

 Prompts and skills page, now linked from
+  hero credit line, third shift, press lede, footer (both pages)

The hero framing now says "cut it into tickets". Each roller is drawn around its own origin so CSS can turn it in place. share-card.png is re-rendered because its press line now shows the crosses on the rollers.

Evidence

• Before:
  After:

• Before:
  After:

  In headless Chromium, only the lit unit's drum transform changes over time: 400 ms apart it went from matrix(0.19, -0.98, …) to matrix(-0.56, -0.83, …), and units 2 to 4 stayed at the identity. Clicking unit 3 in the drawing lit unit 3 and showed "3 · Y · Review". No page errors. cargo test passes.

Merge Danger

Door: two-way

Static site files only. Reverting the commit restores the old page.

Blast Radius: cosmetic

The press stage is sticky and scroll-stepped, so a click on a unit scrolls the page, the same as the step buttons do. The drawing stays role="img", and the step buttons remain its keyboard and screen reader equivalent.

🤖 Generated with Claude Code