Description
Two related gaps found by the Schema Consistency Check (#52243):
- Stale inspection target:
pkg/parser/frontmatter.go now only contains a logger declaration — actual frontmatter field extraction/parsing lives under pkg/workflow/ (frontmatter_extraction_yaml.go, frontmatter_types.go, trigger_parser.go). Automated field-diff/schema-consistency tooling that only inspects pkg/parser/*.go produces false negatives (e.g. parser_yaml_fields comes back empty, which reads as "nothing to check" rather than "wrong file").
- Incomplete generated reference:
docs/src/content/docs/reference/frontmatter-full.md is missing runtimes.<runtime>.run-install-scripts (implemented in pkg/workflow/frontmatter_types.go as RunInstallScripts *bool) and safe-outputs.report-failed-jobs (parsed in pkg/workflow/safe_outputs_config_global.go) as searchable field names, even though both are schema-defined and documented in frontmatter.md itself.
Expected Impact
Field-diff/schema-consistency checks stop silently missing the real implementation surface, and the "complete" generated frontmatter reference actually contains every schema field a user might search for.
Suggested Agent
General docs/tooling agent — (a) update schema-consistency tooling to point at pkg/workflow/frontmatter_types.go instead of pkg/parser/frontmatter.go; (b) fix frontmatter-full.md generation to emit run-install-scripts and report-failed-jobs; (c) optionally add a regression check asserting every schema property is searchable in frontmatter-full.md or intentionally excluded.
Estimated Effort
Medium (1-4 hours)
Data Source
DeepReport Intelligence Briefing 2026-08-12, mined from Schema Consistency Check #52243.
Generated by 🔬 Deep Report · agent · 198.4 AIC · ⌖ 54.5 AIC · ⊞ 11.4K · ◷
Description
Two related gaps found by the Schema Consistency Check (#52243):
pkg/parser/frontmatter.gonow only contains a logger declaration — actual frontmatter field extraction/parsing lives underpkg/workflow/(frontmatter_extraction_yaml.go,frontmatter_types.go,trigger_parser.go). Automated field-diff/schema-consistency tooling that only inspectspkg/parser/*.goproduces false negatives (e.g.parser_yaml_fieldscomes back empty, which reads as "nothing to check" rather than "wrong file").docs/src/content/docs/reference/frontmatter-full.mdis missingruntimes.<runtime>.run-install-scripts(implemented inpkg/workflow/frontmatter_types.goasRunInstallScripts *bool) andsafe-outputs.report-failed-jobs(parsed inpkg/workflow/safe_outputs_config_global.go) as searchable field names, even though both are schema-defined and documented infrontmatter.mditself.Expected Impact
Field-diff/schema-consistency checks stop silently missing the real implementation surface, and the "complete" generated frontmatter reference actually contains every schema field a user might search for.
Suggested Agent
General docs/tooling agent — (a) update schema-consistency tooling to point at
pkg/workflow/frontmatter_types.goinstead ofpkg/parser/frontmatter.go; (b) fixfrontmatter-full.mdgeneration to emitrun-install-scriptsandreport-failed-jobs; (c) optionally add a regression check asserting every schema property is searchable infrontmatter-full.mdor intentionally excluded.Estimated Effort
Medium (1-4 hours)
Data Source
DeepReport Intelligence Briefing 2026-08-12, mined from Schema Consistency Check #52243.