Skip to content

docs: fix documentation drift — directory name, missing codemod, conclusion config#1255

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/fix-documentation-drift-8aabf531749e1f3f
Draft

docs: fix documentation drift — directory name, missing codemod, conclusion config#1255
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/fix-documentation-drift-8aabf531749e1f3f

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Documentation Freshness Audit

This audit found the following inconsistencies between code and documentation:

Findings

Area Issue File(s)
Architecture tree safeoutputs/ wrong — actual directory is src/safe_outputs/ AGENTS.md
Codemods list 0003_flatten_work_item_config.rs exists on disk but not in architecture tree AGENTS.md
Docs index References non-existent `conclusion:` front-matter field; config is under safe-outputs: AGENTS.md
Pipeline IR section "when `conclusion:` is configured" — no such field exists docs/cli.md

Details

1. Wrong directory name (AGENTS.md architecture tree)

The tree listed src/safeoutputs/ but the actual directory on disk is src/safe_outputs/. This would cause AI agents reading AGENTS.md to look in the wrong place when navigating the codebase.

2. Missing codemod in architecture tree (AGENTS.md)

src/compile/codemods/0003_flatten_work_item_config.rs exists and handles the migration of nested work-item: config blocks (under noop, missing-tool, missing-data) to the new flat form with title-prefix: / report-as-work-item:. It was absent from the architecture tree.

3. Misleading `conclusion:` field reference (AGENTS.md docs index)

The docs index entry for docs/conclusion.md said "`conclusion:` configuration for the always-running post-pipeline housekeeping job". There is no conclusion: key in FrontMatter — the Conclusion job is emitted automatically when safe-outputs: is non-empty, and its configuration lives entirely under safe-outputs: (as docs/conclusion.md itself states: "All configuration lives under safe-outputs: in front matter").

4. Same `conclusion:` confusion in docs/cli.md

The Pipeline IR Reference section said "plus the optional always-running Conclusion job when `conclusion:` is configured". Fixed to reference `safe-outputs:`.

Applied Fixes

  • AGENTS.md: rename safeoutputs/safe_outputs/ in the architecture tree
  • AGENTS.md: add 0003_flatten_work_item_config.rs entry to the codemods section
  • AGENTS.md: rewrite docs/conclusion.md index entry to accurately describe Conclusion job configuration
  • docs/cli.md: fix "when conclusion: is configured" → "when safe-outputs: is configured"

This pull request was created by the automated documentation freshness check.

Generated by Documentation Freshness Check · 2K AIC · ⌖ 32 AIC · ⊞ 35.8K ·

…lusion config

- Fix AGENTS.md architecture tree: rename safeoutputs/ → safe_outputs/ (actual
  directory name on disk)
- Add missing 0003_flatten_work_item_config.rs codemod entry to the AGENTS.md
  codemods section
- Fix AGENTS.md docs index: remove misleading reference to a non-existent
  `conclusion:` front-matter field; Conclusion job config lives under
  `safe-outputs:` (as docs/conclusion.md itself states)
- Fix docs/cli.md Pipeline IR Reference: replace `conclusion:` with
  `safe-outputs:` — the Conclusion job is emitted when safe-outputs are
  configured, not when a `conclusion:` key is set

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants