Development pulse.
Current work, meaningful activity, release boundaries and a dated snapshot of Nebulah development.
Live public repository pulse
NO LOGIN REQUIREDCurrent work
ACTIVEConsole acceptance
Build Revision 30 on the configured Windows RXDK/XDK environment and run the recovery/storage-review console checklist with the matching manifest and reports.
Enrollment + mount revalidation
Resolve mount ownership/revalidation before connecting existing writer/token primitives. Session review is not write authority.
Cover-card acceptance
Verify compact card width, narrow-phone wrapping and persisted fetched cover artwork in a real browser/Windows/console path.
Transfer + device coverage
Complete file-size, cancellation, disconnect/reconnect, phone layout, multi-console and broader compatibility checks without weakening transfer recovery.
Meaningful activity
LATEST SNAPSHOTKeep shortcut cards compact and persist fetched cover artwork — Trial 6.
Preserve paired browser sessions across refresh with 300-second idle expiry — Trial 5.
Persist local game-data JSON and remember Neighborhood console profiles — Trial 4.
Controlled launch recovery and read-only storage review — Revision 30.
Browse live scans and stop/restart safely — Revision 29.
Public modular bot release with Windows launcher and clean terminal output.
Development timeline
Fresh/reopen and synthetic recovery gates established.
Migration and state-preservation work moved forward.
Temporary scan results entered the full UI.
Targeted console launch success recorded; not universal compatibility.
Browse results while scanning, stop safely and rescan.
Controlled launch recovery and read-only storage enrollment review.
Longer-term planning
Recovery & safe mode
Broader renderer/platform/module failure recovery and safe/alternate boot behavior remain open planning areas.
Plugin runtime
Plugin ABI, capability negotiation, validated load/unload and recovery are planned; runtime loading is not currently implemented.
Versioned API
Dash-hosted authenticated/versioned local APIs remain a separate milestone; Link's current local bridge does not close that scope.
Known limits
Testing details →- Dash normal persistent scanner commits: disabled while enrollment, durable identity and hardware durability remain gated.
- Link runtime extensions: plugin loading, trainers, title-update management, GSC injection, screenshots and live console video remain unimplemented.
- Transfers: 128 MiB per file; cancellation is bounded by the active console operation and retained partial files are reported.
- Link compatibility: automated host checks are not a substitute for real Windows, browser, phone and console acceptance.
- Public demo: simulated only; it cannot connect to a console or expose a pairing token/CPU key.