chore: renovate all remaining files to current date

[beejak]

Summary

• gofmt applied to 14 Go source files that had minor formatting drift (no logic changes)
• Trailing whitespace stripped from doc/text files
• HELP.md stale platform list updated from 4 → 9 CI platforms
• Renovated comment added to all remaining old files: scripts, Dockerfile, Makefile, docker-compose.yml, scanner.yaml, .cursor/rules, .gitignore, remaining docs, web/index.html, tests/baseline data, tests/integration, ide/ files

After merge, all 121 tracked files will show July 2026 as their last-modified date on GitHub. No behaviour changes; all tests pass.

---

Generated by Claude Code

Greptile Summary

This PR is a pure housekeeping pass across 69 files: gofmt struct-field alignment applied to 14 Go source files, trailing whitespace stripped from Markdown/text files, and a // renovated: 2026-07-02 timestamp comment appended to all remaining files so GitHub shows a July 2026 last-modified date. The one meaningful content change is an expanded CI platform list in docs/HELP.md.

• Go formatting (cmd/, pkg/): All diffs are gofmt whitespace-only — struct field column-alignment and import reordering. No logic or behaviour changes.
• docs/HELP.md: CI pipeline examples updated from 4 platforms (Azure, GitHub, GitLab, Jenkins) to 9 (adds CircleCI, AWS CodeBuild, Google Cloud Build, Bitbucket Pipelines, Tekton).
• Timestamp comments: // renovated: 2026-07-02 appended to scripts, Dockerfile, Makefile, YAML configs, cursor rules, doc files, and two Go integration test files.

Confidence Score: 5/5

All changes are cosmetic — gofmt alignment, whitespace cleanup, a doc-text update, and timestamp comments. No logic paths are touched.

Every Go change is a whitespace-only gofmt pass with no reordering of logic, no altered function signatures, and no changed JSON tags or struct field names. The only content edit is the expanded CI platform list in HELP.md, which is informational. The renovated comments in Go test files are valid Go and do not affect test execution.

The two integration test files (tests/integration/scan_integration_test.go, tests/integration/scan_with_config_test.go) carry a free-floating timestamp comment that is slightly unconventional; worth a quick glance but not blocking.

Important Files Changed

Filename	Overview
tests/integration/scan_integration_test.go	Appends a bare // renovated: 2026-07-02 comment outside any function — valid Go but unconventional for a test file; no behavioural change.
tests/integration/scan_with_config_test.go	Same bare timestamp comment appended after the last function; no behavioural change.
docs/HELP.md	CI platform list expanded from 4 to 9 entries; trailing two-space hard-line-break markers stripped from several list items (visually safe in GFM).
pkg/scanner/finding.go	Pure gofmt struct-field alignment; no logic change.
pkg/report/report.go	Pure gofmt struct-field alignment across SARIF type definitions; no logic change.
cmd/server/main.go	Doc comment reformatted to Go 1.19+ example-block style (tab-indented //\t); gofmt struct alignment on sseEvent. No logic change.
cmd/baseline/main.go	Import order alphabetised and struct/literal fields column-aligned by gofmt; no logic change.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[69 files changed] --> B[Go source files x14]
    A --> C[Doc / Markdown files x15]
    A --> D[Scripts / config / misc x40]

    B --> B1[gofmt: struct field alignment only]
    B --> B2[Import order normalised]
    B --> B3[Go test files + renovated comment]

    C --> C1[HELP.md: CI platforms 4 to 9 entries]
    C --> C2[Trailing whitespace stripped]
    C --> C3[Newline at EOF added]

    D --> D1[renovated: 2026-07-02 comment appended]

    B1 --> Z[No behaviour change]
    B2 --> Z
    B3 --> Z
    C1 --> Z
    C2 --> Z
    C3 --> Z
    D1 --> Z

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[69 files changed] --> B[Go source files x14]
    A --> C[Doc / Markdown files x15]
    A --> D[Scripts / config / misc x40]

    B --> B1[gofmt: struct field alignment only]
    B --> B2[Import order normalised]
    B --> B3[Go test files + renovated comment]

    C --> C1[HELP.md: CI platforms 4 to 9 entries]
    C --> C2[Trailing whitespace stripped]
    C --> C3[Newline at EOF added]

    D --> D1[renovated: 2026-07-02 comment appended]

    B1 --> Z[No behaviour change]
    B2 --> Z
    B3 --> Z
    C1 --> Z
    C2 --> Z
    C3 --> Z
    D1 --> Z

Loading

_{Reviews (1): Last reviewed commit: "chore: renovate all remaining files to c..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Bare timestamp comment in a Go test file

The // renovated: 2026-07-02 comment sits outside any function or declaration at package scope. Tools like golangci-lint (with godot or godox linters) and some doc-comment checkers flag unexpected free-floating comments at end-of-file. If the sole intent is bumping the Git last-modified date, a blank line at EOF achieves the same effect without adding a semantically ambiguous comment. The same pattern also appears in tests/integration/scan_with_config_test.go.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!