ci: move k3s debug payload to sim golden #118

Closed
L0GYKAL wants to merge 1 commit from docs/k3s-sim-golden-contract into main
Owner

Summary

  • keep spoke descriptor v2 closed to the existing sim and nexus artifacts
  • define k3s-debug as a Replicant-tier profile consuming the exact Sim golden artifact
  • make runner identity the activation boundary: K3s starts only for k3s-debug
  • reserve the checksum-pinned upstream k3s-selinux local RPM for sim-golden and reject it for Nexus or any other image

Test-first evidence

Red before implementation:

FAIL: nexus-golden accepted the K3s SELinux local RPM reserved for sim-golden

Green after implementation:

image source hash derivation: PASS
markdownlint-cli2: 0 errors
the-rules complete local contract suite: PASS

No descriptor key or schema change is introduced.

## Summary - keep spoke descriptor v2 closed to the existing `sim` and `nexus` artifacts - define `k3s-debug` as a Replicant-tier profile consuming the exact Sim golden artifact - make runner identity the activation boundary: K3s starts only for `k3s-debug` - reserve the checksum-pinned upstream `k3s-selinux` local RPM for `sim-golden` and reject it for Nexus or any other image ## Test-first evidence Red before implementation: ```text FAIL: nexus-golden accepted the K3s SELinux local RPM reserved for sim-golden ``` Green after implementation: ```text image source hash derivation: PASS markdownlint-cli2: 0 errors the-rules complete local contract suite: PASS ``` No descriptor key or schema change is introduced.
ci: move k3s debug payload to sim golden
All checks were successful
lint / lint (pull_request) Successful in 45s
lint / release-gate (pull_request) Successful in 1s
1eb89e8600
L0GYKAL closed this pull request 2026-10-18 18:01:08 +02:00
All checks were successful
lint / lint (pull_request) Successful in 45s
lint / release-gate (pull_request) Successful in 1s
Required
Details

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
L0GYKAL/the-rules!118
No description provided.