Code design

[enyst]

Clone yourself enyst.github.io and see how it's structured; then analyze this repository deeply and create a new 'arch' page alongside the other pages to document the architecture of openhands automations. Feel free to clone also agent-canvas to see how they're used; and/or typescript-client.

[enyst]

@OpenHands can you do this?

[openhands-ai]

@enyst your session has expired. Please login again at OpenHands Cloud and try again.

[enyst]

@OpenHands can you do this

[openhands-ai]

I'm on it! enyst can track my progress at all-hands.dev

[openhands-ai]

Since the last summary, there are no additional code or repository changes.

Checklist:

• ✅ Issue Code design #175’s request was addressed: a new /arch page was added to document OpenHands Automations architecture.
• ✅ The page follows the referenced architecture-note style: system overview, lifecycle, state machine, data model, execution modes, injected env vars, and design boundaries.
• ✅ Routing was updated so /arch resolves correctly before the dynamic :automationId route.
• ✅ The automations list now links to the Architecture page.
• ✅ Tests were added for the new page and navigation link.
• ✅ Validation passed:
  • cd frontend && npm run test -- architecture automations-list
  • cd frontend && npm run lint
  • cd frontend && npm run build
• ✅ Changes were committed and a PR was opened: docs: add automations architecture page #176
• ✅ The PR description includes Fixes #175 and an AI-generated disclosure note.

Conciseness:

• The changes are focused on the requested architecture page and minimal supporting route/navigation/test updates.
• No extraneous tracked changes were included.