docs(progress): pin event-driven routings commit ref

zichun
1 parent 35ad8a8d
Showing 1 changed file with 1 additions and 1 deletions
PROGRESS.md
@@ -102,7 +102,7 @@ That target breaks down into roughly 30 work units across 8 phases. About **22 a
 | # | Unit | Status |
 |---|---|---|
 | REF.0 | Hello-world plug-in (PF4J + Plugin lifecycle + endpoints + own DB) | ✅ DONE through v0.6 |
-| REF.1 | Real BPMN workflow handler (quote → job card) | ✅ DONE — `3027c1f` — plug-in BPMN publishes `WorkOrderRequestedEvent` (new api.v1 event); pbc-production's `WorkOrderRequestedSubscriber` reacts by creating a DRAFT WorkOrder via `WorkOrderService.create`. Idempotent on event code. Plug-in has zero compile-time coupling to pbc-production; pbc-production has zero knowledge the plug-in exists. |
+| REF.1 | Real BPMN workflow handler (quote → job card) | ✅ DONE — `3027c1f` core + `35ad8a8` v3 routings — plug-in BPMN publishes `WorkOrderRequestedEvent` (new api.v1 event); pbc-production's `WorkOrderRequestedSubscriber` reacts by creating a DRAFT WorkOrder via `WorkOrderService.create`. Idempotent on event code. Plug-in has zero compile-time coupling to pbc-production; pbc-production has zero knowledge the plug-in exists. **v3 follow-up**: event now carries optional `RoutingOperationSpec` list; the plug-in's handler ships a default 4-step CUT → PRINT → FOLD → BIND routing that reaches the created WO as v3 operations, end-to-end through api.v1 alone. |
 | REF.2 | Plate / ink / press CRUD as customer-style domain | ✅ Partial — plate + ink CRUD live (`7af11f2`) |
 | REF.3 | Reference forms + automation rules in plug-in metadata | 🔜 Pending — depends on P3.3, P3.4 |