Skip to content

Harden OpenAI evidence boundary before canary rollout - #13

Draft
qt314wink wants to merge 7 commits into
mainfrom
fix/openai-evidence-boundary-v2
Draft

qt314wink wants to merge 7 commits into
mainfrom
fix/openai-evidence-boundary-v2

Conversation

@qt314wink

Copy link
Copy Markdown
Contributor

Purpose

Follow-up hardening for the merged Automation v2 control plane before any repository uses OPENAI_API_KEY.

Fixes

  • disable persisted checkout credentials for both caller and control-plane checkouts
  • canonicalize evidence-path and require it to resolve inside the caller checkout
  • explicitly forbid evidence reads from .git
  • expand credential detection/redaction for GitHub token families and x-access-token
  • make Responses API text extraction tolerant of valid output item shapes and string / { value } text forms
  • expand the documentation JSON Schema so findings/opportunities match the runtime contract
  • add regression assertions to Control Plane QA

Authority / safety

This PR does not invoke the OpenAI API, deploy, merge, publish, spend, or modify product repositories. Keep it draft until QA and human review are complete.

Promotion gate

Only after this hardening is reviewed should a canary caller pin the reusable workflow to the immutable corrected commit SHA and exercise the newly-added organization secret.

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