Skip to content

Create standalone leddy-esp32 repository from the native ESP-IDF port #5

Description

@ORESoftware

Goal

Create public led-dynamo/leddy-esp32 and extract the merged native ESP32-S3/ESP-IDF implementation from leddy-arduino/src/ports/esp32-idf without changing the capability or renderer-hook contract.

Acceptance criteria

  • public led-dynamo/leddy-esp32 repository exists with standard org governance files
  • ESP-IDF + FreeRTOS firmware builds for esp32-s3-devkitc-1
  • shared embedded capability/frame-planning layer and host tests are preserved
  • device hello advertises platform=esp32 and usb_serial, wifi, ble
  • CI runs native tests and ESP-IDF compilation
  • leddy-monorepo optional submodule/fleet entries are updated
  • leddy-arduino removes the extracted native port after downstream references move
  • organization docs and Linear links are updated

Publication readiness

leddy-arduino PR #3 provides deterministic standalone-tree extraction:

bash scripts/extract-controller-repo.sh esp32 /tmp/leddy-esp32

PR #4 adds reproducible leddy-esp32.tar.gz generation, SHA-256 sidecars, and controller-artifacts.json, with CI requiring byte-identical repeated packaging.

PR #5 is now merged and adds the network-ready publisher:

export GH_TOKEN='...'
bash scripts/publish-controller-repos.sh esp32

The publisher creates the missing public org repository through GitHub REST, publishes the extracted tree, initializes main and dev, keeps the PAT environment-only, and refuses to overwrite a repository that already contains branches. All five PR #5 CI jobs passed.

The replacement PAT was exercised against this path from the current runtime. It fails before authentication at DNS resolution (curl: (6) Could not resolve host: api.github.com), confirming the remaining blocker is outbound network reachability rather than token selection or code packaging.

Existing implementation

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