Repository navigation
docs(#1946): add undefined-propagation checklist to AGENTS.md - #1948
fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
Add guidance for detecting Rego's undefined-propagation failure mode, where accessing a missing or wrong-typed field causes a rule body to silently produce no result — effectively bypassing the policy check. Two additions: 1. "Undefined propagation" bullet in the Rego Evaluation Model section explaining the silent-pass behavior when fields are missing or wrong-typed. 2. "Undefined-propagation completeness" checklist item in the Review Checklist for New Policy Rules, with concrete guidance to verify rule behavior under missing, wrong-typed, and malformed-structure inputs. References is_object/is_array/is_string guards and PR #1871 examples (malformed_params, _malformed_workspaces, input_format). Note: make fmt/lint could not run (sandbox restriction). Only AGENTS.md changed — no Rego code affected. Closes #1946 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewPowered by Qodo |
PR Summary by QodoDocument Rego undefined-propagation risks in policy reviews
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
|
🤖 Review · Commit: |
|
<!-- fullsend:risk-assessment --> DetailsA minimal docs-only bot PR adding 15 lines to AGENTS.md scores moderate (2) because AGENTS.md is a protected path with high multi-author contention (9 authors in 90d) and change-coupling history, slightly elevating risk above low despite the tiny, trivially-reversible nature of the change. |
ReviewFindingsMedium
Labels: Documentation-only PR modifying AGENTS.md, matching the consistent labeling pattern for AGENTS.md documentation issues. <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> |
What:
Add undefined-propagation completeness guidance to AGENTS.md in two places:
Rego Evaluation Model section — new "Undefined propagation" bullet explaining that accessing a missing or wrong-typed field causes a rule body to silently produce no result, effectively bypassing the policy check.
Review Checklist for New Policy Rules — new "Undefined-propagation completeness" checklist item with concrete guidance to verify rule behavior under (a) missing fields, (b) wrong-typed fields, and (c) malformed internal structure. References
is_object/is_array/is_stringguards and PR fix(EC-2235): reject malformed Pipeline and Task values #1871 examples (malformed_params,_malformed_workspaces,input_format).Why:
PR #1871 exposed 4 undefined-propagation gaps in a single PR, all caught by a human reviewer and missed by automated review. The existing Rego Evaluation Model section (added per #1757) covers Rego semantics but does not warn about the inverse problem: false negatives from undefined propagation. This change extends both the conceptual guidance and the review checklist to cover this failure mode, following the established pattern of prior review-checklist issues (#1760, #1799, #1801, #1802).
Tickets:
Closes #1946
Post-script verification
agent/1946-undefined-propagation-checklist)fe20bff24b1cafdbcb92b004dacada2ea94ee825..HEAD)