code-analysis

Legacy codebase analysis from a single entry point automatically discovers connected components across layers. It traverses imports, method calls, SQL, and configuration to map presentation, business logic, and data access dependencies.

Architectural drift detection in legacy code is handled by generating fingerprint.json and analysis.md artifacts. These files map cross-layer components and highlight structural inconsistencies discovered during the auto-discovery process.

Auto-discovery of SQL stored procedures and messaging components works by traversing method calls and deployment references from a designated entry point. It maps these data access and messaging layers into source-extracts.md.

Tracing code paths across presentation, business logic, and data access layers is supported by end-to-end mapping. The analysis traverses dependency injection and imports to generate a comprehensive structural inventory.

Manual configuration for dependency tracking in legacy code is unnecessary. The auto-discovery mechanism automatically traverses imports, DI, SQL, and configuration files starting from a single specified entry point path.

Cross-entry-point governance for shared resources works by appending discovered components to contracts.json. This supports tracking and reuse across multiple entry-point analyses within the same legacy codebase.