Skip to content

feat(automation): run Wardnet hourly NVIDIA NIM review repair - #1070

Open
seonghobae wants to merge 12 commits into
mainfrom
feat/wardnet-hourly-nvidia-nim-review-repair
Open

feat(automation): run Wardnet hourly NVIDIA NIM review repair#1070
seonghobae wants to merge 12 commits into
mainfrom
feat/wardnet-hourly-nvidia-nim-review-repair

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Buyer-perceivable gap

Hourly NVIDIA NIM review repair never scanned ContextualWisdomLab/wardnet. Live AI-SOC pull requests such as ContextualWisdomLab/wardnet#76 and #72 target protected main and stalled while Clearfolio, DiskSage, and fast-mlsirm received heartbeats.

Change

  • Thin scheduled caller at minute 7, base_branch: main, one dispatch, two-hour same-head retry.
  • Job-scoped id-token: write so the reusable scheduler can mint the OpenCode App fallback from GitHub OIDC.
  • Maps only PR_REVIEW_MERGE_TOKEN and OPENCODE_APPROVE_TOKEN. Never NVIDIA_NIM_API_KEY on the caller. Never COPILOT_GITHUB_TOKEN.
  • Independent pull_request / push / compileall path contracts.

Do not self-approve. Merge remains subject to two-approval + last-pusher ruleset.

Refs ContextualWisdomLab/wardnet#76 and ContextualWisdomLab/wardnet#72.


Open in Devin Review

@cursor

cursor Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 8 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: 0937538b-e94f-4355-b267-603ae5e8d6c6

📥 Commits

Reviewing files that changed from the base of the PR and between 5f3188b and 5554908.

📒 Files selected for processing (7)
  • .github/workflows/afipc-hourly-review-repair.yml
  • .github/workflows/hourly-nvidia-nim-review-repair.yml
  • .github/workflows/nonnest2-hourly-review-repair.yml
  • .github/workflows/originweave-hourly-review-repair.yml
  • .github/workflows/wardnet-hourly-review-repair.yml
  • docs/doctoring/wardnet-hourly-review-caller.md
  • tests/test_wardnet_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.

@seonghobae
seonghobae enabled auto-merge (squash) August 17, 2026 00:51
@seonghobae seonghobae moved this from Todo to In Progress in naruon Platform Roadmap Aug 17, 2026
@opencode-agent
opencode-agent Bot disabled auto-merge August 19, 2026 00:32
@seonghobae
seonghobae force-pushed the feat/wardnet-hourly-nvidia-nim-review-repair branch from 1a86d8d to e1d67c0 Compare August 19, 2026 09:58
@seonghobae

Copy link
Copy Markdown
Contributor Author

Rebased onto current main 9e9f59f3; resolved shared hourly-contract conflicts while preserving Wardnet paths. Caller tests passed (6 passed); actionlint passed on both changed workflows; diff check passed. Project #1 is In Progress.

@seonghobae
seonghobae force-pushed the feat/wardnet-hourly-nvidia-nim-review-repair branch from 1750e43 to cf24032 Compare August 19, 2026 14:55
@seonghobae

Copy link
Copy Markdown
Contributor Author

Current-head maintenance: rebased the Wardnet hourly caller onto main bbedc1a. Exact head: cf24032. Caller contract tests: 34 passed; actionlint and git diff --check passed. Protected hosted checks remain; no bypass used.

@opencode-agent opencode-agent 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.

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/wardnet-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/wardnet-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1070 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: cf24032bba23411a34fc323d5c2fcc1b9351f9f5
  • Workflow run: 32291041280
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 5554908ce32c25e565f0c40f711110814e6094ad
  • Workflow run: 33005282858
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for 5554908ce32c25e565f0c40f711110814e6094ad.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (5 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (5 files)"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Docs: wardnet-hourly-review-caller.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: wardnet-hourly-review-caller.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["Test: test_wardnet_hourly_review_caller.py"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test: test_wardnet_hourly_review_caller.py"]
  R3 --> V3["targeted test run"]
Loading

Buyer-facing AI-SOC PRs on ContextualWisdomLab/wardnet#76 and #72 target
main while hourly repair scanned other products. Add a minute-7 caller
with job-scoped id-token: write, two-hour retry, and no COPILOT_GITHUB_TOKEN.
@seonghobae
seonghobae force-pushed the feat/wardnet-hourly-nvidia-nim-review-repair branch from cf24032 to d3376a4 Compare August 20, 2026 01:24
@seonghobae

Copy link
Copy Markdown
Contributor Author

Rebased onto current origin/main c47bee5 and preserved the existing hourly caller path set plus the Wardnet AI-SOC documentation/changelog/runtime-budget coverage.

Current HEAD: d3376a4

Validation on this HEAD:

  • pytest -q tests/test_wardnet_hourly_review_caller.py tests/test_hourly_scheduler_runtime_budget.py: 9 passed
  • actionlint: caller and hourly dispatcher passed
  • compileall and git diff --check passed

@OpenCode review this exact HEAD after the rebase.

Copy link
Copy Markdown
Contributor Author

@opencode-agent Review the current exact head of the Wardnet hourly review-repair caller. Verify the thin caller targets ContextualWisdomLab/wardnet protected main, delegates only to the bounded central scheduler, dispatches at most one current-head repair with the configured retry floor, preserves non-cancelling single-flight execution, grants only read contents plus job-scoped OIDC, maps only established scheduler credentials, and exposes no model, merge, release, or protection authority. Reacquire exact-head quality/security/supply-chain checks and submit the formal review without altering the branch.

@seonghobae
seonghobae enabled auto-merge (squash) August 20, 2026 06:19
@opencode-agent
opencode-agent Bot disabled auto-merge August 20, 2026 07:00
@seonghobae

Copy link
Copy Markdown
Contributor Author

Current-head review refresh for exact commit b1cbe69d60a22f33fa3aaff82c4cd7efccf888ce: prior OpenCode REQUEST_CHANGES referenced cf24032b... and is stale. Please review only this exact HEAD, revalidate Wardnet caller scope, current required Checks, and mergeability with @opencode-agent; do not reuse predecessor evidence.

@seonghobae
seonghobae dismissed opencode-agent[bot]’s stale review August 20, 2026 09:41

Dismiss stale review: review commit cf24032 is not current PR head b1cbe69; current-head review is required.

@opencode-agent opencode-agent 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.

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/wardnet-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/wardnet-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1070 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: 148a3e0b3766438797ab728af2bd95dd9cd7c674
  • Workflow run: 32398826208
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

Copy link
Copy Markdown
Contributor Author

Current-head merge repair pushed normally at 5f899a47 after reconciling the stale main base; the Wardnet caller, architecture record, and exact-artifact SBOM documentation are preserved. Please observe Checks for this exact head; no merge bypass is used.

devin-ai-integration[bot]

This comment was marked as resolved.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head lock repair pushed as 9c752db from 5f899a4. Updated the hashed pip audit runtime from pip 26.1.2 to pip 26.2.1 with exact hashes, without changing the hourly caller implementation. The same lock has already passed local pip-audit in this maintenance loop; hosted checks and exact-head approval must be re-evaluated. No bypass or force push was used.

devin-ai-integration[bot]

This comment was marked as resolved.

@opencode-agent opencode-agent Bot added priority: medium Normal-priority or P2 work status: blocked Blocked by conflict, dependency, or required prerequisite type: feature New or expanded product capability labels Aug 22, 2026

@opencode-agent opencode-agent 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.

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/wardnet-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/wardnet-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1070 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (5 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: 9c752db19fa91b320a74da6c8bd0fbe6d03bce1e
  • Workflow run: 32907591958
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (5 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

@opencode-agent opencode-agent 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.

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/wardnet-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/wardnet-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1070 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/wardnet-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (5 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: 9c752db19fa91b320a74da6c8bd0fbe6d03bce1e
  • Workflow run: 32926597881
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (5 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs (2 files)"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

# Conflicts:
#	.github/workflows/hourly-nvidia-nim-review-repair.yml
#	AGENTS.md
#	CHANGELOG.md
#	docs/automation/hourly-review-repair.md
devin-ai-integration[bot]

This comment was marked as resolved.

@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 0 new potential issues.

Open in Devin Review

@opencode-agent opencode-agent 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.

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for 5554908ce32c25e565f0c40f711110814e6094ad.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (5 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (5 files)"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Docs: wardnet-hourly-review-caller.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: wardnet-hourly-review-caller.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["Test: test_wardnet_hourly_review_caller.py"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test: test_wardnet_hourly_review_caller.py"]
  R3 --> V3["targeted test run"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: medium Normal-priority or P2 work status: blocked Blocked by conflict, dependency, or required prerequisite type: feature New or expanded product capability

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

1 participant