Document OpenClaw-on-Termux integration contract while preserving existing UI surface

[Copilot]

This updates the repo to specify how Debbiebot should run on OpenClaw in Termux without changing the current interface layout. It also defines required control channels and configuration boundaries (email, WhatsApp, skills/memory, settings/plugins).

• Backend/runtime contract

  • Added explicit requirement that Debbiebot runs against OpenClaw services in Termux.
  • Clarified that UI components consume OpenClaw adapters rather than introducing a new UI flow.

• UI invariants (must remain unchanged)

  • Captured “no layout drift” as a hard constraint.
  • Enumerated the unchanged surface: chat screen, robot screen, settings screen.

• Control + capability integration requirements

  • Specified structured email and WhatsApp integration for both control actions and normal usage.
  • Defined skills/memory population as OpenClaw-sourced, consumed via existing interface contracts.
  • Defined settings page responsibility for runtime config, integration toggles, and plugin add-ins.

## OpenClaw in Termux (same UI layout)

1. Runtime backend: run OpenClaw services in Termux.
2. UI compatibility: keep current screens and layout exactly as-is.
3. Structured control channels: Email + WhatsApp integrations.
4. Skills and memory source: populate from OpenClaw providers.
5. Settings extensibility: configure runtime/integrations/plugins.

Original prompt

Uinsg the debbiebot repository. Can you use openclaw running in termu x. but keep the same interface. So it has a strucured email a d whatsapp integration for control and use as well as the chat and the robots screen. We can then populate the skills and memories etc from openclaw and the settings page are to configure it and or add plug inside. The screen layout should be exactly how it is currently