Skip to content

docs(gap-baseline): record Actions congestion and noema/strix hot-file divergence - #1819

Merged
seonghobae merged 3 commits into
mainfrom
docs/gap-baseline-actions-congestion-and-hot-file-divergence-20260904
Sep 4, 2026
Merged

docs(gap-baseline): record Actions congestion and noema/strix hot-file divergence#1819
seonghobae merged 3 commits into
mainfrom
docs/gap-baseline-actions-congestion-and-hot-file-divergence-20260904

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Updates the product/technical gap baseline with exact organization-wide Actions evidence and reconciles the original hot-file-divergence snapshot with current protected main.

  • A repository-by-repository REST census across all 74 visible organization repositories found 5,991 queued and 47 in-progress runs. Targeted cleanup removed only review/security runs stuck in progress for more than six hours; the queue fell as low as 5,471 while active admission recovered to 45–50. This proves renewed throughput, not backlog elimination.
  • The organization-wide startup_failure census found 404 historical rows in 56 repositories. Every repository's newest row was the retired central CodeQL PR workflow; the latest was 2026-09-03T03:26:53Z. Central PRs feat(codeql): add the native CodeQL scan dispatch handler (not wired up yet) #1776 and feat(codeql): rewrite codeql-pr.yml as dispatch+poll (not wired to the ruleset) #1778 replaced that unsupported required-workflow form with native dispatch/poll execution, and a current wardnet PR materialized both Actions and Rust CodeQL jobs. No later startup-failure type was observed.
  • Preserves the original noema/Strix hot-file collision evidence while incorporating all central workflow changes merged since the PR opened.
  • Corrects the hourly review-repair description to match protected code: discover up to 200 PRs, deeply inspect a deterministic rotating window of 50, and stop after one permitted dispatch.

Verification

  • uv run pytest -q tests/test_product_technical_gap_baseline.py -> 5 passed
  • git diff --check -> clean

Scope

Documentation only. No workflow or runtime behavior is introduced by this PR; the merged central fixes and observed runtime evidence are recorded without claiming that the remaining queue is cleared.

…e divergence

This round's org-wide open-PR sweep found two significant, non-PR-specific
patterns worth a durable record:

1. Severe central Actions capacity congestion (1719 queued workflow runs vs
   2 in_progress at snapshot time; individual jobs queued 20min-2.5h+) --
   confirmed live via actions_list, not the already-tracked
   QUEUE_SATURATION_CHICKEN_EGG pattern. No fix attempted; a merely-queued
   job is never re-run per the standing directive.

2. scripts/ci/noema_review_gate.py and .github/workflows/strix.yml /
   security-scan.yml are active multi-PR hot-file collision zones: 6+ open
   PRs (#1198, #1606, #1589, #939, #1009, #1674, #1158) each carry a
   materially different, mutually incompatible design for the same
   mechanism, and main has independently evolved yet another version in
   several cases. #1674 additionally demonstrates a more dangerous failure
   mode than a marked conflict: a clean git merge silently dropped a real
   fail-closed step with no conflict marker at all, caught only by running
   the full suite before push.

Two PRs (#1187, #933) and one PR (#1685) were successfully merge-conflict
repaired and pushed this round with full green suites -- their fixes are
append-only doc drift or one confirmed-stale carried-forward test
assertion, not touching the contested files above.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4
@coderabbitai

coderabbitai Bot commented Sep 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 22 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 61d0a2f7-d02c-4daf-acd8-781fd5f501f7

📥 Commits

Reviewing files that changed from the base of the PR and between f0dd406 and d57f2ad.

📒 Files selected for processing (1)
  • docs/product-technical-gap-baseline.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

claude and others added 2 commits September 4, 2026 03:57
…test-bug fix

Follow-up to this same PR's original entry: this round's continued PR sweep
found #1065 and #1681 conflicting on strix.yml/noema_review_gate.py (same
pattern as the 7 PRs already documented), plus #1271 and #1231 conflicting on
scripts/ci/pr_review_merge_scheduler.py -- confirming the #1803 facade/core
split is now also an active collision surface (4,074-line monolith on each
PR's branch vs. a 241-line facade + separately-evolving core file on main).
Evidence-based comments were left on all 4; no guessed resolution was pushed.

Also records one genuine pre-existing (not merge-caused) test bug found and
fixed while merge-repairing #1655: a jq trailing-newline off-by-one in a new
E2E test, and a coverage gap in opencode_review_normalize_output.py's new
needs-info wrapper (branches only exercised via subprocess, invisible to
coverage.py). Both fixes are test-only, pushed as part of #1655 itself.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4
# Conflicts:
#	docs/product-technical-gap-baseline.md
@seonghobae
seonghobae merged commit f8c3b30 into main Sep 4, 2026
4 of 16 checks passed
@seonghobae
seonghobae deleted the docs/gap-baseline-actions-congestion-and-hot-file-divergence-20260904 branch September 4, 2026 07:18
Sign up for free to 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.

2 participants