Add transition notification publication substrate - #386
Conversation
…n publication substrate
|
To preview the documentation for this pull request, visit the following URL:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #386 +/- ##
===========================================
+ Coverage 90.94% 92.98% +2.03%
===========================================
Files 135 656 +521
Lines 6251 17411 +11160
Branches 1338 4471 +3133
===========================================
+ Hits 5685 16189 +10504
- Misses 172 473 +301
- Partials 394 749 +355
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Current status: All findings originating in this review are resolved.
Last reconciled on97f6a12. See aggregate Bugbot status.
🤖 Bugbot review snapshot
Bugbot reported 1 potential problem when commit 8793745 was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.
Findings
- low: Failed results can be reported as published notifications —
src/application/policies/publication_outcome_policy.ts:120
Bugbot: review complete
|
There was a problem hiding this comment.
Current status: All findings originating in this review are resolved.
Last reconciled on97f6a12. See aggregate Bugbot status.
🤖 Bugbot review snapshot
Bugbot reported 1 potential problem when commit 87b876b was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.
Findings
- low: Invalid transition targets can create unreconcilable notifications —
src/application/policies/publication_identity_policy.ts:111
Adds a reusable, idempotent transition-notification publication path with strict identity, fingerprint, content, and target validation. It records bounded, content-free outcomes for localized Job Summary reporting and strengthens coverage for duplicate handling and invalid targets.
What changed
Review notes