release-train: develop -> staging

[LukasWodka]

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

Medium Risk
Changes required CI gate behavior (pagination and longer waits) for all repos using Bugbot gate; incorrect pagination logic could still block or mis-evaluate large PRs, though selftests and mutations target that path.

Overview
Bugbot review gate now paginates GraphQL checkSuites and reviewThreads so PRs with more than 100 threads or suites are no longer permanently refused as “truncated” (backend#3530). Shared query fragments, follow-up pages, bounded cursor handling, and a pageInfo self-check back the new follow_pages path; selftests and mutation cases cover it.

The reusable workflow raises wait budgets: default wait-seconds 900 → 1500 and job timeout-minutes 20 → 30, with rationale tied to slow/outlier Bugbot runs and gate timeouts mistaken for findings.

Fleet inventory updates: docs marked private; Bugbot issue refs normalized to .github#277; new org-config repo entry (private seed of .github operational logic, protection/callers aligned with peers).

^{Reviewed by Cursor Bugbot for commit 1316a49. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

bugbot run

[cursor]

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

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

^{Reviewed by Cursor Bugbot for commit 1316a49. Configure here.}

[LukasWodka]

Promoted with 1 open Medium/Low Bugbot finding(s), per the severity policy in release-train's README (High stops the line; Medium/Low are recorded and ship, at both hops):

Selftest loop breaks after first connection, hiding broken stripper

This is a second look at once-reviewed code -- it passed per-feature review on the source branch, and has NOT had functional review yet (that happens on staging). Fix forward on develop if any is real.

What the train did with each:

• Selftest loop breaks after first connection, hiding broken stripper - filed as https://github.com/tracebloc/backend/issues/3653, thread resolved by the train.

[LukasWodka]

Functional review — staging batches of 2026-09-10 (10:43 and 14:49 hops) — PASS (FR reviewer: LukasWodka; self-signoff per RFC-BACKEND-1405 D6)

Decision: PASS, by the reviewer's instruction at 15:45 UTC. All 132 cards that sat at FR on staging — the 86 held since the 10:43 hop plus the 46 this hop pushed — are advanced to Ready for prod.

What changed since the hold. The 12:00 hold was not about this batch: the edge refused every training envelope with NEVER_STEADY_STATE because chart 1.9.109 (kubelet reservation) plus the runtime's v3 envelope contract left a 2-core / 8 GiB node 100 m and 682 MiB short of the smallest envelope. The interim control-plane trim (tracebloc/client#1032, chart 1.9.112, render 650 m / 2272 MiB with the collector counted) merged at 14:47 UTC and reached staging with this hop at 15:37 UTC; rc v1.9.112-rc.1 is published.

Evidence at signoff.

• Staging tips: every repo in the hop is on its 15:20–15:37 UTC mirror; the e2e-test-agent mirror was HELD by the train on a Bugbot High (teardown ceiling) and its harness stays at the 11:22 tip — that affects nothing under review here.
• Artifact channels (fr-assist, 11:34 UTC run 34471966935): all OK, 1 SKIPPED (credentials).
• Frontend smoke on staging (11:47 UTC, 34473123260): green.
• Journey battery on the corrected chart is IN FLIGHT at signoff (dispatched 15:39 UTC on the staging harness): baseline https://github.com/tracebloc/e2e-test-agent/actions/runs/34497041338 and the 16-task fleet https://github.com/tracebloc/e2e-test-agent/actions/runs/34497050908. The verdict that matters is Train a model scheduling on the 2-core k3d node. It will be appended below when the runs finish; if it is red, the prod hop does not proceed and the cards come back.

Things this evidence cannot tell you (README → Functional review): interactive/TTY behaviour, per-ticket behaviour, anything at or after a failing step, and any step a run skipped.

[LukasWodka]

Correction to the evidence paragraph above (15:50 UTC). The two journey runs named there (34497041338, 34497050908) were dispatched with chart_source/chart_ref blank, which installs the published chart from the Helm index — the index is stable-only, so they exercise chart 1.9.109, the customer path as it is on prod today, not the 1.9.112 candidate on staging. They are a control, not the proof. The proof runs are the candidate-chart baselines dispatched with chart_ref=v1.9.112-rc.1: https://github.com/tracebloc/e2e-test-agent/actions/runs/34498185079 (tabular_classification) and the image_classification twin dispatched a minute later. The fleet workflow has no chart_ref input, so the candidate is proven on the baseline cell only. Verdicts will be appended here; the prod hop waits for them.

[LukasWodka]

Journey verdict appended (16:20 UTC) — the fix is confirmed on staging's candidate chart.

run	chart installed	node arithmetic (k3d-tracebloc-server-0)	Train a model
34498185079 tabular_classification	client-1.9.112-rc.1 (candidate)	allocatable 1900m / 5538Mi, requested 750m / 2284Mi, leaves 1150m / 3254Mi → envelope fits	✅ experiment COMPLETED, leaderboard found
34498269145 image_classification	client-1.9.112-rc.1 (candidate)	same: leaves 1150m / 3254Mi → fits	✅ experiment COMPLETED, leaderboard found
34497041338 control, published chart	client-1.9.109 (prod today)	requested 1000m / 3148Mi, leaves 900m / 2390Mi → refused	❌ UnschedulableEnvelope at 15:54 UTC
34497050908 control fleet, published chart	client-1.9.109	same refusal on 14 legs; 1 leg died earlier on a cosign download inside the installer	❌ 15/16 red at Train

Same node, same runtime image, same envelope; only the chart differs. The published chart (prod) still refuses; the candidate admits and trains to completion. Prod hop proceeds so 1.9.112 supersedes 1.9.109.