docs(memory): record the CI runner contract - #29
Merged
Conversation
CI-01-ACTIONS said only that CI memories record which checks prove integrity. It now carries the constraint the workflows actually depend on: every ci-workflows caller that accepts a runner passes ubuntu-latest explicitly, because the reusable's default belongs to the pinned commit and current main defaults 39 of 46 reusables to the estate self-hosted label. Also records the pin-bump review step and that the library enforces this for its own calls but not for external consumers. 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.
Follow-up to the explicit-runner change: the Serena
CI-01-ACTIONSmemoryrecorded only that "CI memories record which checks prove repository integrity",
which is true of every repository and therefore says nothing about this one.
It now carries the constraint the workflows actually depend on:
ci-workflowsreusable that exposesrunnerpassesubuntu-latestexplicitly, because this repository is public and thereusable default is a property of the pinned commit — on current
ci-workflows main, 39 of 46 reusables default to the estate self-hosted
amsterdamlabel;ubuntu-latest, so the explicit valueis a no-op today and becomes load-bearing at the next bump;
inputs.runner.defaultacross the two commits;nothing extends it to external consumers, which is why the rule also lives in
AGENTS.mdand.claude/CLAUDE.mdhere.Memory metadata and evidence commit refreshed. No code or workflow change.