Skip to content

v0.4.1 Stable

This is the canonical public release page for the stable patch release that hardens Skylattice's Hosted Alpha deployment story.

What This Release Proves

  • Skylattice now distinguishes preview, local development, Hosted Alpha blocked state, and real paired control more explicitly
  • production-style Hosted Alpha deployments no longer silently fall back to local-file control-plane state
  • the repository now includes a more complete deployment contract for Vercel, Neon, GitHub OAuth, and control-plane bootstrap

What Works Today

  • skylattice doctor
  • governed task-agent runs with deterministic edit modes, reviewed memory context, and recovery-aware GitHub collaboration sync
  • skylattice memory ... review, search, export, and rollback flows
  • technology-radar runs with GitHub/GitLab discovery configuration, provider-tagged evidence, and bounded promotion metadata
  • skylattice web status, web pair, and web connector ...
  • hosted web workspaces for dashboard, tasks, radar, memory, commands, devices, approvals, and connect flows
  • Hosted Alpha deployment checks and SQL bootstrap through npm run web:hosted-alpha:check and npm run web:hosted-alpha:bootstrap
  • public proof artifacts and Pages landing pages for cold visitors

Verify It

Why This Patch Matters

v0.4.0 introduced the hosted web control-plane foundation. v0.4.1 makes that story safer and more deployable: better blocked-mode semantics, better browser/runtime boundary clarity, better maintainer setup paths, and more reliable web builds.

Known Limits

  • there is still not yet a public hosted deployment URL for the web app in this repository alone
  • the real Hosted Alpha deployment still requires Vercel, Neon, and GitHub OAuth setup outside the repo
  • task execution remains text-native rather than AST-aware
  • meaningful task planning still depends on OPENAI_API_KEY
  • the project is still early if you need a polished multi-user hosted platform