Problem
Schema Consistency Check (#36193, finding #10) found that the expires default is asymmetric across sibling safe-output configs in pkg/parser/schemas/main_workflow_schema.json:
create-discussion.expires sets default: 7
create-issue.expires has no default (null)
This is surprising and undocumented divergence — a workflow author reasonably expects the two to behave the same.
Suggested fix
Decide the intended default and apply it consistently:
- If issues should also auto-expire → add
default: 7 to create-issue.expires.
- If the divergence is intentional → document why in the schema description so it isn't flagged as a bug each audit cycle.
Success criteria
expires defaults are consistent across create-issue / create-discussion, or the difference is explicitly documented.
Effort
~20 min. Suggested agent: schema maintenance agent.
Source: DeepReport 2026-06-01, finding #10 of #36193.
Generated by 🔬 DeepReport - Intelligence Gathering Agent · opus48 1.6M · ◷
Problem
Schema Consistency Check (#36193, finding #10) found that the
expiresdefault is asymmetric across sibling safe-output configs inpkg/parser/schemas/main_workflow_schema.json:create-discussion.expiressetsdefault: 7create-issue.expireshas no default (null)This is surprising and undocumented divergence — a workflow author reasonably expects the two to behave the same.
Suggested fix
Decide the intended default and apply it consistently:
default: 7tocreate-issue.expires.Success criteria
expiresdefaults are consistent acrosscreate-issue/create-discussion, or the difference is explicitly documented.Effort
~20 min. Suggested agent: schema maintenance agent.
Source: DeepReport 2026-06-01, finding #10 of #36193.