Description
A schema consistency audit (discussion #50792) found that docs/src/content/docs/reference/glossary.md incorrectly states that status-comment: true is configured in safe-outputs. The implementation and other docs place it under on: instead.
Suggested Changes
- Update
docs/src/content/docs/reference/glossary.md so the status-comment entry describes it as configured under on: (matching docs/src/content/docs/reference/frontmatter.md and docs/src/content/docs/reference/triggers.md)
- Verify against
pkg/workflow/trigger_parser.go, which parses status-comment from the on map, to confirm the corrected wording matches implementation
Files Affected
docs/src/content/docs/reference/glossary.md
Success Criteria
Source
Extracted from Schema Consistency Check - 2026-08-06 (discussion #50792)
Priority
Low - documentation-only fix, quick and low risk
🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · auto · 35.3 AIC · ⌖ 4.12 AIC · ⊞ 10.2K · ◷
Description
A schema consistency audit (discussion #50792) found that
docs/src/content/docs/reference/glossary.mdincorrectly states thatstatus-comment: trueis configured insafe-outputs. The implementation and other docs place it underon:instead.Suggested Changes
docs/src/content/docs/reference/glossary.mdso thestatus-commententry describes it as configured underon:(matchingdocs/src/content/docs/reference/frontmatter.mdanddocs/src/content/docs/reference/triggers.md)pkg/workflow/trigger_parser.go, which parsesstatus-commentfrom theonmap, to confirm the corrected wording matches implementationFiles Affected
docs/src/content/docs/reference/glossary.mdSuccess Criteria
status-commentcorrectly describes it as anon:fieldfrontmatter.mdandtriggers.mdSource
Extracted from Schema Consistency Check - 2026-08-06 (discussion #50792)
Priority
Low - documentation-only fix, quick and low risk