docs(i18n): point tutorial entries at index pages

docs/user/develop/framework/events.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write docs/user/develop/framework/events.md
-events.md: 1d9fe5c8f5068de6ad8b2abaa85cf67be35c8459
+events.md: 17ce5f6c4a70e406b5e3d9e5dd26182f62dc9868
 events.zh.md: 6936a5ad6c51393d2fbcd5103d4e418ce010d569

docs/user/develop/framework/events.md

@@ -139,5 +139,5 @@ export function apply(ctx: Context) {
 
 ## Next steps
 
-- [Capability layering](../practice/) — understand events within capability interfaces
+- [Capability layering](../practice/index.md) — understand events within capability interfaces
 - [LLM adapters](../practice/llm-adapter.md) — implement a complete LLM backend

docs/user/develop/framework/service.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write docs/user/develop/framework/service.md
-service.md: 03f4e7dc4df934495a4b203066183753b621339e
+service.md: 1bcfe2e7690d9f93b871500660e0fbe1e3439b3f
 service.zh.md: b275c3d200fb50b1fab0e762d0154477c7ca4447

docs/user/develop/framework/service.md

@@ -145,4 +145,4 @@ The repository generates the service names, public methods, and source locations
 ## Next steps
 
 - [Event system](./events.md) — communicate between plugins without tight coupling
-- [Capability layering](../practice/) — use services as capability interfaces
+- [Capability layering](../practice/index.md) — use services as capability interfaces