skills(delivery,verify): teach the release walk about carried-forward digests - #311
Merged
Conversation
… digests (#310) Release skill step 7: correct the trigger description (tags + workflow_dispatch — a plain main push never fired the fleet) and document what the workflow now does: rebuild only images whose eval.input-hash changed, retag the rest from the prior release (delivery/RULES.md rules 12-14), force_rebuild / rebuild_bases for CVE refreshes, freshness auditable via the Fleet status workflow. Verify skill step 40: the pass criterion becomes existence AND freshness — fleet-status.sh <tag> must read every image fresh, which covers carried-forward digests exactly (tag existence alone cannot distinguish a correct carry from a stale image). No step renumbering. Rules-side companion to the merged #307 (contributing rule 2 split). Resolves #310. Signed-off-by: Elron Bandel <elron.bandel@ibm.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
1 participant
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.
Resolves #310. The rules-side companion to #307 (kept separate per contributing rule 2), closing out #292's migration path.
What
Two procedure docs catch up with the shipped carried-forward system:
.agents/delivery/release/SKILL.mdstep 7 — corrects the trigger description (tags +workflow_dispatch; a plainmainpush never fired the fleet workflow) and documents the new behavior: only images whoseeval.input-hashchanged rebuild, the rest retag from the prior release (delivery rules 12–14);force_rebuild/rebuild_basesfor CVE refreshes (upstream drift is invisible to the hash); freshness auditable via the Fleet status workflow orfleet-status.sh <tag>..agents/verification/verify/SKILL.mdstep 40 — the pass criterion becomes existence and freshness:fleet-status.sh eval-vX.Y.Zmust read every imagefresh. Tag existence alone cannot distinguish a correctly carried-forward digest from a stale image; the hash check can, and covers carried digests exactly. No step renumbering (principle 9's 46-step count untouched).Rules checked against
.agents/contributing/RULES.md1–3 (resolves drift drift: release + verify skills predate carried-forward releases (wrong trigger, existence-only step 40) #310; rules/docs-only PR — no code; this section)..agents/meta/skills/RULES.md(procedure form preserved; steps stay walkable by human or agent)..agents/delivery/RULES.md12–14 (the outcomes these procedures now describe accurately).