fix(ci): preserve every started job - #20
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes preservation of every started CI job an executable library invariant. Removes cancellation from all self-workflows and consumer examples, updates the performance/free-tier agent skills, and rejects future cancellation expressions in the workflow contract.
Type of change
Threat-model note (required for workflow / permission changes)
No new action, token, permission, runner, egress, or external input is introduced. Runs may queue or execute concurrently instead of being cancelled. This preserves complete evidence and prevents a newer ref from erasing the result of already executing code.
Permissions diff (required for workflow / permission changes)
No permissions changed. Every existing top-level and job-level permission remains byte-identical.
Checklist
Tier impact
Runtime policy
No synthetic Drakkars workload is created. Private fleet runtime evidence continues to come only from real consumer project jobs.