Flow Intent Scenarios (Layer 1)
These Layer 1 Gherkin scenarios express the flow insight MVP in provider-neutral language. They are ground truth for the signal semantics. A Layer 2 conformance profile and TypeScript contract harness now exist to validate these semantics against running stacks.
Source: tests/features/flow-insights.feature
Scenario summaries
- Blocked on review: A change waiting beyond the expected review window is surfaced with pending reviewers and elapsed time, directing action to reviewers rather than the author.
- Passed checks but failing trunk integration: Branch-level validation passed, but trunk integration failed afterward; the mismatch is explained with integration timing.
- Unclear ownership: Ownership is missing or conflicting for a work item; the signal requests a single accountable owner for the scoped service or team.
- Waiting on evidence, not effort: Implementation is complete and validation is clear, but required evidence is missing or stale; the signal names the missing artifacts and responsible owner.
- Aging work between implementation and validation: Implementation finished, yet validation has not started or is stalled beyond the expected window; the signal cites the delay and outstanding checks.
- Risk signal by service, team, or flow stage: Multiple signals cluster in the same scope within a short window, elevating risk and recommending focused remediation.
Provider-specific and edge-case scenarios
The feature file also includes provider-tagged scenarios (@github, @gitlab,
@gitlab-self-managed, @cross-provider) that validate provider-specific
normalization paths, cross-provider equivalence, ownership ambiguity, evidence
state inference, and reduced-confidence behavior under partial data.
Layer 2 conformance profile
A formal Layer 2 profile and TypeScript contract harness now exist for this capability. See Flow Insights Profile for the scenario table, fixture catalog, cross-stack equivalence rules, and stack declaration requirements.