Skip to content

release-train: develop -> staging - #155

Merged
tracebloc-release-train[bot] merged 1 commit into
stagingfrom
release-train/to-staging
Aug 5, 2026
Merged

release-train: develop -> staging#155
tracebloc-release-train[bot] merged 1 commit into
stagingfrom
release-train/to-staging

Conversation

@LukasWodka

@LukasWodkaLukasWodka commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Automated promotion by the release train (RFC-0008 D14). Head is the train-managed release-train/to-staging branch (a mirror of develop), so it never collides with a human PR. Merged only when the fr-gate is green.


Note

Low Risk
Governance/inventory YAML only; no runtime or auth changes, though caller-drift will fail if e2e-test-agent workflows are missing or mis-pinned on the audited branch.

Overview
Updates repo-inventory.yml for e2e-test-agent now that .github/workflows exists (e2e-test-agent#13), replacing the large block of UNREMEDIATED “no workflows directory” exemptions with required entries for the standard reusable callers and kanban copy workflows.

public-pii-gate moves to the shared private-repo exemption; wip-limit-check uses the org-wide “no callers” anchor. release_train stays false until release-train/repos.yml lists the repo (caller-drift guard enforces that coupling).

A short comment block documents the remediation date and that this is inventory catching up to RFC-BACKEND-1405, not a policy change.

Reviewed by Cursor Bugbot for commit d106c7f. Bugbot is set up for automated code reviews on this repo. Configure here.

…end#1552) (#153)
e2e-test-agent#13 added the .github/workflows directory this repo had lacked
since it was created on 2026-06-03, so nine `exempt` entries now assert the
opposite of reality — `exempt` means the caller must be ABSENT, and all nine
are present. Left alone, the next scheduled caller-drift run goes red for a
gap that has just been closed.
This was the largest single-repo block of UNREMEDIATED exemptions in the file:
11 of the 21 org-wide, where the next worst repo has 3. The harm they recorded
was not hypothetical — no issue or PR in the repo had ever reached the board,
which is why e2e-test-agent#11 sat open and unreviewed for seven days.
Flipped to the private-train-repo template, identical to frontend-app:
seven required callers, public-pii-gate exempt (private repo),
wip-limit-check exempt (retired org-wide), both copies required.
RFC-BACKEND-1405 D1 always required this — "Exempt never means ungoverned:
every repo keeps branch protection, the code-quality caller and kanban
auto-add" — so this is compliance catching up, not a change of policy.
release_train stays FALSE. caller-drift.py:562 verifies that field against
release-train/repos.yml, so flipping it before the repos.yml entry lands
would fail the guard. RFC-BACKEND-1552 D2 amends D1 to enrol the repo; the
flip to true follows the repos.yml entry.
The *no_workflows_directory_at_all anchor stays — devex-bootstrap still uses it.
Verified: `python3 scripts/caller-drift.py --inventory repo-inventory.yml
--source-dir .` exits 0, "No drift. Every repo read, every entry matched."
across all 20 repos.
Epic: tracebloc/backend#1552
RFC: tracebloc/rfcs#12
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@LukasWodka

Copy link
Copy Markdown
ContributorAuthor

bugbot run

@cursorcursorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit d106c7f. Configure here.

Comment threadrepo-inventory.yml
@tracebloc-release-traintracebloc-release-trainBot added gate-nudge Toggled by the release train to (re-)fire the fr-gate and removed gate-nudge Toggled by the release train to (re-)fire the fr-gate labels Aug 5, 2026
@tracebloc-release-train
tracebloc-release-trainBot merged commit a7fd254 into stagingAug 5, 2026
18 of 24 checks passed
LukasWodka added a commit that referenced this pull request Aug 6, 2026
… has one (backend#1586) (#169)
The WHY-THIS-FILE-EXISTS note closed with a present-tense claim - "there is
no closure caller there to route it" - that the body of the same file now
contradicts. e2e-test-agent's entry reads
kanban-closure-router.yml: required # kanban-closure-routing.yml
since the e2e-test-agent#13 remediation, and the caller is really there:
tracebloc/e2e-test-agent@develop ships .github/workflows/kanban-closure-routing.yml
resolving to tracebloc/.github/.github/workflows/kanban-closure-router.yml@main.
Note the filename - `kanban-closure-routing.yml`, not `-caller.yml` - which is
exactly the mismatch the MATCHING IS ON `uses:` CONTENT paragraph below warns
about, and exactly why a reader checking the header's claim by filename would
have concluded it was still true.
This is a file whose entire purpose is being the single source of truth that
caller-drift.yml enforces. A header that misstates the live state of a repo
the body governs is the one defect it cannot afford, even in a comment: the
guard checks the entries, nobody checks the prose, so the prose is where a
stale claim survives longest.
The fix keeps the motivating history and moves it into the past tense, because
e2e-test-agent#1 really did close without routing and that is the evidence
backend#1415 was built on. What changed is not the diagnosis, it is the repo:
the motivating gap is closed, the detection gap the file exists to fix is not.
Zero runtime impact - a comment. YAML parse re-verified (20 repos load).
Found on the 2026-08-05 develop->staging hop (.github mirror #155,
repo-inventory.yml:444), landed to staging under triage. Parent backend#1405.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@LukasWodka