Repository navigation
docs(ledgers): T1 closes on corpay-console-smoke's first green night; G11 met (#325) - #583
Open
omercelikdev wants to merge 2 commits into
Open
omercelikdev wants to merge 2 commits into
omercelikdev wants to merge 2 commits into
Conversation
… G11 met (#325) The proof T1's row named is the link to the job's first green night: nightly run 154, 2026-11-10, the first nightly after #540 merged. It drove CorPay on its published train with Keycloak 26.0.7, and 4 of 4 Playwright specs passed: the API head's floor, the EOD job on the internal head, the four-eyes payment file by two principals, and the approved file pinned to #539's failure shape. Green on every nightly since (runs 154-160). The nightly runs themselves end cancelled for the Messaging mutation timeout (#562), not for this job. open-threads: T1 to Closed threads. ga-gate-status: G11 met. ai-sdlc-status and the master plan's item 11 say so. CHANGELOG [Unreleased]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018AFdNZjRzMYQfNkJCg4Zjr
3 tasks
…ds no closed claim on open issues (#325) ledger-check reads any line holding 'closed' as claiming every issue on it is closed. The G11 row names #325 and #539, both open until this merges, and the master plan's note names #325. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018AFdNZjRzMYQfNkJCg4Zjr
Collaborator
Author
|
CI follow-up: Cause: ledger-check reads any line containing "closed" as a claim that every issue number on that line is closed. Two lines tripped it:
Fix in Generated by Claude Code |
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 and why
#325's last open criterion (AC3 in #540) is closing T1, and T1's row names the proof that closes it: "the thread closes with the link to its first green night."
When #540 merged (2026-11-10 08:37Z), T1 could not close in that PR, because no night had run yet. That night has now run, and so have six more.
corpay-console-smokeThe job ran for real, not as a skipped step. In run 154 the drive step took 5 min. CorPay was built on its published train (0 warnings), Keycloak 26.0.7 was pulled, and the Playwright log reads:
Honesty about the whole runs. The nightly runs end
cancelledorfailurebecause of other jobs. The Messaging mutation job hits its 300-minute timeout (#562, PR #577 open). T1's proof is this job's night, and the ledger entry says exactly that, so nobody reads "the nightly was green".The change (ledgers only; no package, script or workflow change)
docs/strategy/open-threads.md: the T1 row leaves the open table, and a Closed threads entry carries the job link, what the four specs proved, and the green streak. T62, T63 and T64, which the drive found, stay open in their own rows.docs/strategy/ga-gate-status.mdG11: now Met, with the link. This file holds gate status.docs/rfc/goldpath-ga-readiness.mdis untouched, so the PR is not Tier C on that account.docs/strategy/ai-sdlc-status.md: "T1 is still OPEN" becomes CLOSED, with the night.docs/strategy/master-plan-2026-08.mditem 11: a dated status note. The plan's original sentence is kept.CHANGELOG.md[Unreleased] › Changed: one entry.Reproduce
This is a ledger change, so there is no failing test to plant. The "red" here is the evidence itself: a night where the job failed or was skipped would leave T1 open. Every night since #540 is listed above with the job's own conclusion.
Self-check
grep -rn "first green night"over*.mdnow matches only the historical CHANGELOG entry for test(console): the console DRIVES CorPay through the consoles it serves, two principals via Keycloak (G11, T1, #325) #540 and the new entries. CHANGELOG [Unreleased] is updated. No new deferral, so no new T-number.Gates run
docs-freshness.shrc 0,schema-honesty.shrc 0,skills-parity.shrc 0,template-pins.shrc 0.ledger-check.shrc 0, but it printed "no authenticated gh — skipped honestly", so its GitHub reconciliation did not run here. That is the one gate I could not run. Please run it with an authenticatedgh.What I could not verify
ledger-check.sh's GitHub half (above).Closes #299and merged, but the issue is still open.Closes #325
Generated by Claude Code