Skip to content

docs: update renamed repo references in AGENTS.md - #89

Closed
seonghobae wants to merge 1 commit into
mainfrom
docs/agents-rename-sweep
Closed

docs: update renamed repo references in AGENTS.md#89
seonghobae wants to merge 1 commit into
mainfrom
docs/agents-rename-sweep

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Update the stale waf-ids-ai-soc ecosystem reference in AGENTS.md to the repository's current name, wardnet, using ContextualWisdomLab/.github/docs/CWL-MASTER-CONTEXT.md as the organization source of truth.

Scope

  • Documentation only
  • One AGENTS.md ecosystem-list entry
  • No runtime, dependency, workflow, or API changes

Validation

The current diff contains only the exact repository-name replacement. Repository Tests, Fuzz, Security, and Security Scan pass on the current head. The repository-wide Semgrep failure is the pre-existing base-branch finding set repaired by PR #76, not a finding introduced by this documentation change.

All required checks and repository merge rules remain mandatory.

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c7ffc6a9-d7d4-4429-8ab9-791e601a013a

📥 Commits

Reviewing files that changed from the base of the PR and between 6841b71 and c0af464.

📒 Files selected for processing (1)
  • AGENTS.md

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

@seonghobae
seonghobae enabled auto-merge (squash) August 4, 2026 05:47

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #88. Both changes are documentation-only corrections in the same AGENTS.md ecosystem list; #88 now contains the keyverse role correction and the waf-ids-ai-socwardnet rename together, reducing duplicate checks and avoiding a predictable same-file merge conflict.

@seonghobae seonghobae closed this Aug 4, 2026
auto-merge was automatically disabled August 4, 2026 06:18

Pull request was closed

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