[Schema Consistency] Schema Consistency Audit — 2026-03-23

[github-actions[bot]]

Overview

Schema consistency audit for 2026-03-23 (run 43, day 82 → proven strategy). Analysis focused on new changeset features (safe-outputs.actions, safe-outputs.scripts, blocked deny-lists, label_command trigger) and cross-referencing schema definitions against Go implementation and documentation.

• New findings this run: 2
• Confirmed persisting issues: 6 (from previous runs)
• Strategy: New Changeset Features Audit + safe-outputs.actions/scripts Schema Completeness Check
• Workflow run: §23431625170

---

Critical Issues

Issues that could cause runtime failures or mislead users in high-impact ways.

1. update-discussion labels is a Dead Feature (persisting, strategy-31)

Schema (main_workflow_schema.json): defines labels: and allowed-labels: fields under safe-outputs.update-discussion.
Docs (safe-outputs.md): documents it with YAML examples ("Updates discussion title, body, or labels").
Reality: LLM tool definition in both pkg/workflow/js/safe_outputs_tools.json and actions/setup/js/safe_outputs_tools.json has no labels parameter — the LLM can never send labels. update_discussion.cjs has zero label-handling code. safe_outputs_validation_config.go uses requiresOneOf: title, body with no labels field.

Impact: Users configuring update-discussion with label management expectations will silently get no label changes.

2. proxy-args Missing from MCP Schema (persisting, strategy-30)

Code: proxy-args is parsed at the top level of MCP server configs via mcp_config_custom.go:661 (config.GetStringArray) and tested at top level in mcp_config_comprehensive_test.go:903.
Schema: proxy-args only exists in the deprecated network.proxy-args path in main_workflow_schema.json. The $defs/stdio_mcp_tool definition uses additionalProperties: false, so any workflow using proxy-args at the top-level MCP server config will fail schema validation even though the code accepts it.
Both schemas affected: main_workflow_schema.json and mcp_config_schema.json.

3. Wrong Codemod ID in MCP Tools and Docs (persisting, strategy-32)

mcp_tools_management.go:171 and gh-aw-as-mcp-server.md:284 both reference codemod ID sandbox-agent-false-removal (described as "Removes sandbox.agent: false — firewall now mandatory").
Reality: This codemod does not exist in fix_codemods.go GetAllCodemods(). The actual codemod is sandbox-false-to-agent-false (migrates top-level sandbox: false to sandbox: {agent: false}). The fake codemod has opposite semantics: the real one preserves the disabled firewall state; the documented-but-fake one would remove it.
upgrading.md:84 correctly references sandbox-false-to-agent-false.

LLM agents using the gh aw MCP server are told a non-existent codemod exists with wrong semantics.

---

High-Priority Documentation Gaps

4. `close-older-key` Field Completely Undocumented (persisting, strategy-33)

The close-older-key field for create-issue and create-discussion is fully implemented:

• Schema: main_workflow_schema.json lines ~4313 (create-issue), ~4855 (create-discussion)
• Go code: create_issue.go, create_discussion.go with yaml:"close-older-key" tags
• Runtime: close_older_issues.cjs:81, close_older_discussions.cjs:103 using gh-aw-close-key markers

Missing from all documentation: safe-outputs.md, frontmatter.md, frontmatter-full.md, safe-outputs-specification.md.

Users cannot discover this deduplication mechanism that prevents duplicate issues/discussions across workflow runs.

5. `gh-aw-workflow-call-id` Marker Behavior Undocumented (persisting, strategy-33)

When GH_AW_CALLER_WORKFLOW_ID is set (compiler injects this in workflow_call contexts only — compiler_safe_outputs_job.go:441), items receive a second marker and close-older filtering uses this marker exclusively, ignoring the standard workflow-id marker.

Items created before this feature was introduced will not be closed in workflow_call contexts. Implemented in generate_footer.cjs:122, close_older_issues.cjs:61, close_older_discussions.cjs:65. Not documented anywhere.

6. `status-comment` Schema Description is Stale (persisting, strategy-30)

Schema (main_workflow_schema.json:1568) says: "Must be explicitly set to true to enable status comments — there is no automatic bundling with ai-reaction".
Code (compiler_safe_outputs.go:192-197): automatically sets StatusComment=true when slash_command OR label_command triggers are present.
Also stale: frontmatter-full.md:706-709 has identical outdated text.
Caused by the minor-enable-reaction-status-comment-by-default changeset.

---

New Findings This Run

7. safe-outputs.actions inputs Property Undocumented (NEW — 2026-03-23)

Schema (main_workflow_schema.json): safe-outputs.actions.<name>.inputs is defined as:

"Explicit input definitions for the action, overriding the auto-fetched action.yml schema. Use this to ensure deterministic compilation without requiring network access at compile time."

Go code (safe_outputs_actions.go): parseActionsConfig() parses the inputs map and populates actionConfig.Inputs, which is used downstream for tool generation.

Documentation (custom-safe-outputs.md Action Reference table): Only shows uses, description, and env. The inputs override field is completely absent.

This is a genuinely useful escape-hatch for CI environments without network access at compile time — users compiling gh aw compile in air-gapped or restricted environments can pre-specify action inputs to skip the action.yml fetch. Without docs, this feature is undiscoverable.

# Undocumented usage — works but not in docs:
safe-outputs:
  actions:
    deploy-prod:
      uses: my-org/deploy-action@v2
      inputs:
        environment:
          description: "Target environment"
          required: true
        version:
          description: "Version to deploy"

8. safe-outputs.scripts name Field Has No Effect (NEW — 2026-03-23)

Schema: safe-outputs.scripts.<name>.name exists as a valid property (mirroring safe-outputs.jobs.<name>.name).
Go code: parseSafeScriptsConfig() in safe_scripts.go:43-45 parses name into SafeScriptConfig.Name.
Problem: generateCustomScriptToolDefinition() adapts the script to a SafeJobConfig passing only Description and Inputs — Name is never applied.

Compare with safe-outputs.jobs.<name>.name: that field maps to job.DisplayName (used as the GitHub Actions step display name). For scripts, the analogous field does nothing.

Impact: Low — no user-visible functionality is broken. But the schema implies name does something (e.g., display name in logs), misleading users who set it expecting behavior similar to jobs.

---

Existing Schema Issues (Confirmed Still Unresolved)

Issue	Severity	First Found	Status
assign-to-user/unassign-from-user blocked field not in docs examples	MEDIUM	strategy-20	Persisting
reaction: eyes default description misleads non-slash_command triggers	MEDIUM	strategy-30	Persisting
state-reason in Go code and actions/setup/js but missing from pkg/workflow/js close_issue tool	HIGH	strategy-23	Persisting
on: string description omits <entity> labeled <label> shorthand format	MEDIUM	strategy-29	Persisting

---

Recommendations

1. Document safe-outputs.actions inputs override — Add a row to the Action Reference table in custom-safe-outputs.md and add a tip/note explaining its offline-compilation use case.

2. Fix safe-outputs.scripts name field — Either (a) implement it as a display label used in log output (consistent with jobs), or (b) remove it from the schema with a comment explaining why scripts don't use display names.

3. Add proxy-args to MCP server schema — Add proxy-args to $defs/stdio_mcp_tool.properties in main_workflow_schema.json (and top-level in mcp_config_schema.json).

4. Fix codemod ID mismatch — Change sandbox-agent-false-removal to sandbox-false-to-agent-false in mcp_tools_management.go and gh-aw-as-mcp-server.md.

5. Document close-older-key — Add a section in safe-outputs.md under create-issue and create-discussion explaining the deduplication key feature.

6. Fix update-discussion labels — Either implement label-handling in update_discussion.cjs + add LLM tool parameters, or remove labels/allowed-labels from the schema and docs.

---

Strategy Performance

• Strategy Used: New Changeset Features Audit + safe-outputs.actions/scripts Schema Completeness Check
• Findings: 2 new + 6 persisting
• Effectiveness: MEDIUM (new code features have good schema/docs coverage; main gaps are in detail-level properties)
• Should Reuse: YES — changeset archaeology continues to surface edge cases in newly added features

References:

• §23431625170

AI generated by Schema Consistency Checker · history

• expires on Mar 24, 2026, 10:13 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Schema Consistency Checker.

A newer discussion is available at Discussion #22595.