Event taxonomy parity: Node/Java expose only 4 outcome events #535

Activity

1. kartikeya-27

   added

   enhancementNew feature or requestNew feature or request

   javaJava SDKJava SDK

   nodeNode SDKNode SDK

   parityCross-SDK parity gapCross-SDK parity gap

   on Jul 24, 2026
2. pratyush618

   closed this as completedon Jul 24, 2026
3. pratyush618

   reopened this on Jul 27, 2026
4. stromanni commented on Jul 27, 2026

   

   stromanni

   on Jul 27, 2026

   Collaborator

   More actions

   Taxonomy is ported. Node emits all 28 wire names (#537), Java 25 of its 26 (#538), matching Python's 28 (worker.unhealthy is declared-but-reserved in Java; Java predicates are pass/reject only so predicate.deferred/predicate.cancelled have no constant — both documented in docs/content/docs/java/guides/extensibility/events.mdx).

   Two follow-ups split out, both narrower than this issue:

   • Predicate skip event has two wire names across SDKs #570 — Python predicate.cancelled vs Node predicate.skipped for the same outcome; breaks webhook filtering across SDKs.
   • Node events docs stale after predicate events landed #571 — Node events page still describes the pre-feat(node): predicate recipes, decisions, and registry #543 predicate surface.

   This can close once those are filed against the right milestone.
5. kartikeya-27

   closed this as completedon Jul 28, 2026