Dragan Spiridonov b4374f220b fix(bridge): preserve domain-specific fan-out per #484, parametrize tests ...

Rescoped per @Jordi-Izquierdo-DDS's filed issue #484 and his Stage A.1
verified shop patch 050:

- KEEP the domain-specific fan-out events (test-execution.TestRunCompleted,
  coverage-analysis.CoverageGapDetected/CoverageReportCreated,
  test-generation.TestGenerated, code-intelligence.FileChanged) with
  their existing flat basePayload shape. Their handlers were already
  shipped against this shape; changing it would break out-of-tree
  subscribers. Smaller blast radius.
- ONLY change the universal learning.ExperienceCaptured event to use the
  canonical nested { experience: TaskExperience-shaped, reward } shape.

Tests parametrized across multiple non-fan-out domains
(requirements-validation, security-compliance, visual-accessibility) per
Jordi's #484 test improvement suggestion — these exercise the
universal-event path exclusively, which v3.9.28's test-execution-only
test inadvertently masked via the fan-out's side-effect kv write.

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

2026-05-14 12:16:00 +00:00

..

bridge-end-to-end.test.ts

fix(bridge): preserve domain-specific fan-out per #484, parametrize tests

2026-05-14 12:16:00 +00:00