ci: add content validation and secret scan - #4
Conversation
🤖 Automated Review PanelReviewer A — GPT-5.6-terraAPPROVE — no material findings. The workflow meets the requested stable job names, trigger/permission constraints, safe no-match behavior, and full-history secret scan. Reviewer B — Gemini 3 FlashINCONCLUSIVE (environment limitation) — the reviewer was given the diff context but its isolated workspace did not contain the runner worktree, so it could not inspect files directly. It reported no workflow-semantic finding. Local verification independently passed: |
Auto-Merge Gate approvalConfidence: 0.93 The CI workflow directly implements COD-449: deterministic YAML, JSON, and TOML validation plus a full-history, redacted Gitleaks scan. Scope is limited to the workflow and its YAML lint configuration. Both required checks succeeded ( |
Summary
Adds the standard content-repository CI for
agent-context:yamllint), JSON (jq), and TOML (tomllib) validation. JSON/TOML discovery safely succeeds when no matching files exist.Validation
yamllintpassed for the manifest and workflow.actionlintv1.7.7 passed.gitleaks detect --source . --no-git --verbose --redactfound no leaks.git diff --checkpassed.The historical acceptance step to update PR #2 is inapplicable: PR #2 merged before this CI branch. Future agent-context PRs now have the required check names for gate evaluation.
Closes COD-449.