fix: add Schedules to docs overview and add docs completeness rule

Add Schedules entry to Documentation Sections list in docs overview
(EN/ES). Add development guideline to CLAUDE.md requiring docs overview,
sidebar, and translations to be updated when adding new doc pages.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: barckcode

CLAUDE.md

@@ -17,3 +17,4 @@ Source code lives in `web/`. Deployments are automated via GitHub Actions on eve
 - **Validate UI changes with Playwright MCP** to ensure user flows work correctly end-to-end.
 - **Build validation** — if the project has a build step, run it and confirm it succeeds before committing.
 - **Tests are mandatory** — write e2e, functional, and unit tests for every new feature. Tests live in `web/tests/`.
+- **Docs completeness** — when adding a new documentation page, ALWAYS update: (1) the "Documentation Sections" list in the docs overview (`web/src/pages/docs/index.astro` and `web/src/pages/es/docs/index.astro`), (2) the sidebar in `web/src/layouts/DocsLayout.astro`, and (3) the translations in `web/src/i18n/ui.ts`.

web/src/pages/docs/index.astro

@@ -94,6 +94,10 @@ import DocsLayout from '../../layouts/DocsLayout.astro';
         <a href="/docs/skills"><strong>Skills</strong></a>:
         How to extend agent capabilities with installable skills.
       </li>
+      <li>
+        <a href="/docs/schedules"><strong>Schedules</strong></a>:
+        Automate recurring tasks with cron-based schedules and track run history.
+      </li>
       <li>
         <a href="/docs/architecture"><strong>Architecture</strong></a>:
         System components, messaging, container internals, and runtime design.

web/src/pages/es/docs/index.astro

@@ -94,6 +94,10 @@ import DocsLayout from '../../../layouts/DocsLayout.astro';
         <a href="/es/docs/skills"><strong>Habilidades</strong></a>:
         Como extender las capacidades de los agentes con habilidades instalables.
       </li>
+      <li>
+        <a href="/es/docs/schedules"><strong>Tareas Programadas</strong></a>:
+        Automatiza tareas recurrentes con programaciones basadas en cron y consulta el historial de ejecuciones.
+      </li>
       <li>
         <a href="/es/docs/architecture"><strong>Arquitectura</strong></a>:
         Componentes del sistema, mensajeria, internos del contenedor y diseno del runtime.