Skip to content

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

Merged
seonghobae merged 1 commit into
mainfrom
docs/agents-rename-sweep
Aug 7, 2026
Merged

docs: update renamed repo references in AGENTS.md#350
seonghobae merged 1 commit into
mainfrom
docs/agents-rename-sweep

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Docs-only sweep: AGENTS.md ecosystem/sibling-component lists still referenced pre-rename repo names. Per ContextualWisdomLab/.github docs/CWL-MASTER-CONTEXT.md, the renames are:

  • cwl-idpkeyverse
  • waf-ids-ai-socwardnet
  • cwl-editorinkspan

This PR updates the stale name(s) in AGENTS.md only. No code changes.

🤖 Generated with Claude Code

@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: 3 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: f3a4b8ba-a553-416b-ab03-637b262978be

📥 Commits

Reviewing files that changed from the base of the PR and between fccc728 and bc482a0.

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

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

@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 cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 7dad79954dcfcfead89513c3f4bde89f6a0e9a95.

  • Head SHA: 7dad79954dcfcfead89513c3f4bde89f6a0e9a95

  • Workflow run: 31071682284

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: AGENTS.md"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: AGENTS.md"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 7dad79954dcfcfead89513c3f4bde89f6a0e9a95
  • Workflow run: 31071682284
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 7dad79954dcfcfead89513c3f4bde89f6a0e9a95.

  • Head SHA: 7dad79954dcfcfead89513c3f4bde89f6a0e9a95

  • Workflow run: 31071682284

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: AGENTS.md"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: AGENTS.md"]
  R1 --> V1["required checks"]
Loading

Copy link
Copy Markdown
Contributor Author

@coderabbitai review
@cwl-noema-review
@opencode-agent

Review the exact live head only. Verify AGENTS.md replaces only obsolete ecosystem names with keyverse, wardnet, and inkspan according to the central CWL master context, introduces no stale alias or unrelated governance change, and passes documentation/link/policy checks with zero unresolved threads. Review only; do not update the branch, merge, release, or alter protections.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown

Rate Limit Exceeded

@seonghobae have exceeded the limit for the number of chat messages per hour. Please wait 13 minutes and 30 seconds before sending another message.

@seonghobae
seonghobae enabled auto-merge (squash) August 7, 2026 00:40
@opencode-agent
opencode-agent Bot disabled auto-merge August 7, 2026 03:20
@seonghobae
seonghobae force-pushed the docs/agents-rename-sweep branch from 7dad799 to bc482a0 Compare August 7, 2026 06:11
@seonghobae
seonghobae marked this pull request as draft August 7, 2026 06:32
@seonghobae
seonghobae marked this pull request as ready for review August 7, 2026 06:33
@seonghobae
seonghobae dismissed opencode-agent[bot]’s stale review August 7, 2026 06:53

Obsolete exact-head review: it was submitted for head 7dad799 after a central coverage-evidence failure. The live head is bc482a0; CI, Security Scan, SAST Semgrep, fuzz, and CodeRabbit status are successful, and there are no unresolved review threads. A fresh exact-head review has already been requested.

@seonghobae
seonghobae merged commit d169ce2 into main Aug 7, 2026
35 checks passed
@seonghobae
seonghobae deleted the docs/agents-rename-sweep branch August 7, 2026 06:54
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