Skip to content

Make HTML reports purpose-fit and add prose pruning - #26

Merged
mosobande merged 2 commits into
orifrom
feature/html-artifact-report-direction
Aug 23, 2026
Merged

Make HTML reports purpose-fit and add prose pruning#26
mosobande merged 2 commits into
orifrom
feature/html-artifact-report-direction

Conversation

@mosobande

@mosobande mosobande commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Make html-artifact choose one report information architecture and visual direction from the reader Purpose, report family, use case, scenario, entry resource, and available context.
  • Preserve governed formats, evidence coverage, and content authority while rejecting interchangeable dashboards, card grids, design options, and prototype behavior.
  • Add an explicit prune pass to yo-slop for reducing prose and agent-instruction load without weakening the owning artifact's contract.
  • Reduce the active HTML report instruction path from 4,072 to 3,467 words. This path is the root skill plus the report reference loaded for report requests.

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-slop now owns that explicit pass, while structural and behavioral decisions stay with the artifact's owning skill.

Verification

  • git diff --check passes against origin/ori.
  • Skill frontmatter, Changesets metadata, OpenAI metadata YAML, and the plugin manifest parse successfully.
  • All local Markdown links in the changed skill packages resolve.
  • Every bundled HTML control script passes node --check.
  • Independent static behavior reviews passed six report-direction scenarios and seven prose-pruning boundary scenarios.

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-slop compress settled prose without taking ownership of structure or agent behavior.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@mosobande mosobande added the enhancement New feature or request label Aug 23, 2026
@mosobande
mosobande merged commit 360df65 into ori Aug 23, 2026
4 checks passed
@github-actions github-actions Bot mentioned this pull request Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant