chore(ci): regenerate the branding-drift baseline after #6786

[JSONbored]

Summary

• fix(mcp): rename enrichment-analyzers resource URI to loopover:// #6786 (enrichment-analyzers URI rename) merged after chore(ci): add a drift guardrail against new gittensory branding #6788's (branding-drift guardrail) baseline was generated, so main's own branding-drift:check has been red since both landed — exactly the "decreased" scenario the check is designed to catch, working as intended.
• Regenerated via npm run branding-drift:update. Diff is minimal: loopover-mcp.js 5→3, routes.ts 3→2, enrichment-analyzers-taxonomy.ts 1→0 (removed entirely, now clean).

Scope

• Narrow, single-purpose change (generated artifact only)
• No secrets/private terms touched
• No changelog edit

Validation

• npm run branding-drift:check — passes against the regenerated baseline

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.63%. Comparing base (a4dcb48) to head (e275417).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6791      +/-   ##
==========================================
+ Coverage   87.51%   93.63%   +6.12%     
==========================================
  Files         683      683              
  Lines       68148    68148              
  Branches    18703    18703              
==========================================
+ Hits        59641    63812    +4171     
+ Misses       6845     3350    -3495     
+ Partials     1662      986     -676     

Flag	Coverage Δ
shard-1	43.63% <ø> (?)
shard-2	36.73% <ø> (ø)
shard-3	32.75% <ø> (ø)
shard-4	34.21% <ø> (ø)
shard-5	31.56% <ø> (ø)
shard-6	45.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 114 files with indirect coverage changes