Empty Controller top page, move intro into Life Cycle

Author: claude

docs/development/controller/controller.md

@@ -2,14 +2,3 @@
 outline: [2, 4]
 ---
 # Controller
-
-abap2UI5 gives you great flexibility in how you structure apps. Most sample apps follow the pattern below. Use it as a starting point, and tweak it or build a wrapper around abap2UI5 for more specific behavior.
-
-The idea: every request enters the `main` method, and you use `CASE` to dispatch between initialization, navigation returns, and user events.
-
-The following sections walk through each phase:
-
-- [Life Cycle](/development/controller/life_cycle) — the overall dispatch pattern in `main`
-- [Init](/development/controller/init) — first-time setup and rendering the view
-- [Event](/development/controller/event) — handling user actions
-- [Navigated](/development/controller/navigated) — returning from another app

docs/development/controller/life_cycle.md

@@ -3,7 +3,9 @@ outline: [2, 4]
 ---
 # Life Cycle
 
-Every request to an abap2UI5 app enters the `main` method. The recommended pattern uses `CASE abap_true` together with `client->check_on_init`, `client->check_on_event`, and `client->check_on_navigated` to dispatch to the matching handler method.
+abap2UI5 gives you great flexibility in how you structure apps. Most sample apps follow the pattern below. Use it as a starting point, and tweak it or build a wrapper around abap2UI5 for more specific behavior.
+
+The idea: every request enters the `main` method, and you use `CASE` to dispatch between initialization, navigation returns, and user events. The recommended pattern uses `CASE abap_true` together with `client->check_on_init`, `client->check_on_event`, and `client->check_on_navigated` to dispatch to the matching handler method.
 
 ```abap
 CLASS z2ui5_cl_demo_app_001 DEFINITION PUBLIC.