docs(issue-4): replace ESP32 with unified Raspberry Pi controller #5

Merged
rznz merged 1 commit from docs/4-replace-esp32-raspberry-pi into main 2026-10-20 10:06:09 +03:00
Owner

Issue

Closes #4

Summary

  • update README.md with the 5-point course checkpoint 1 specification (team members, topic, tasks, expected December 2026 outcome, and public Forgejo URL) targeting Raspberry Pi (Linux) and Android (Java)
  • replace the split ESP32 + separate Linux hub architecture in AGENTS.md and ARCHITECTURE.md with a unified Raspberry Pi controller that runs both the GPIO/peripheral I/O layer and the scenario/API hub
  • update sl workflow verification references (solve_workflow.md, schema.md) from ESP32 firmware compilation to Raspberry Pi service and hardware checks
  • record architectural decision D1 in task memory and regenerate docs/generated/ indexes

Acceptance Criteria

  • README.md contains the course proposal sections (team members and Forgejo handles, topic, tasks, expected December 2026 outcome, and public repository link) targeting Raspberry Pi and Android (Java).
  • AGENTS.md and ARCHITECTURE.md describe the Raspberry Pi as the unified embedded Linux physical controller and scenario/API hub, with optional VPS sync.
  • System context and core data flow in ARCHITECTURE.md connect the Android app directly to the Raspberry Pi hub over local REST/WebSocket and remove the separate ESP32 network hop.
  • Skill workflow references (solve_workflow.md, schema.md) reflect Raspberry Pi hardware/service verification instead of ESP32 firmware compilation.
  • Task memory (outcome.md) records the architectural decision and regenerates docs/generated/ indexes cleanly.

Verification

  • Automated:
    • rg -i esp32 README.md AGENTS.md ARCHITECTURE.md GITFLOW.md .agents/skills/sl (0 matches)
    • uv run .agents/skills/sl/task-memory/scripts/rebuild-task-index.py
    • uv run .agents/skills/sl/task-memory/scripts/publish-to-docs.py
    • python3 .agents/skills/sl/scripts/validate_branch.py
    • python3 .agents/skills/sl/scripts/validate_commit.py --message "docs(issue-4): replace ESP32 with unified Raspberry Pi controller"
    • git diff --check
  • Manual Android/device/hardware: not applicable (documentation and architecture slice)
  • Offline/reconnect, when relevant: ARCHITECTURE.md preserves offline local-network operation on the Raspberry Pi when the optional VPS is unreachable

Documentation and architecture

  • README.md, ARCHITECTURE.md, protocol, or assembly docs are updated or not affected.
  • No secrets, local state, generated debug output, or unrelated changes are included.

AI assistance

  • Prompt log: docs/prompts/4-replace-esp32-raspberry-pi.md
  • Task outcome: .agents/work/tasks/4-replace-esp32-raspberry-pi/outcome.md

Review

  • Branch follows <type>/<issue>-<english-kebab-slug>.
  • Work is complete without a feature flag.
  • A teammate other than the author (echo1) is requested, and immediate merge is authorized by the user so the public README.md is live for course checkpoint 1 submission.
  • Squash message will use docs(issue-4): replace ESP32 with unified Raspberry Pi controller.
## Issue Closes #4 ## Summary - update `README.md` with the 5-point course checkpoint 1 specification (team members, topic, tasks, expected December 2026 outcome, and public Forgejo URL) targeting Raspberry Pi (Linux) and Android (Java) - replace the split ESP32 + separate Linux hub architecture in `AGENTS.md` and `ARCHITECTURE.md` with a unified Raspberry Pi controller that runs both the GPIO/peripheral I/O layer and the scenario/API hub - update `sl` workflow verification references (`solve_workflow.md`, `schema.md`) from ESP32 firmware compilation to Raspberry Pi service and hardware checks - record architectural decision D1 in task memory and regenerate `docs/generated/` indexes ## Acceptance Criteria - [x] `README.md` contains the course proposal sections (team members and Forgejo handles, topic, tasks, expected December 2026 outcome, and public repository link) targeting Raspberry Pi and Android (Java). - [x] `AGENTS.md` and `ARCHITECTURE.md` describe the Raspberry Pi as the unified embedded Linux physical controller and scenario/API hub, with optional VPS sync. - [x] System context and core data flow in `ARCHITECTURE.md` connect the Android app directly to the Raspberry Pi hub over local REST/WebSocket and remove the separate ESP32 network hop. - [x] Skill workflow references (`solve_workflow.md`, `schema.md`) reflect Raspberry Pi hardware/service verification instead of ESP32 firmware compilation. - [x] Task memory (`outcome.md`) records the architectural decision and regenerates `docs/generated/` indexes cleanly. ## Verification - Automated: - `rg -i esp32 README.md AGENTS.md ARCHITECTURE.md GITFLOW.md .agents/skills/sl` (0 matches) - `uv run .agents/skills/sl/task-memory/scripts/rebuild-task-index.py` - `uv run .agents/skills/sl/task-memory/scripts/publish-to-docs.py` - `python3 .agents/skills/sl/scripts/validate_branch.py` - `python3 .agents/skills/sl/scripts/validate_commit.py --message "docs(issue-4): replace ESP32 with unified Raspberry Pi controller"` - `git diff --check` - Manual Android/device/hardware: not applicable (documentation and architecture slice) - Offline/reconnect, when relevant: `ARCHITECTURE.md` preserves offline local-network operation on the Raspberry Pi when the optional VPS is unreachable ## Documentation and architecture - [x] `README.md`, `ARCHITECTURE.md`, protocol, or assembly docs are updated or not affected. - [x] No secrets, local state, generated debug output, or unrelated changes are included. ## AI assistance - Prompt log: `docs/prompts/4-replace-esp32-raspberry-pi.md` - Task outcome: `.agents/work/tasks/4-replace-esp32-raspberry-pi/outcome.md` ## Review - [x] Branch follows `<type>/<issue>-<english-kebab-slug>`. - [x] Work is complete without a feature flag. - [x] A teammate other than the author (`echo1`) is requested, and immediate merge is authorized by the user so the public `README.md` is live for course checkpoint 1 submission. - [x] Squash message will use `docs(issue-4): replace ESP32 with unified Raspberry Pi controller`.
rznz requested review from echo1 2026-10-20 10:05:15 +03:00
rznz merged commit 522e74e5e7 into main 2026-10-20 10:06:09 +03:00
rznz deleted branch docs/4-replace-esp32-raspberry-pi 2026-10-20 10:06:10 +03:00
Sign in to join this conversation.
No description provided.