Make HTML reports purpose-fit and add prose pruning - #26
Merged
Conversation
added 2 commits
August 24, 2026 00:46
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
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
html-artifactchoose one report information architecture and visual direction from the readerPurpose, report family, use case, scenario, entry resource, and available context.prunepass toyo-slopfor reducing prose and agent-instruction load without weakening the owning artifact's contract.Why
HTML report output could remain generic after selecting a format and density because the skill did not require a scenario-specific composition decision. The revised contract separates reader purpose from report family and makes the supplied evidence shape determine the report direction.
The same work exposed a reusable need for behavior-preserving prose pruning.
yo-slopnow owns that explicit pass, while structural and behavioral decisions stay with the artifact's owning skill.Verification
git diff --checkpasses againstorigin/ori.node --check.Risk and review focus
This PR changes agent instructions and routing descriptions. It does not change bundled runtime behavior. No generated report or browser render was required, so the remaining risk is instruction interpretation.
Review the purpose and family precedence, the anti-generic direction checks, and the boundary that lets
yo-slopcompress settled prose without taking ownership of structure or agent behavior.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.