Skip to content

Separate policy routing metadata#248

Open
pengfei-threemoonslab wants to merge 1 commit into
mainfrom
codex/policy-routing-metadata
Open

Separate policy routing metadata#248
pengfei-threemoonslab wants to merge 1 commit into
mainfrom
codex/policy-routing-metadata

Conversation

@pengfei-threemoonslab

Copy link
Copy Markdown
Contributor

Summary

  • Add findings[].policy_routing for policy-pack owner/reviewer/approval routing metadata and bump the report schema to 0.28.
  • Remove policy routing keys from Finding.evidence so routing-only changes do not affect fingerprints, suppressions, baselines, or release decisions.
  • Preserve v0.27 routing-evidence fingerprints for old baseline matching and stale-baseline checks.
  • Regenerate report schema, docs/public surfaces, llms-full.txt, and sample report goldens.

Validation

  • python scripts/generate_schemas.py
  • pytest tests/test_policy_packs.py tests/test_schema_boundaries.py tests/test_reports.py tests/test_baseline_integrity.py tests/test_privacy.py tests/test_release_decision.py
  • pytest tests/test_public_surface_contract.py tests/test_docs_links.py
  • ruff check src/agents_shipgate tests tools scripts
  • PYTHONPATH=src python -m agents_shipgate check --agent codex --workspace . --format codex-boundary-json

shipgate check returned decision=warn and completion_allowed=true; the warning is that skills/agents-shipgate/SKILL.md is an undeclared capability surface in shipgate.yaml, so verify cannot fully gate that surface until it is declared.

@pengfei-threemoonslab pengfei-threemoonslab changed the title [codex] Separate policy routing metadata Separate policy routing metadata Jun 30, 2026
@pengfei-threemoonslab pengfei-threemoonslab marked this pull request as ready for review June 30, 2026 01:35
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