Repository navigation
fix(cli): set up unconfigured workspaces on start - #1975
Merged
Merged
Conversation
Assisted-by: Hermes-Agent:gpt-6-luna
4 of 21 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Unconfigured Signet workspaces now enter setup during daemon start, restart, or dashboard launch instead of failing before users can initialize them. Database-bearing workspaces missing manifests use recovery setup that preserves existing database contents. The curl installer also supports installing the latest nightly directly with
--nightly.Changes
signet setupguidance.--nightlyto the curl installer; resolve the nightly version, select its release assets, and forward other installer arguments unchanged.Type
fix— bug fixPackages affected
@signet/cli/ dashboard@signet/webScreenshots
Not applicable: this change modifies CLI setup and installer documentation, not a UI.
Testing
bun run typecheckpassesbun run lintpassesbun testpassesN/AFocused checks passed:
bun test surfaces/cli/src/features/setup-recovery.test.ts surfaces/cli/src/features/daemon.test.ts platform/core/src/workspace.test.ts scripts/install-shell-compat.test.ts— 55 passed.bun run --filter '@signet/cli' buildbunx biome check README.md dist/signetai/README.md scripts/install-shell-compat.test.ts surfaces/cli/src/cli.ts surfaces/cli/src/features/daemon.ts surfaces/cli/src/features/daemon.test.ts surfaces/cli/src/features/setup-migrate.ts surfaces/cli/src/features/setup.ts surfaces/cli/src/features/setup-recovery.test.tsbash -n web/marketing/public/install.shandzsh -n web/marketing/public/install.shgit diff --checkbun test surfaces/cli/src/features/setup.test.tsreports 43 passed and 2 failed on both this branch andorigin/main: one existing onboarding test expects a dynamically allocated server port but receives the default port, and the related unavailable-workspace case times out. These failures reproduce on the unchanged base.AI disclosure
Assisted-bytags in commits)Notes
bun scripts/doc-drift.tsexits 1 on bothorigin/mainand this branch because the API reference lists 35 routes not found by the current source inventory; this change does not modify API routes.