// `const` now: the entry is no longer reassigned here, because
// `ensureGameRender()` moved inside the render callback below and
// its upgraded copy is consumed there.
* Phase 5 (boot decomposition) will move the runtime facade
* assembly here as well — a single `attachPublicApi(services)`
* function that wires every `wp.os.*` method in one place.
* Until then, the runtime assembly continues to live in
* `src/desktop.ts`.
* Phase 3 only ships drag-within-folder. Cross-folder drags
* (drop into a folder, drop out to root) and the Recycle Bin
* drop integration land in later phases.
// v1: no-op. Phase 4 will populate this from the push payload.
// We claim the event so a hosting environment that signs us up
// for a push subscription before the v2 PR lands doesn't see
// silently-dropped pushes — the empty handler still satisfies
// `Notification` capability checks on browsers that gate them.
There is a certain taste to not drop comments like this, but there is a tendency to do this in AI. They drop references to phases of work and outdated architecture in ways that aren't helpful and then don't get cleaned up.
They tend to be wordy, long, and leak chatbot history or project management in unimportant ways that just distract.
I could point this out in my own code, but I don't need to since a vibe coded GitHub repo is linked in this very article.
> https://github.com/WordPress/openstation/blob/dd21eb131a2029...
> https://github.com/WordPress/openstation/blob/dd21eb131a2029... > https://github.com/WordPress/openstation/blob/dd21eb131a2029... > https://github.com/WordPress/openstation/blob/dd21eb131a2029... There is a certain taste to not drop comments like this, but there is a tendency to do this in AI. They drop references to phases of work and outdated architecture in ways that aren't helpful and then don't get cleaned up.