Skip to content

docs(#1946): add undefined-propagation checklist to AGENTS.md - #1948

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/1946-undefined-propagation-checklist
Open

fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/1946-undefined-propagation-checklist

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

What:

Add undefined-propagation completeness guidance to AGENTS.md in two places:

  1. 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.

  2. 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_string guards 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

  • Branch is not main/master (agent/1946-undefined-propagation-checklist)
  • Secret scan passed (gitleaks — fe20bff24b1cafdbcb92b004dacada2ea94ee825..HEAD)
  • PR body secret scan passed (gitleaks — no-git)
  • Final PR description secret scan passed (gitleaks — no-git)

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>
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Oct 28, 2026
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner October 28, 2026 14:25
@coderabbitai

coderabbitai Bot commented Oct 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3f612bdd-5008-457a-8b69-84f6f8db90da

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@qodo-for-conforma

Copy link
Copy Markdown

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 review

Powered by Qodo

@qodo-for-conforma

Copy link
Copy Markdown

PR Summary by Qodo

Document Rego undefined-propagation risks in policy reviews

📝 Documentation 🕐 Less than 10 minutes


AI Description

• Explain how undefined propagation can silently bypass Rego policy checks.
• Add a review checklist for missing, wrong-typed, and malformed input, with mitigation examples.
Diagram

graph TD
  A["Rego semantics"] --> B["Review checklist"] --> C{"Input malformed?"} -->|yes| D["Guard or validate"] --> E["Policy behavior"]
  F["New policy rule"] --> B
  C -->|no| E
Loading
High-Level Assessment

Adding both a semantic explanation and an actionable checklist item fits the existing AGENTS.md review guidance. A separate document would make this check less visible during policy-rule review.

Files changed (1) +15 / -0

Documentation (1) +15 / -0
AGENTS.mdAdd undefined-propagation guidance for Rego reviewers +15/-0

Add undefined-propagation guidance for Rego reviewers

• Explains that missing or wrong-typed field access can silently leave a rule body without a result. Adds a checklist to examine missing fields, unexpected types, and malformed structures in new deny/warn rules, with guard and validation options and references to PR #1871.

AGENTS.md

@fullsend-ai-review

Copy link
Copy Markdown

🤖 Review · ⚠️ Cancelled · Ended 2:26 PM UTC

Commit: 2d9a94f · View workflow run →

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 28, 2026
@fullsend-ai-review

Copy link
Copy Markdown

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

A 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.

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium


Labels: Documentation-only PR modifying AGENTS.md, matching the consistent labeling pattern for AGENTS.md documentation issues.

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment documentation Improvements or additions to documentation labels Oct 28, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation ready-for-review Triggers review agent dispatch requires-manual-review Review requires human judgment risk/moderate PR risk: moderate size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add undefined-propagation completeness check to AGENTS.md review checklist

0 participants