docs: clarify re-grant page-view suppression and event race tradeoff

- appinsights-manager.js: add comment explaining no trackPageView() on
  consent re-grant within the same page lifetime (initial page view was
  already recorded; re-tracking would duplicate the same URL visit)
- trydotnet-module.js: add comment acknowledging the SDK-loading race
  window where TryCodeRunner events may be dropped/unpaired (accepted
  v1 tradeoff for a low-frequency edge case)

Author: BenjaminMichaelis

EssentialCSharp.Web/wwwroot/js/appinsights-manager.js

@@ -152,6 +152,10 @@
                 } else {
                     appInsights.config.disableTelemetry = false;
                     setAuthenticatedContext();
+                    // Intentionally no trackPageView() here: the instance was created (and the
+                    // initial page view recorded) during a previous consent-granted cycle in this
+                    // same page lifetime.  Re-tracking would produce a duplicate page view for
+                    // the same URL visit.
                 }
             })
             .catch((error) => {

EssentialCSharp.Web/wwwroot/js/trydotnet-module.js

@@ -34,6 +34,11 @@ function getCorrelationContext() {
 function trackTryEvent(name, properties = {}, measurements = {}) {
     const appInsights = getAppInsights();
     if (!appInsights || typeof appInsights.trackEvent !== 'function') {
+        // No-op when the SDK is unavailable (consent denied, or SDK still loading).
+        // Known limitation: if consent is granted but the CDN script hasn't finished
+        // downloading yet, TryCodeRunnerRequested/TryCodeRunnerCompleted for a run
+        // started during that window may be dropped or mismatched.  This is accepted
+        // as a low-frequency edge case for v1.
         return;
     }