@W-22210602 cip analytics VS extension

[charithaT07]

Summary

Polishes the CIP Analytics surface in the VS Code extension:

• Curated Reports tree (src/cip-analytics/types.ts) —
  replaced the generic folder icon with a distinct codicon per
  category (graph-line, package, account, search, tag,
  credit-card, globe, gear), humanized report slugs
  (customer-registration-trends → Customer Registration Trends), and moved the SDK report description into the
  right-hand description slot in place of the trailing emoji.
• Description color (.vscode/settings.json) — lightened
  workspace list.descriptionForeground /
  list.deemphasizedForeground to #9a9a9a so report subtext
  recedes from the title.
• Hero eyebrow accent (src/cip-analytics/cip-styles.css) —
  switched the B2C-DX ANALYTICS eyebrow on Query Builder and
  Entity Browser from --vscode-descriptionForeground to
  --cip-accent, picking up the theme's link/blue token.

Testing

• tsc --noEmit passes for packages/b2c-vs-extension.
• Reloaded the Extension Development Host and verified:
  • Curated Reports categories render with their new icons;
    report rows show humanized titles + descriptions.
  • Description text in the tree reads in the lighter grey.
  • Query Builder and Entity Browser headers show the eyebrow in
    the theme accent (verified in light + dark themes).

Dependencies

• No net-new third-party dependencies were added
• If net-new third-party dependencies were added,
  rationale/discussion is included and 3pl-approved is set by a
  maintainer

---

• Tests pass (pnpm test)
• Code is formatted (pnpm run format)

[clavery]

Looks good so far. Few initial notes:

This item I added recently to support our safety mode and analytics. Should be a simple mechanical fix.

1. Doesn't use registerSafeCommand (safety.ts) — none of the 11 commands are gated.
   api-browser/index.ts, sandbox-tree/, webdav-tree/, code-sync/ all route through registerSafeCommand. CIP uses vscode.commands.registerCommand directly (src/cip-analytics/index.ts:74-183). Most CIP commands are read-only so safety policy probably wouldn't block them, but bypassing the wrapper also means no
   markFeatureUsed() telemetry fires for any CIP command. That's the bigger miss — the analytics feature itself is invisible to your usage analytics.

This item is a build consistency issue:

Styles shipped as 3,495-line raw CSS in src/cip-analytics/cip-styles.css with a special-case .vscodeignore exception (!src/cip-analytics/*.css).
The webview JS goes through esbuild → dist/webview-ui/, but the stylesheet is loaded straight from src/. That's an inconsistency — you reach back into src/ from a packaged extension. Nothing is broken (the .vscodeignore exception keeps it shipped), but it would be cleaner to either:

• Have esbuild copy/bundle it into dist/webview-ui/cip-styles.css (matches the JS), or
• Use the loader: {'.css': 'text'} rule already in webviewBuildOptions and import './cip-styles.css' from each entry — the rule is even configured already, but no one imports the CSS file. Right now it's dead-config.

Documentation — README/CHANGELOG entry, plus a new "VS Code IDE Integration" section in the existing analytics-reports-cip-ccac.md guide.

I'll have some UX/UI notes later