test(docs): keep CodeGraph agent guidance code-current - #333
Draft
seonghobae wants to merge 3 commits into
Draft
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finding
Fresh protected-main inventory found an executable documentation drift: the repository contains
.codegraph/, but protectedAGENTS.mdstill stated that no.codegraph/index existed and directed agents to fall back to plain text search. That contradicted the live repository capability and the standing code-exploration contract.This is a bounded Wardnet-owned developer-operability/documentation correction. It does not change gateway/SOC policy, Agent Artifact Admission, quarantine, egress, LLM orchestration, appguardrail, Context Graph or EA authority.
Hosted hostile RED
Exact test-only head
ae89b6f510bbeb4fc21c8ef0161e22779ece2fe8added one architecture-fitness regression while production/runtime source remained unchanged from protectedmain@f8260f1e03836039ff9463dd99fa982e4e270c4b.Hosted CI
34639380286, rust job103395055797, acquired GitHub-hosted Ubuntu 24.04, completed checkout/toolchain/formatting and all 142 existing library tests, then failed exactly incodegraph_guidance_matches_repository_statebecauseAGENTS.mddenied the live.codegraph/capability. This is the intended documentation-contract RED, not runner/bootstrap noise.Minimum causal repair
3ecb054ac9d4f30fcad888b6f0a926baafdbcb2echanged only the stale Code exploration paragraph inAGENTS.md: it now records the live.codegraph/index, directs agents to prefer CodeGraph/code-review-graph for caller/callee/impact exploration, and retains ordinary grep/ripgrep/Cargo/editor navigation only when the index cannot answer the query.The first post-fix CI
34639598846, rust job103395771168, exposed a test-oracle defect rather than a product defect: the assertion looked for case-sensitiveprefer CodeGraphwhile the repaired prose correctly began the sentence withPrefer CodeGraph. All existing runtime tests passed. Exact successor7a12973c9d844abb2bf91b1aabf0cbee0de75272makes only that regression assertion case-stable by normalizing the guidance text before matching; product/documentation semantics are unchanged.Exact-current evidence
Current head is exact
7a12973c9d844abb2bf91b1aabf0cbee0de75272on unchanged protected basemain@f8260f1e03836039ff9463dd99fa982e4e270c4b; GitHub reports the Draft mechanically mergeable.34639707970— SUCCESS.34639707972— SUCCESS.34639707971— SUCCESS.34639707968— non-passing central settlement, with clean exact-head scan. Initial compatibility job103396322555failed closed pending. One bounded rerun only (103397206132, attempt 2) also failed closed before terminal central evidence was visible. The later exact central identity run.github@34640269326, job103397993301, proves the Wardnet scan itself is clean: CodeQL initialize/analyze and the SARIF gate succeeded with exact logCODEQL_SARIF files=1 results=0 medium_plus=0, and SARIF artifactcodeql-dispatch-actions-34640269326-1/ id10279782945was preserved. The central job becomes FAILURE only afterward: target-head status publication is rejected with HTTP 403 for both available credentials, andWake exact CodeQL required jobfails becauseGH_TOKENis empty andWAKE_TOKEN_SOURCE=unavailable(Actions-capable CodeQL wake credential is unavailable.). This is central.githubcontrol-plane settlement, not a Wardnet source finding. Exact root cause/acceptance is handed to.github#1929comment5639822896; no further leaf rerun or source churn is justified until central settlement advances.Keep Draft until every then-live exact-head required gate is terminal-valid and live governance permits ordinary protected integration. No source churn solely to redispatch, central-workflow copy, synthetic status, force update, destructive rebase, self/model approval, gate weakening, predecessor-evidence promotion, or routine administrator bypass.