README.md still points at the two starter repos under the personal account:

• Unisay/purescript-lua-template (README line 28, "template repository")
• Unisay/purescript-lua-example (README line 30, the OpenResty/Nginx example)

Both should live under the purescript-lua org like the compiler and the forks.

Tasks

• Transfer purescript-lua-template and purescript-lua-example to the purescript-lua org (GitHub keeps redirects from the old Unisay/* URLs, but update them anyway).
• Update README.md links (and any other references) to the new purescript-lua/* URLs.
• In each repo, nix flake update so they pin the latest pslua and refresh their flake inputs.
• Point each project's package set at the latest Lua set release psc-0.15.15-20260615-2 (merged as upstream-ps // upstream-lua; drop any stale sha256: so spago re-freezes).
• Rebuild each (spago build / the project's build script) to confirm they still compile against the current toolchain + set, and refresh any committed CoreFn/Lua output.

Why

Keeps the onboarding path (template → example) consistent with the org, and ensures the starter projects actually build against the current compiler and the just-released FFI-fixed package set rather than a months-old pin.