Neutralize internal Anthropic prose in explanatory comments (#357)

This is a small prose-only follow-up that rewrites clearly internal or
explanatory Anthropic comment language to neutral wording in a handful of
high-confidence files. It avoids runtime strings, flags, command labels,
protocol identifiers, and provider-facing references.

Constraint: Keep this pass narrowly scoped to comments/documentation only
Rejected: Broader Anthropic comment sweep across functional API/protocol references | too ambiguous for a safe prose-only PR
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Leave functional Anthropic references (API behavior, SDKs, URLs, provider labels, protocol docs) for separate reviewed passes
Tested: bun run build
Tested: bun run smoke
Tested: bun run verify:privacy
Tested: bun run test:provider
Tested: bun run test:provider-recommendation
Not-tested: Full repo typecheck (upstream baseline remains noisy)

Co-authored-by: anandh8x <test@example.com>

src/utils/buildConfig.ts

@@ -1,7 +1,7 @@
 /**
  * OpenClaude build-time constants.
  *
- * These replace process.env checks that were only meaningful in Anthropic's
+ * These replace process.env checks that were only meaningful in the upstream
  * internal build. In OpenClaude all such gates are permanently disabled so
  * external users cannot activate internal code paths by setting env vars.
  */
@@ -9,7 +9,7 @@
 /**
  * Always false in OpenClaude.
  * Replaces all `process.env.USER_TYPE === 'ant'` checks so that no external
- * user can activate Anthropic-internal features (commit attribution hooks,
+ * user can activate internal-only features (commit attribution hooks,
  * system-prompt section clearing, dangerously-skip-permissions bypass, etc.)
  * by setting USER_TYPE in their shell environment.
  */