Bug: inaccurate 'POST-based triggers' comment in CodebaseAnalytics.vue (#2258)

[mrveiss]

Problem

In PR #2264, a bridging comment was added at line ~716 of CodebaseAnalytics.vue:

// #2258: Bridge code-intel scans into the data-fetcher scan orchestrator.
// loadCachedAnalyticsData uses lighter cached loaders; runAllAnalysisScans
// uses full POST-based triggers after indexing completes.

The claim that runAllAnalysisScans uses "full POST-based triggers" is factually incorrect. Of the 9 loaders in codeIntelFullScans():

Loader	HTTP Method
loadConfigDuplicates	GET (useAnalyticsFetch default)
loadApiEndpointAnalysis	GET (useAnalyticsFetch default)
loadBugPrediction	POST (useBackgroundTask)
loadSecurityScore	GET (useAnalyticsFetch default)
loadPerformanceScore	GET (useAnalyticsFetch default)
loadRedisHealth	GET (explicit)
loadEnvironmentAnalysis	GET (explicit)
loadOwnershipAnalysis	GET (useAnalyticsFetch default)
getCrossLanguageAnalysis	GET

Only 1 of 9 uses POST. The meaningful distinction is cached vs fresh re-fetch, not GET vs POST.

Fix

Change "full POST-based triggers" to "full re-fetch triggers" or "fresh analysis triggers".

Discovered During

Code review of PR #2264

Impact

Low — misleading comment only, no functional impact.

[mrveiss]

Fixed in PR #2276 — changed 'POST-based triggers' to 're-fetch triggers' in bridging comment.