Startup config should be processed before first user prompt, not after

Problem

The startup validation sequence is inverted relative to standard software architecture. Currently:

1. System loads context
2. Claude waits for first user input
3. Only then does Claude execute startup validation (actually processing .claude/settings.json, CLAUDE.md etc content)
4. This means any statements made before step 3 contradict the environment state discovered in step 3

Expected Behavior

Standard initialization order (used by ~99.9999% of applications):

1. Load and validate configuration
2. Display configuration state info to user
3. THEN enter main loop and accept user input

This eliminates the coherence problem of making environment claims before actually validating the environment.

Impact

• Pre-initialization statements are made with incomplete knowledge
• These statements are later contradicted by actual behavior once config is processed
• Users can catch the system making false claims about its own state

This is a fundamental architectural ordering issue, not a workaround-able behavior.