Implement baseline benchmarks for Task T001 (Phase 3.1)

[Copilot]

This PR implements Task T001 from specs/001-baseline-specification-for/tasks.md to establish baseline performance metrics for the modular framework prior to dynamic reload and health aggregator changes.

Implementation

Creates internal/benchmark/benchmark_baseline_test.go with three core benchmarks:

BenchmarkApplicationBootstrap

Measures application lifecycle performance including module registration, initialization, startup, and shutdown. Uses minimal mock modules to focus on framework overhead:

• Performance: ~11-12μs per operation, 100 allocations
• Coverage: Full application lifecycle with proper cleanup

BenchmarkServiceLookup

Tests service registry performance with realistic workloads:

• Registers 50 dummy services as specified
• Sub-benchmarks for named lookup (~640ns) vs enhanced registry lookup (~680ns)
• Exercises both simple and interface-based service resolution

BenchmarkConfigLoad

Measures configuration provider creation and validation:

• Performance: ~5-6ns per operation, 0 allocations
• Uses synthetic configuration with realistic nested structures
• Tests common patterns (database, server, feature flags)

Key Features

• Build Constraints: Uses //go:build planned tag to exclude benchmarks from normal builds
• Deterministic: No external dependencies, network calls, or long sleeps
• Framework Compliant: Follows existing benchmark patterns and uses correct APIs
• Documentation: Proper header referencing specification path and purpose

Verification

# Run benchmarks with planned tag
go test -tags=planned -run=^$ -bench=. ./internal/benchmark/

# Verify build constraints (should exclude files)
go test -run=^$ -bench=. ./internal/benchmark/

The benchmarks provide a performance baseline for tracking regressions during upcoming feature development phases (T031+ dynamic reload and health aggregation implementations).

No production code changes - only adds benchmark infrastructure as specified.

Created from VS Code via the GitHub Pull Request extension.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR implements baseline performance benchmarks for the modular framework to establish performance metrics before upcoming dynamic reload and health aggregator features. The implementation provides three key benchmarks measuring application lifecycle, service lookup, and configuration loading performance.

• Adds comprehensive benchmarks for application bootstrap (~11-12μs), service registry lookup (~640-680ns), and config loading (~5-6ns)
• Creates infrastructure with build constraints to exclude benchmarks from normal builds
• Establishes performance baseline for tracking regressions during future development phases

[Copilot]

The service name generation logic is unnecessarily complex and hard to understand. Consider using fmt.Sprintf(\"service-%02d\", i) for clearer intent and better readability.

[Copilot]

This duplicates the complex service name generation logic from line 136. Extract this into a helper function like generateServiceName(i int) string to eliminate code duplication and improve maintainability.