docs(ci): build workspace deps before Pages deploy; revert Dropdown comment

Two related fixes:

1. Roll back the leading "SHARP EDGE" comment added to
   examples/Dropdown.rozie. Although it lived above the <rozie>
   wrapper and didn't alter any emitted fixture content, it shifted
   byte offsets enough to break a byte-placement check in the source
   map / parser test suite. The convention is documented in the docs
   demo's inline comment instead, which is the right place for it
   anyway (consumer-side guidance, not source-side).

2. Update .github/workflows/docs.yml for the new workspace dep graph.
   @rozie/docs now consumes @rozie/unplugin (compiles .rozie files at
   build time) and @rozie/runtime-vue (debounce / throttle /
   useOutsideClick referenced by emitted Vue SFCs). Both ship from
   their dist/. Mirror the build-order pattern used by
   vue-matrix.yml / react-matrix.yml: build core → unplugin →
   runtime-vue → docs.

   Also extend the workflow's path triggers so changes to those
   packages or to examples/*.rozie sources rebuild the docs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: serpentblade

.github/workflows/docs.yml

@@ -5,6 +5,14 @@ on:
     branches: [main]
     paths:
       - 'docs/**'
+      # The docs site dogfoods @rozie/unplugin/vite to compile examples/*.rozie
+      # at build time, and the emitted Vue SFCs import @rozie/runtime-vue at
+      # runtime. Rebuild on any change to those packages, the example sources,
+      # or @rozie/core (transitively consumed by the unplugin).
+      - 'packages/core/**'
+      - 'packages/unplugin/**'
+      - 'packages/runtime/vue/**'
+      - 'examples/*.rozie'
       - '.github/workflows/docs.yml'
   workflow_dispatch:
 
@@ -36,6 +44,21 @@ jobs:
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 
+      # @rozie/docs imports @rozie/unplugin/vite (compiles .rozie files at
+      # build time) and the emitted Vue SFCs reference @rozie/runtime-vue
+      # (debounce / throttle / useOutsideClick at runtime). Both packages
+      # ship from their dist/, so build them before the docs build runs.
+      # @rozie/core is bundled into the unplugin's dist via tsdown but we
+      # still build it explicitly so the peggy generated parser is in place.
+      - name: Build @rozie/core
+        run: pnpm --filter @rozie/core run build
+
+      - name: Build @rozie/unplugin
+        run: pnpm --filter @rozie/unplugin run build
+
+      - name: Build @rozie/runtime-vue
+        run: pnpm --filter @rozie/runtime-vue run build
+
       - name: Build docs
         run: pnpm --filter @rozie/docs build
 

examples/Dropdown.rozie

@@ -10,21 +10,6 @@
     - Named slot with slot params (consumer uses `#name="{ data }"` shorthand)
     - Default slot with slot params
     - $props writes (compiles to parent-update path because `model: true`)
-
-  SHARP EDGE — trigger click handling:
-    The wrapping <div ref="triggerEl"> below has @click="toggle". Consumers should
-    render their trigger content inside the #trigger slot WITHOUT binding a click
-    handler — the wrapper's click bubbles up from any descendant and toggles. If a
-    consumer also binds @click="toggle" on their slotted button, both fire and the
-    state immediately flips back closed.
-
-    The slot's `:toggle` parameter is exposed for OTHER uses (e.g. closing the
-    dropdown from inside the panel body), not for wiring the trigger click. The
-    five consumer demos in examples/consumers/*/ follow this convention.
-
-    Tightening this contract (e.g. dropping the wrapper @click and making
-    consumers wire toggle themselves) would be a breaking change to the API and
-    every target's fixture set — tracked as a follow-up, not fixed here.
 -->
 
 <rozie name="Dropdown">