Web: MiniWebApp routing pattern (front controller + path dispatch)

[PurHur]

Problem

#67 defines the reference app. This issue specifies the routing architecture so implementers know the target before writing 003-MiniWebApp.

Goal

Document and implement a minimal front-controller pattern:

public/index.php  → router → handlers/
templates/*.php   → include with extract()

Routes (minimum)

Method	Path	Behavior
GET	/	Home template
GET	/hello?name=	Greet (#1 parity)
POST	/contact	Form validate + thank-you
GET	/api/status	JSON (#61)

Tasks

• Create examples/003-MiniWebApp/ skeleton (blocked on Reference app: examples/003-MiniWebApp (router, templates, forms) #67)
• Use PATH_INFO (Web: PATH_INFO and front-controller routing ($_SERVER) #121 ✅) or query ?route=
• Shared layout template (include Language: include/require in JIT and AOT (multi-file applications) #54)
• CSRF token optional (Stdlib: random_bytes and bin2hex for CSRF/session tokens #123)
• README with curl recipes
• Run matrix: VM serve, JIT serve (Web: JIT/AOT mode for bin/serve.php (compile per script on first request) #207), AOT CGI (Web: CGI/1.1 request driver (stdin/stdout, env, Status line) #50)

Acceptance criteria

All routes pass PHPT/web tests in #68.

Dependencies

• Reference app: examples/003-MiniWebApp (router, templates, forms) #67, Language: Implement foreach (CFG → VM → JIT) #53, Language: include/require in JIT and AOT (multi-file applications) #54, Stdlib: json_encode and json_decode for API endpoints #61, JIT: htmlspecialchars() native fast path (ENT_QUOTES, UTF-8) #124, Web: Runtime-populated superglobals for JIT and AOT (per-request $_GET/$_POST) #49

Files

• examples/003-MiniWebApp/