Repository navigation
docs(specs): validate gate visibility and the full quickstart - #209
Merged
Juanmadiaz45 merged 1 commit intoSep 21, 2026
Merged
Conversation
EstebanGZam
self-requested a review
September 21, 2026 00:05
EstebanGZam
approved these changes
Sep 21, 2026
Juanmadiaz45
deleted the
docs/gate-visibility-and-quickstart-validation
branch
September 21, 2026 00:08
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.
What changes
Adds evidence (
evidence/runs/20260921T000000Z-gate-visibility-validation/) validating T024 (gate presence/visibility/fail-fast) and T038 (full quickstart end-to-end), and links the companion.githubfix.Why
T024 asks to validate gate visibility via
actdry-run and a forcedrun-unit=truerun.run-unitno longer exists (retired when the architecture centralized on one mandatorytest-command), and localactproved impractical (20+ minutes pulling a runner image without completing on this workstation). Switched to real GitHub Actions runs (disposable draft PRs, closed without merging once observed) and found a real defect: an emptytest-commandmade "Run repository tests" reportsuccesshaving tested nothing -- a genuine FR-017 violation, not just a stale-task-wording issue. Fixed upstream in MicroTodoSuite/.github#27.T038 asks to run quickstart end-to-end against a GHCR/cloud-disabled mode that also no longer exists (same reconciliation as T035). Ran every section that still applies against the current repos instead of a mode that can no longer be exercised.
Tasks
gitops specs/003-reusable-cicd-delivery T024 (delivered, defect found and fixed)
gitops specs/003-reusable-cicd-delivery T038 (delivered, with reconciliation)
The task register is updated in this pull request
Every task ticked here was verified by locating its artifact
How it is verified
act):test-command: ""reported"Run repository tests": successbefore the fix (disposable PR.github#25); after the fix (.github#27), the same input reports"Reject an empty test-command": failureand"Run repository tests": skipped(disposable PR.github#26). Both throwaway PRs closed without merging once observed.actionlintclean onci.yml/release.yml/promote.yml; all three declareworkflow_call.uses:callers pinned to the same SHA, nodevelopment.ymlremains.kustomize build | kubeconform -strictpasses for all four onboarded services' local overlays (Valid: 4, Invalid: 0, Errors: 0each); base is environment-neutral; shared JWT confirmed by T029's new contract test.validate-gitops.ymlruns on every PR including this one.aws-knowledge,microsoft-learn) applies to this specific change.Risk and rollback
None: adds evidence documentation only. The actual behavior fix lives in the linked
.github#27PR, reviewed there. Rollback here is reverting this commit.What this PR does not do
Does not itself change any workflow -- the fix is in
.github#27. Does not restore a GHCR/cloud-disabled mode that no longer matches the architecture.