docs(user/apps/coding-agents): cover indirectly generated prose in hard-wrap rule#88
Merged
Merged
Conversation
…rd-wrap rule Closes #85
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #85. The hard-wrap rule in AGENTS.md already split prose from structural line breaks (#83), but it only listed prose typed directly (commit bodies, PR/issue descriptions, doc paragraphs, comments, chat responses). It didn't say whether the rule covers prose assembled indirectly by generated code — e.g. a heredoc inside a CI workflow that writes a PR body at runtime — and in practice that gap led to hard-wrapped prose shipping in a real nixpkgs PR.
Changes
Added a clause stating the rule applies even when prose is generated indirectly (script, heredoc, template, CI workflow), and that it should be judged by the rendered artifact, not by how the generating source looks in an editor.
Per the issue's note, not reviving the
check-hardwrap.shdemonstration checker dropped in 764f0a9 — this is a documentation-only fix.Test plan