You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare Gittensory self-host for a beta-stable release candidate that other teams can safely run, without sharing our GitHub token budget or creating recurring rate-limit stalls.
Current state
The current self-host stack is functional and recently redeployed from main, with Redis, Qdrant, queue admission, scheduler backpressure, webhook coalescing, cache metrics, and observability improvements in place. The system now avoids blindly retrying into exhausted GitHub buckets, but rate-limit pressure can still park jobs for minutes at a time.
That means the next milestone is not simply more retry logic. The beta-stable milestone must reduce unnecessary GitHub work at the source, make token ownership explicit for external self-hosters, publish an image-first release path, and document exactly how operators should run, observe, and troubleshoot the stack.
Release target
Ship a beta/RC self-host image suitable for early external operators.
Recommended channel:
orb-v0.1.0-rc.1 or equivalent prerelease image tag
GitHub Release marked prerelease
no stable claim until rate-limit behavior, docs, and onboarding have survived real external usage
Non-negotiables
External self-hosters must use their own GitHub App installation tokens by default.
Orb telemetry must remain available without routing all GitHub API calls through our central broker.
Brokered Orb token mode must be explicitly managed/private-beta only.
The default compose/env path must be image-first and safe for first-time operators.
The queue must keep moving without wasteful polling or duplicate scheduled work.
Rate-limit metrics must identify whether pressure comes from webhooks, background regates, status reads, brokered calls, or operator misconfiguration.
Documentation must match the shipped image and defaults.
Second-pass priority order (reliability + rate-limit audit)
A live-system audit (VPS queue/DB/rate-limit data + error telemetry + an 8-way codebase deep-dive) surfaced the following, now tracked as #2533-#2543 above. #2527 (merged) already addressed the single largest GitHub-budget driver found (uncapped historical merged-PR file hydration). Suggested execution order for the rest, grouped by why they're sequenced this way:
Third-pass priority order (self-host review-gap audit)
An 8-lens audit of the self-host PR/issue review-gate system (gate rule dimensions, AI review capabilities, anti-abuse mechanisms, self-host ops, merge-time race conditions, competitive parity, config-as-code parity, and already-tracked roadmap work — cross-checked against open issues to avoid duplicates) surfaced the following, now tracked as #2550-#2568 above. This audit was directly triggered by a real production incident: PR #2479 and PR #2527 independently claimed migration number 0090, both merged clean, and only PR #2532's reactive patch caught it — the 4th occurrence of this exact bug class in project history. Suggested execution order:
Goal
Prepare Gittensory self-host for a beta-stable release candidate that other teams can safely run, without sharing our GitHub token budget or creating recurring rate-limit stalls.
Current state
The current self-host stack is functional and recently redeployed from
main, with Redis, Qdrant, queue admission, scheduler backpressure, webhook coalescing, cache metrics, and observability improvements in place. The system now avoids blindly retrying into exhausted GitHub buckets, but rate-limit pressure can still park jobs for minutes at a time.That means the next milestone is not simply more retry logic. The beta-stable milestone must reduce unnecessary GitHub work at the source, make token ownership explicit for external self-hosters, publish an image-first release path, and document exactly how operators should run, observe, and troubleshoot the stack.
Release target
Ship a beta/RC self-host image suitable for early external operators.
Recommended channel:
orb-v0.1.0-rc.1or equivalent prerelease image tagNon-negotiables
Child issues
Three-hour execution order
Second-pass priority order (reliability + rate-limit audit)
A live-system audit (VPS queue/DB/rate-limit data + error telemetry + an 8-way codebase deep-dive) surfaced the following, now tracked as #2533-#2543 above. #2527 (merged) already addressed the single largest GitHub-budget driver found (uncapped historical merged-PR file hydration). Suggested execution order for the rest, grouped by why they're sequenced this way:
Third-pass priority order (self-host review-gap audit)
An 8-lens audit of the self-host PR/issue review-gate system (gate rule dimensions, AI review capabilities, anti-abuse mechanisms, self-host ops, merge-time race conditions, competitive parity, config-as-code parity, and already-tracked roadmap work — cross-checked against open issues to avoid duplicates) surfaced the following, now tracked as #2550-#2568 above. This audit was directly triggered by a real production incident: PR #2479 and PR #2527 independently claimed migration number
0090, both merged clean, and only PR #2532's reactive patch caught it — the 4th occurrence of this exact bug class in project history. Suggested execution order:review-enrichment/src/analyzers/secret-scan.ts— this is a wiring fix, not new detection work.(Several audit findings were already tracked elsewhere and are NOT duplicated here — cross-referenced for visibility: plagiarism/copycat detection (#1969), CI-run cancellation on contributor_cap/blacklist close (#2462), AI-generated inline
suggestionrendering (#2139/#2140/#2141), review-memory/repeat-false-positive suppression (#1964 + #2178-#2181), changed-files summary table + finding severity taxonomy + reply-threaded Q&A (#2012).)Done when