docs: remove stale triage CSV worksheet references#597
Merged
Conversation
The scan no longer emits a separate triage CSV worksheet (it produces the HTML report and the raw JSON data file); the report contains read-only triage guidance, not a fillable worksheet. Update the triage workflow to ask reviewers to justify findings against the HTML report directly, and fix the comparison doc. Follow-up (needs a JS rebuild, out of scope here): the in-report guidance asset cloudsplaining/output/src/assets/2-triage-guidance.md carries the same stale CSV worksheet wording. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kmcquade
added a commit
that referenced
this pull request
Jun 14, 2026
…sh demo report) (#598) * Remove stale triage CSV worksheet references from the in-report guidance The HTML report's Triaging guidance still told users to attach and fill out a "Triage CSV worksheet" that the scan no longer generates. Update the in-report guidance asset (2-triage-guidance.md) to ask reviewers to justify findings against the HTML report directly, and rebuild the committed Vue bundle so the generated report reflects it. Rebuilt with `npm run build` (not `just build-js`) to avoid regenerating example IAM fixtures; diff is limited to the asset and the dist bundle, no fixture drift. Mirrors the docs-site fix in #597. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Refresh the example report to embed the corrected triage guidance Re-render index.html from the existing committed fixture and the rebuilt Vue bundle so the demo report no longer shows the stale "Triage CSV worksheet" wording. Used generate_example_report.py (not generate-report) to avoid regenerating fixtures: compare-reports confirms 0 findings added/removed, and example-iam-data.json / sampleData.js are untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Removes stale references to the triage CSV worksheet from the docs. The
scancommand no longer emits a separate CSV worksheet — it produces the single-file HTML report and the raw JSON data file (verified against a real scan). The HTML report contains read-only triage guidance, not a fillable worksheet.docs/report/triage.md: "three files" → "two files"; the triage workflow now asks reviewers to justify findings against the HTML report directly instead of filling out a CSV worksheet.docs/appendices/comparison-to-other-tools.md: "(as shown in the Triage CSV worksheet)" → "(as shown in the triage guidance)".Context
Follows the docs modernization in #595 (which removed "triage worksheet" wording from the README/overview). This finishes that cleanup for the dedicated triage page.
Known follow-up (out of scope — needs a JS rebuild)
The in-report guidance source,
cloudsplaining/output/src/assets/2-triage-guidance.md, carries the same stale CSV-worksheet wording, so the rendered HTML report still tells users to "fill out the Triage CSV worksheet." Fixing that means editing the asset and rebuilding the committed Vue bundle (just build-js), which is a larger, non-docs change — worth its own PR.🤖 Generated with Claude Code