Skip to content

feat: persist scoped project warning acceptances - #2434

Closed
jeremi wants to merge 2 commits into
mainfrom
feat/project-check-acceptances
Closed

jeremi wants to merge 2 commits into
mainfrom
feat/project-check-acceptances

Conversation

@jeremi

@jeremi jeremi commented Oct 25, 2026

Copy link
Copy Markdown
Member

Project checks now read optional check-acceptances.yaml entries containing an exact warning code, source scope, and required reason. Accepted warnings stay visible with their reasons and do not fail --deny-warnings; errors remain blocking. Acceptances persist until edited or removed, with no fingerprints, expiry, or automatic reapproval.

The shared implementation covers BReg, Evidence, Casework, Scheduling, Messaging, Coordinator, Document Store, Discovery, Manifest, and Render. It includes schema and editor support, configuration documentation, and regressions for malformed files, error non-acceptance, source scoping, and combined project/runtime reports.

Validation:

  • Shared YAML/config suites with all features; affected product check regressions; native CLI journeys, including BReg unrestricted action targets; CLI catalog and language-server tests.
  • Strict Clippy across affected packages and consumers, all targets; Cargo format check.
  • 222 configuration/editor/catalog script tests and 178 CI-classifier tests; convention, schema drift, identifier reproducibility/reference, and documentation checks.
  • Gitleaks: no leaks found.

Security review: this changes advisory reporting only. Runtime authorization and validation are unchanged. Negative tests confirm that acceptance cannot suppress errors, match another resource, import an external symlink, or omit its reason.

Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-25T18:40:25.376910Z 60f9c58 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 793b770a04

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread crates/registry-messagingctl/src/lib.rs Outdated
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 60f9c58684

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +67 to +68
cwd.and_then(|cwd| within_project(cwd.join(path)))
.or_else(|| within_project(root.join(path)))

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish external runtime sources from project-relative labels

When a check receives --project /path/to/project --runtime-config runtime.yaml from outside the project, and both the working directory and project contain runtime.yaml, this fallback assigns warnings from the external runtime file to the project's file. For example, Messaging's runtime_report preserves the CLI-relative source name, so an external platform.runtime-config.check-incomplete warning can inherit an acceptance authored for the project's runtime file and incorrectly pass --deny-warnings. Preserve the source-path context or normalize explicit runtime sources before matching; an existing external source must not be reinterpreted as a different project file. This violates the exact project-file scope required by CFG-DIAG-7 in the normative configuration conventions.

AGENTS.md reference: AGENTS.md:L131-L133

Useful? React with 👍 / 👎.

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