Skip to content

Track the Leddy cross-repository delivery roadmap #9

Description

@ORESoftware

Purpose

This is the organization-level governance issue for the Leddy delivery program and the canonical issue to place on led-dynamo-project.

Source-of-truth links

Current gates

  • Merge leddy-lib#2 for playback lifecycle and physical LED-chain ordering. Squash commit: 2a9a0cd.
  • Publish the organization roadmap through .github#8. Squash commit: 1991812.
  • Merge Claude's leddy-cli#4 with modular flags-2-env commands and canonical offline preview. Squash commit: 5adb8c6.
  • Merge leddy-api-server.rs#3 for reconnect desired-state replay and duplicate suppression. Squash commit: 3171b44.
  • Complete DEN-2343: software-only API → virtual device → renderer → E2E path. leddy-e2e#3 passed the full live-system workflow and merged as 907939c.
  • Merge the Raspberry Pi software runtime foundation in leddy-rasp-pi#2. Squash commit: 7ce0089.
  • Complete DEN-2893: first physical topology is five chained 64×32 HUB75 RGB panels (320×32 physical canvas around a max 300×20 logical viewport), external fused 5V panel power, active 3.3V→5V level shifting, and a separately packaged rpi-rgb-led-matrix helper. leddy-rasp-pi#3 merged as 50e2660.
  • Merge the software implementation of the GPL-scoped HUB75 helper in leddy-rasp-pi#4, merged as 9b9e4c5. Rust CI and the C++20 helper protocol/mapping job are green.
  • Complete DEN-2346: physical Raspberry Pi matrix. The remaining acceptance work is DEN-2961: build against a pinned upstream driver on a real Pi, record exact panel/adapter/power BOM and measured current, then attach physical soak/reconnect/clear/shutdown evidence.
  • Complete DEN-2349: Arduino/ESP32 firmware parity. leddy-arduino#2 passed host-native, Arduino ESP32, native ESP-IDF ESP32-S3, and STM32Cube HAL lanes and merged as 4aa3154.
  • Complete DEN-2352: authenticated WhatsApp connector. Group/channel capability verification is active in DEN-2898; public Cloudflare ingress stays deferred until the supported official event surface is known.

Coordination policy

GitHub owns code, reviews, checks, releases, artifacts, and runtime evidence. Linear owns priority, milestones, dependencies, and status. Update this issue with merged PR and release links; update Linear when scope, sequencing, ownership, or health changes.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions