[Parent] Safe outputs reliability and compiler backlog #53049

Summary

This parent issue tracks open work in the safeoutputs platform across compiler behavior, runtime tool registration, CLI UX, workflow integration, and documentation mapping. These issues are distinct defects, but they all belong to the same broader backlog: making safe outputs reliable and predictable for agentic workflows.

Included sub-issues

• safeoutputs JSON stdin mode reports invalid JSON as "No arguments provided" and prints help #52848 safeoutputs JSON stdin mode reports invalid JSON as "No arguments provided" and prints help
• safe outputs not working anymore after upgrading to v0.86.2 #52723 safe outputs stop working after upgrade to v0.86.2
• safe-outputs.github-token: no hook to inject a same-job mint step before safe_outputs checkout or in the conclusion job (masked STS tokens unusable) #52608 safe-outputs.github-token cannot support same-job minting for safe_outputs / conclusion jobs
• Designer Drift AuditMissing safe-output types in designer mapping tables #52424 Designer mapping tables are missing registered safe-output types
• safe-outputs.jobs.<id>.runs-on rejects the runner-group object form #52303 safe-outputs.jobs.<id>.runs-on rejects the runner-group object form
• call_workflow (and other renamed dynamic tools) get a duplicate, unwired generic tool that silently no-ops #52299 Renamed dynamic safe-output tools get a duplicate generic tool that silently no-ops

Rationale

All six issues target the same user-facing capability surface: declaring, compiling, exposing, and executing safe outputs correctly. Grouping them under one parent should make ownership and prioritization clearer than treating them as unrelated one-off bugs.

Generated by Issue Arborist · gpt54 · 40.2 AIC · ⊞ 11.9K · ◷

• expires on Aug 17, 2026, 9:19 PM UTC-08:00