Skip to content

ci: add LineageWeave hourly review-repair scheduler - #1288

Open
seonghobae wants to merge 2 commits into
mainfrom
feat/lineageweave-hourly-review-repair
Open

ci: add LineageWeave hourly review-repair scheduler#1288
seonghobae wants to merge 2 commits into
mainfrom
feat/lineageweave-hourly-review-repair

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds the missing per-repo hourly scheduler for ContextualWisdomLab/LineageWeave, matching the established bandscope/afipc/clearfolio pattern.
  • Dispatches the shared pr-review-fix-scheduler against main every hour at minute 4 with a two-hour same-head redispatch floor (Strix and coverage-source-tree routinely exceed one hour on a single head).

Why

  • docs/product-technical-gap-baseline.md in LineageWeave claims an org-level hourly control plane, but no LineageWeave-specific workflow existed; only other repos had one.

Open in Devin Review

Route the hourly PR queue sweep through the shared pr-review-fix-scheduler
with a two-hour same-head redispatch floor so Strix, coverage-source-tree,
and the full backend suite can finish before the next autofix dispatch.
@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 53 minutes.

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: Pro Plus

Run ID: adc0830f-0eb2-4558-91cf-06ae21c18f5d

📥 Commits

Reviewing files that changed from the base of the PR and between 0c6b9a6 and 2dae274.

📒 Files selected for processing (3)
  • .github/workflows/lineageweave-hourly-review-repair.yml
  • docs/doctoring/lineageweave-hourly-review-caller.md
  • tests/test_lineageweave_hourly_review_caller.py

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.

devin-ai-integration[bot]

This comment was marked as resolved.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact head 80dfb6e against main@0c6b9a6459c9dbdf5e23fb01df7a32a8a14964b3 is unchanged. The only failed check was scan-pr-queue run 32691900176, cancelled before steps started; no source failure was present. I requested a normal exact-head rerun. The diff is one bounded reusable-workflow caller for LineageWeave with explicit permissions, target, main base, hourly cadence, and two-hour retry floor. Please publish a substantive formal review for this exact head; no merge until required checks and independent approval are current.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent review

Review exact current head 80dfb6e against protected main@0c6b9a6459c9dbdf5e23fb01df7a32a8a14964b3. Walk through the reusable hourly caller, permissions, target repository, base branch, cadence, and retry floor. Publish a substantive Reviews API verdict on this exact SHA.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head remediation for 2dae274f01511d5f42f8d398f669b4f083e02c43:

  • changed the LineageWeave heartbeat from the Inkspan slot (47) to the reserved LineageWeave slot (4);
  • added the caller doctoring record and focused contract tests;
  • appended ContextualWisdomLab/LineageWeave to the organization OPENCODE_REPOSITORY_DISPATCH_TARGETS variable after verifying it was absent.

Merge-result validation: 1399 passed, 1 skipped, 16 subtests; statement and branch coverage 100%; interrogate --fail-under=100 scripts/ci; focused actionlint; and git diff --check all passed. The repair worker remains proposal-only; protected checks, independent approval, and merge governance are unchanged.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Devin Review found 2 new potential issues.

Open in Devin Review

Comment thread .github/workflows/lineageweave-hourly-review-repair.yml
Comment thread .github/workflows/lineageweave-hourly-review-repair.yml
@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head review disposition for 2dae274: corrected the PR description from the stale minute 47 claim to minute 4, matching the workflow and doctoring record. Live GitHub metadata confirms ContextualWisdomLab/LineageWeave default_branch=main, so base_branch: main is verified. No source workaround or permission expansion is needed.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent review

Review exact current head 2dae274 against protected main@0c6b9a6459c9dbdf5e23fb01df7a32a8a14964b3. The PR description and live LineageWeave default branch were corrected/verified, and local targeted tests plus actionlint pass. Read all three changed files and publish a substantive formal verdict on this exact SHA.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent review | Independent exact-current-head formal review requested for 2dae274f01511d5f42f8d398f669b4f083e02c43. Read the full current diff and current-head checks only; do not reuse predecessor approvals or hosted evidence. Report changed-file walkthrough, security/control-plane impact, test gaps, residual uncertainty, and a structured verdict.

@seonghobae
seonghobae enabled auto-merge (squash) August 24, 2026 05:20
@seonghobae

Copy link
Copy Markdown
Contributor Author

Current-head check observation for 2dae274: earlier scan-pr-queue runs were cancelled by newer per-PR scheduler activity, while the latest scan remains queued. No source failure is present; this is not yet D1-D6 deadlock evidence.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head RCA for 2dae274: Strix run 32692828269 failed closed after repeated NVIDIA NIM HTTP 429 responses and a fallback HTTP 404; no vulnerability report artifact was produced. The two scan-pr-queue cancellations are scheduler supersession, not source evidence. Rerun the failed Strix job normally; do not weaken the security gate.

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.

1 participant