🎨 [FFL-2857] drop comments that restate the code

Remove field docs that repeated their own names or the enclosing interface
doc, and replace the opaque RFC 7009 aside on tryRevokeGrant with a plain
explanation plus a link on revokeAndClearTokens.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: kellyw1806

developer-extension/src/panel/components/tabs/flagsTab/flagCatalogList.tsx

@@ -132,7 +132,6 @@ function FlagRow({
       py="sm"
       style={{
         borderBottom: '1px solid var(--mantine-color-default-border)',
-        // Mantine's scheme-aware subtle tint (the one variant="light" uses), not a saturated fill.
         backgroundColor: overridden ? 'var(--mantine-color-violet-light)' : undefined,
       }}
     >
@@ -209,7 +208,6 @@ function FlagDescription({ description }: { description: string }) {
   }, [description, expanded])
 
   return (
-    // Slightly more separation than the name↔key gap, so the row reads as "title/key" then "description".
     <Box mt={4}>
       <Text ref={textRef} size="xs" lineClamp={expanded ? undefined : 1}>
         {description}

developer-extension/src/panel/components/tabs/flagsTab/flagIdentity.ts

@@ -10,13 +10,9 @@ import { fetchFfeJson, ForbiddenError } from './ffeApi'
 import { getFlagsApiHost } from './oauth'
 
 export interface FlagIdentity {
-  /** UUID of the signed-in user, or null when it couldn't be resolved. */
   userId: string | null
-  /** Handles of the teams the signed-in user belongs to, sorted for stable display. */
   teamHandles: string[]
-  /** True when the team lookup was refused because the user lacks permission to read teams. */
   teamsForbidden: boolean
-  /** True when the team lookup failed for another reason (network/server), distinct from an empty membership. */
   teamsUnavailable: boolean
 }
 

developer-extension/src/panel/components/tabs/flagsTab/flagsRequests.ts

@@ -5,16 +5,12 @@ import { getFlagsApiHost } from './oauth'
 export interface CatalogFlag {
   key: string
   name: string
-  /** Free-text description authored in the Datadog UI. Empty when the flag has none. */
   description: string
   type: FlagType
   /** Parsed value of each variant (any JSON value); see parseVariantValue. */
   variants: Array<{ name: string; value: unknown }>
   tags: string[]
-  /**
-   * UUID of the user who created the flag. Undefined for flags created by a service account or
-   * integration. Compared against the signed-in user's UUID for the "My feature flags" filter.
-   */
+  /** Undefined for flags created by a service account or integration, which carry no user UUID. */
   createdBy?: string
 }
 
@@ -33,9 +29,7 @@ export interface FlagCatalogRequest {
   search: string
   typeFilter: string[]
   tagFilter: string[]
-  /** Team handles for the "My teams" filter, sent as `tags=team:<handle>`. */
   teamFilter: string[]
-  /** The signed-in user's UUID when "My feature flags" is on, else null. Sent as `created_by`. */
   createdBy: string | null
 }
 

developer-extension/src/panel/components/tabs/flagsTab/oauth.ts

@@ -228,9 +228,9 @@ export async function clearStoredTokens(): Promise<void> {
 }
 
 /**
- * Ends the connection: revokes the grant at Datadog (RFC 7009), then drops the local tokens.
- * Clearing locally alone would only make this extension forget them — the grant would stay live and
- * any copy of the refresh token would keep working.
+ * Ends the connection: revokes the grant at Datadog, then drops the local tokens. Clearing locally
+ * alone would only make this extension forget them — the grant would stay live and any copy of the
+ * refresh token would keep working. Revocation follows https://datatracker.ietf.org/doc/html/rfc7009.
  *
  * Returns whether the revocation succeeded. Local tokens are cleared either way, so a user who asked
  * to disconnect ends up disconnected even if Datadog is unreachable; the caller reports a failure as
@@ -244,9 +244,11 @@ export async function revokeAndClearTokens(site: string): Promise<{ revoked: boo
 }
 
 /**
- * Revokes the refresh token — the renewable part of the grant. The access token is left to expire
- * (RFC 7009 only *recommends* cascading revocation, so we don't rely on it) and is dropped locally
- * by the caller. Refreshes first because the revoke endpoint authenticates with a Bearer token.
+ * Revokes the refresh token, since that's the renewable part of the grant — revoking only the access
+ * token would leave the grant able to mint new ones. The short-lived access token is left to expire
+ * on its own, and dropped locally by the caller.
+ *
+ * Refreshes first: the revoke endpoint authenticates the caller with a Bearer token.
  */
 async function tryRevokeGrant(site: string): Promise<boolean> {
   try {

developer-extension/src/panel/components/tabs/flagsTab/useFlagCatalogView.ts

@@ -2,7 +2,6 @@ import { useEffect, useMemo, useState } from 'react'
 import type { FlagCatalogRequest } from './flagsRequests'
 
 const CATALOG_PAGE_SIZE = 20
-// Long enough to wait out a typing burst, short enough to still feel responsive.
 const SEARCH_DEBOUNCE_MS = 400
 
 export interface FlagCatalogView {