ci(security): use central dependency review

[seonghobae]

Current ownership boundary

This PR correctly removes the repository-local dependency-review implementation and makes ScopeWeave a thin caller of the canonical ContextualWisdomLab/.github reusable workflow. The caller is pinned to exact commit f43dcb884be5a0efc61611b5c8cb83c4c7735995, preserves fail_on_severity: moderate, and keeps pull-request concurrency isolated from manual runs.

Fleet finding — immutable release prerequisite

Fresh central-owner inventory on 2026-09-05 shows ContextualWisdomLab/.github currently has zero GitHub Releases. The exact SHA pin is immutable as a Git object, but the ecosystem contract requires the canonical workflow generation to be published and traceable as a versioned immutable owner release before consumers promote it as a released foundation dependency.

That is an owner prerequisite, not a reason to duplicate the workflow back into ScopeWeave or weaken dependency review. This PR has therefore been returned to Draft while retaining its valid thin-caller delta.

RED:

• ScopeWeave exact head 135ba0f0652b941282caec243b136e395d928a0d consumes central workflow commit f43dcb884be5a0efc61611b5c8cb83c4c7735995;
• .github has no canonical GitHub Release that identifies this workflow generation and its release evidence;
• local actionlint/config tests prove caller syntax/ownership shape, not publication provenance or released-contract status.

GREEN before Ready:

1. .github owner publishes a canonical immutable release containing the dependency-review reusable workflow generation, with version/CHANGELOG and applicable security/SBOM/provenance/rollback evidence;
2. the release/tag resolves to the exact workflow commit consumed here, or this caller advances normally to the released exact commit SHA;
3. ScopeWeave's ownership regression pins that released immutable SHA and the caller preserves moderate severity/fail-closed behavior;
4. this unchanged consumer head then obtains terminal current CI/security/SAST/CodeQL/review evidence under live protection.

Do not replace the owner prerequisite with a mutable branch/tag, local workflow copy, bypass, source-neutral retrigger, or weaker dependency-review policy.

Existing verification

• actionlint .github/workflows/dependency-review.yml
• git diff --check
• uv run --with pytest pytest -q tests/config — 3 passed

These remain useful source-level evidence but are not the release gate.

[coderabbitai]

Warning

Review limit reached

Next included review available in 57 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: 3620d40a-e21d-4403-ae3e-6b6ae603cc4a

📥 Commits

Reviewing files that changed from the base of the PR and between 2c32887 and 135ba0f.

📒 Files selected for processing (2)

• .github/workflows/dependency-review.yml
• tests/config/test_strix_static_repo_adaptations.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

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-04T21:47:19.740124Z	135ba0f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.