Skip to content

Add lifecycle telemetry transitions #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ncolesummers merged 2 commits into from
Jul 8, 2026
Merged

Add lifecycle telemetry transitions #78

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0845544
feat(loops): add lifecycle telemetry transitions
uidaho-nsummers Jul 8, 2026
5b56778
fix(loops): preserve validation blocked reasons
uidaho-nsummers Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/loop-manifest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,9 @@ Reports must not embed raw stdout, stderr, prompts, tokens, credentials, or
secret-looking fixture values. Run and step status transitions, downstream
blocking, approval-policy continuation, and lifecycle telemetry are handled by
the transition layer rather than by the validation report runner.
Failed validation gates block downstream stages by default. Skipped required
gates also block downstream stages, even when other gates passed; skipped
optional gates remain inspectable in the report but do not block progression.

Queued `validation_report` artifacts may carry
`validationReportMetadataKind: validation_report_contract` with
Expand Down
Loading
Loading