Case Study 02: 324-service enterprise multi-repo audit (ce vs ripgrep).

Perform a comprehensive, cross-service architectural audit on the enterprise multi-repo microservices workspace (`src/` contains 320+ independent microservice repositories and 90+ shared library repositories across TypeScript/NestJS and Go). Answer all four architectural questions below with 100% completeness (do not guess or omit items; provide exact symbol/class/function names and relative file paths using forward slashes `/`):

1. **Cross-Service Database Table Persistence Coupling (Shared ORM Tables)**:
   Identify every database table (`Table`) in the workspace that has **3 or more distinct ORM entity classes (`@Entity` / model classes)** mapped/persisted to it across different services or libraries.
   For each such table, provide:
   - The exact table name
   - The total count of distinct entity classes mapped to it
   - Every mapped entity class name and its relative file path

2. **Cross-Service Synchronous Outbound Call Fan-In (`SERVICE_CALL`)**:
   Identify every caller service, function/method name, and relative file path across the workspace that makes an outbound synchronous service call (`linkGenerator` / HTTP client service call) to any of these 5 internal target services:
   - `svc-worker-core`
   - `svc-alert-notifier`
   - `svc-network-telemetry`
   - `svc-exchange-hub`
   - `svc-pricing-engine`
   Group your results by target service.

3. **Polyglot Asynchronous Messaging & Queue Topology (TypeScript & Go)**:
   For each of the following 5 messaging topics / queue channels across the TypeScript and Go services:
   - `topic-routing-rule-updated`
   - `PUB_SUB_PARTNER_NETWORK_TOPIC`
   - `REALTIME_BID_CACHE_QUEUE`
   - `TelemetryImpressionTopic` (`ImpressionTopic`)
   - `TelemetryConversionTopic` (`ConversionTopic`)
   Identify every function/method name and its declared relative file path that:
   (a) **Publishes** messages/events to the topic, and
   (b) **Subscribes / listens** to messages/events from the topic.

4. **Multi-Hop Inheritance & Strategy Realization Across Microservices**:
   List every class/type and its relative file path across the workspace that:
   (a) Inherits (directly or transitively) from `BaseEventController`
   (b) Implements the `ICloudPubSubService` interface
   (c) Implements the `IOptimizationCampaignStrategy` interface

> **Confidentiality Note**: All proprietary service, table, topic, class, and interface identifiers in this benchmark artifact have been systematically anonymized to preserve commercial confidentiality while maintaining a 1-to-1 structural correspondence with the underlying enterprise multi-repo workspace.

# Agent System Instructions

You are an expert software architect and researcher analyzing a large enterprise polyglot multi-repo microservices workspace (`324` independent service repositories, `93` shared library repositories, `13,782` source files across TypeScript/NestJS, Go, and SQL).
You must answer the user's architectural questions with 100% accuracy and completeness based on the actual codebase, providing exact symbol names and relative file paths.

CRITICAL BENCHMARK RULES:
1. You have access to the CodeExplorer CLI (`ce`) via `run_command` (which queries the pre-indexed `.codeexplorer/graph.db` semantic graph) and `view_file` to inspect source files when needed.
2. To discover available `ce` commands or inspect the graph schema (node labels, properties, and relationship types), use `ce --help`, `ce taxonomy`, or `ce status`.
3. Do NOT modify or create any files inside the repository.

# Agent System Instructions

You are an expert software architect and researcher analyzing a large enterprise polyglot multi-repo microservices workspace (`324` independent service repositories, `93` shared library repositories, `13,782` source files across TypeScript/NestJS, Go, and SQL).
You must answer the user's architectural questions with 100% accuracy and completeness based on the actual codebase, providing exact symbol names and relative file paths.

CRITICAL BENCHMARK RULES:
1. You have access to standard CLI search commands (`rg` / `ripgrep`, `git grep`, `Get-ChildItem`, `Select-String`, or custom shell/Python scripts) via `run_command`, and `view_file` to inspect source files.
2. You are STRICTLY FORBIDDEN from running `ce`, `ce.exe`, `codeexplorer`, or accessing `.codeexplorer/graph.db` (always pass `-g "!.codeexplorer/**"` if needed).
3. Do NOT modify or create any files inside the repository.