Skip to content

Report: longer content — architecture summary + findings-by-priority + full minor fix blocks #29

Description

@serenakeyitan

Make the report longer so users have more to fix, without inventing findings or breaking determinism. All new content lives OUTSIDE the share card.

  • What Even Is This — a savage-but-TRUE architecture summary (stack/shape/wiring), every claim tied to a real file (package.json, dirs, config), rendered with code chips. Roast is the voice; facts are load-bearing. Followed by a one-line transition into the professional fix zone.
  • Findings by Priority — every emitted finding as one overview row (derived from dimensions[].findings[]; no new required field).
  • Minor tier as full fix blocks — Medium/Low get the same Evidence / Root cause / The fix / Verify treatment as blockers (markdown was a one-liner list before; HTML already did this).
  • Contract synced across skill (SKILL.md schema, render-report.mjs, report-template.html) and website (scanSample.ts, api/reports validateReport, ScanReport.astro).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions