[Schema Consistency] Schema Consistency Check — 2026-03-04

[github-actions[bot]]

This repository (norrietaylor/tt2) is a Unity game project — none of the expected Go schema/parser/documentation targets (pkg/parser/schemas/, pkg/workflow/*.go, docs/src/content/docs/) exist. Analysis pivoted to internal consistency of .github/workflows/*.md frontmatter, which contains the de-facto YAML schema for the workflow automation system.

113 workflow files parsed (105 successfully). 22 distinct inconsistency categories found across field types, polymorphic shapes, and semantic contradictions.

Strategy used: Workflow Frontmatter Internal Consistency (proven, run #5) — Day-of-year 063 % 10 = 3 → proven strategy selected.

---

Summary

Category	Count
Type mismatches (same field, different YAML types)	14
Semantic inconsistencies (feature flags vs permissions)	1
Polymorphic field shapes (valid but undocumented variance)	5
Single-file anomalies (likely typos/bugs)	5
Total inconsistency categories	22

---

Critical Issues

These are likely bugs (wrong type used, will cause parse errors or silent failures):

🔴 safe-outputs.create-discussion.expires — bool instead of string

File: agent-persona-explorer.md

safe-outputs:
  create-discussion:
    expires: false   # ← bool, should be a duration string like "30d"

35 other files use strings ("90d", "30d", etc.). The boolean false is almost certainly a mistake and may disable expiry silently or cause a type error.

🔴 safe-outputs.create-issue.expires — integer instead of string

File: daily-architecture-diagram.md

safe-outputs:
  create-issue:
    expires: 7   # ← integer, should be "7d" or similar string

23 other files use strings. The integer 7 likely represents 7 days but may parse incorrectly.

🔴 on.slash_command — string instead of object

File: pr-nitpick-reviewer.md

on:
  slash_command: 'nit'   # ← string, all other files use a dict

5 other files use a dict shape. A bare string here likely causes the trigger to be misconfigured.

🔴 features.dangerous-permissions-write — feature enabled but only read permissions granted

Files: daily-issues-report.md, daily-observability-report.md, daily-performance-summary.md, org-health-report.md

All 4 files declare features.dangerous-permissions-write: true but grant only read permissions on all scopes:

features:
  dangerous-permissions-write: true   # ← declares write intent
permissions:
  contents: read
  issues: read
  pull-requests: read
  discussions: read

Either the feature flag is vestigial/incorrect, or the permissions block is missing the required write grants.

---

Type Mismatches

View all type-mismatch inconsistencies (14 fields)

Field	Types observed	File counts	Likely correct type
safe-outputs.create-discussion.expires	str / bool	35 / 1	str
safe-outputs.create-issue.expires	str / int	23 / 1	str
safe-outputs.create-issue.assignees	list / str	1 / 2	list
safe-outputs.create-pull-request.reviewers	list / str	6 / 2	list
on.slash_command	dict / str	5 / 1	dict
engine	str / dict	70 / 7	both (polymorphic)
network	dict / str	42 / 3	both (polymorphic)
permissions	dict / str	84 / 1	both (polymorphic)
tools.bash	list / bool	53 / 9	both (polymorphic)
tools.cache-memory	bool/dict/list/null	27/9/2/1	both (polymorphic)
tools.repo-memory	dict/list/bool	15/1/1	both (polymorphic)
tools.repo-memory.file-glob	list / str	11 / 3	list
tools.serena	list / dict	3 / 2	both (polymorphic)
on.schedule	str / list	35 / 28	both (polymorphic)

Single-file anomalies (likely typos):

• safe-outputs.create-issue.assignees: 'copilot' (string, 2 files) — should be ['copilot']
• safe-outputs.create-pull-request.reviewers: 'copilot' (string, 2 files: github-mcp-tools-report.md, technical-doc-writer.md) — should be ['copilot']
• safe-outputs.create-pull-request.reviewers: [] (empty list, 1 file: weekly-safe-outputs-spec-review.md) — no effect, may be intentional

---

Polymorphic Field Shapes

These fields legitimately accept multiple shapes but lack a documented schema:

View polymorphic field details

engine — string vs object

# String form (70 files):
engine: copilot

# Object form (7 files):
engine:
  id: copilot
  model: gpt-5.1-codex-mini   # only 1 file: ci-doctor.md
  agent: technical-doc-writer  # only 2 files
  max-continuations: 2         # only 1 file: smoke-copilot.md

The engine.model, engine.agent, and engine.max-continuations sub-keys appear in only 1–2 files each — these may be experimental/undocumented features.

tools.serena — list vs object

# List form (3 files):
tools:
  serena: ['go']

# Object form (2 files):
tools:
  serena:
    languages:
      go: {}

The list form is a shorthand that may not be formally specified.

tools.cache-memory — 4 distinct shapes

tools:
  cache-memory: true              # bool (27 files) — enable with defaults
  cache-memory:                   # dict (9 files)
    allowed-extensions: [...]
  cache-memory:                   # list (2 files)
    - id: repo-audits
      key: repo-audits-$\{\{ github.workflow }}
  cache-memory: ~                 # null (1 file) — explicit disable

sandbox — 2 distinct shapes

sandbox:
  agent: awf      # 8 files — agent sandbox type

sandbox:
  mcp:            # 2 files — MCP container sandbox
    container: ghcr.io/github/gh-aw-mcpg

tools.github — dict keys vary

The tools.github dict accepts 5 distinct sub-keys with variable co-occurrence:

• toolsets (list) — 56 files
• lockdown (bool) — 10 files
• mode (str: 'local' | 'remote') — 5 files
• read-only (bool) — 2 files
• github-token (str) — 1 file only (code-scanning-fixer.md) — possibly undocumented

---

Unique/Rare Top-Level Fields

View rare or single-file top-level fields

Field	Files	Notes
disable-model-invocation	1	Undocumented; purpose unclear
rate-limit	1	Undocumented; possible rate limiting config
mcp-servers	3	MCP server configuration
runtimes	3	Multiple runtime configuration
safe-inputs	3	Input validation
cache	2	Cache configuration (not tools.cache-memory)
concurrency	1	GitHub Actions concurrency group
runs-on	1	Explicit runner selection
if	2	Conditional execution
tracker-id	31	Issue/work tracking reference

---

Recommendations

1. Fix agent-persona-explorer.md — change expires: false to expires: "never" or remove the field if expiry should be disabled.
2. Fix daily-architecture-diagram.md — change expires: 7 to expires: "7d" to match string convention.
3. Fix pr-nitpick-reviewer.md — on.slash_command: 'nit' should be a dict object (e.g., {command: nit}).
4. Audit 4 dangerous-permissions-write files — either add write permissions or remove the feature flag from daily-issues-report.md, daily-observability-report.md, daily-performance-summary.md, org-health-report.md.
5. Standardize list-vs-string fields — assignees and reviewers in safe-outputs should consistently use lists. Fix breaking-change-checker.md, duplicate-code-detector.md, github-mcp-tools-report.md, technical-doc-writer.md.
6. Document polymorphic fields — engine, tools.bash, tools.cache-memory, tools.serena, sandbox all accept multiple shapes. A schema or README documenting accepted forms would prevent future inconsistencies.
7. Investigate tools.github.github-token in code-scanning-fixer.md — this sub-key appears in only 1 file and may be an undocumented/experimental feature.

---

References: §22687766100

AI generated by Schema Consistency Checker

• expires on Mar 5, 2026, 8:31 PM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-03-05T20:31:12.832Z.

Closed by Workflow