gitspace 0.2.0-rc.13 → 0.2.0-rc.15

package/.claude/settings.local.json

@@ -3,7 +3,8 @@
     "allow": [
       "Bash(gh api:*)",
       "Bash(gh search code:*)",
-      "Bash(curl:*)"
+      "Bash(curl:*)",
+      "Bash(bun scripts/build.ts:*)"
     ]
   }
 }

package/.gitspace/select/01-status.sh

@@ -3,9 +3,8 @@
 #
 # This runs every time you switch to an existing workspace.
 #
-# Bundle values are available as environment variables:
-#   SPACE_VALUE_<KEY> - Regular values from input steps
-#   SPACE_SECRET_<KEY> - Secret values from secret steps
+# Bundle values are available as environment variables using bundle key names.
+# Example: DEVELOPERNAME, EXAMPLEAPITOKEN
 
 WORKSPACE_NAME=$1
 REPOSITORY=$2
@@ -15,14 +14,14 @@ echo "=== Workspace: $WORKSPACE_NAME ==="
 echo ""
 
 # Show bundle values (proof of concept)
-if [ -n "$SPACE_VALUE_DEVELOPERNAME" ]; then
-  echo "Welcome back, $SPACE_VALUE_DEVELOPERNAME!"
+if [ -n "$DEVELOPERNAME" ]; then
+  echo "Welcome back, $DEVELOPERNAME!"
 fi
 
 # Show that we have access to the secret (masked)
-if [ -n "$SPACE_SECRET_EXAMPLEAPITOKEN" ]; then
+if [ -n "$EXAMPLEAPITOKEN" ]; then
   # Only show first 4 characters to prove we have access
-  TOKEN_PREVIEW="${SPACE_SECRET_EXAMPLEAPITOKEN:0:4}..."
+  TOKEN_PREVIEW="${EXAMPLEAPITOKEN:0:4}..."
   echo "API Token available: $TOKEN_PREVIEW (stored in OS keychain)"
 fi
 

package/AGENTS.md

@@ -128,22 +128,21 @@ src/
 │   │   └── ProjectList.tui.tsx
 │   ├── providers/              # Machine access abstraction
 │   │   ├── MachineProvider.ts  # Interface definition
-│   │   ├── LocalMachineProvider.ts  # Direct tmux-lite access
-│   │   └── RemoteMachineProvider.ts # Via relay
+│   │   └── LocalMachineProvider.ts  # Direct tmux-lite access
 │   ├── hooks/
-│   │   └── useNavigation.ts    # Navigation state management
+│   │   └── useUserActivity.ts  # Activity tracking for notifications
 │   └── types.ts                # Shared type definitions
 ├── tui/                        # Terminal UI (OpenTUI)
 │   ├── index.ts                # TUI entry point
 │   ├── app.tsx                 # Main TUI application
-│   ├── state.ts                # State management
-│   ├── adapters.ts             # Local/remote machine adapters
 │   ├── components/
-│   │   └── Terminal.tsx        # Embedded terminal
+│   │   ├── RemoteMachineScreen.tsx # Remote machine browser screen
+│   │   └── RemoteTerminal.tsx  # Embedded session terminal
 │   └── hooks/
-│       ├── useAppState.ts
 │       ├── useRemoteMachines.ts
-│       └── useInboxTUI.ts
+│       ├── useRemoteTerminal.ts
+│       ├── useLocalSession.ts
+│       └── useDaemonStatus.ts
 ├── web/                        # Web application (Vite + React)
 │   └── src/
 │       ├── App.tsx             # Main web app
@@ -335,7 +334,7 @@ interface MachineProvider {
 ```
 
 - `LocalMachineProvider`: Direct filesystem + tmux-lite CLI
-- `RemoteMachineProvider`: Via relay WebSocket
+- Remote machine access in UI now uses shared relay/session hooks + backend adapters (`shared/relay/*`, `shared/session/*`)
 
 ## Development Workflow
 

package/README.md

@@ -118,11 +118,11 @@ A bundle is a directory (typically `.gitspace/`) containing:
 .gitspace/
 ├── bundle.json           # Bundle manifest with onboarding steps
 └── scripts/
-    ├── pre/              # Scripts to run before setup
+    ├── pre/              # Deprecated: migrate scripts into ordered setup/
     │   └── 01-copy-env.sh
-    ├── setup/            # Scripts to run on first workspace creation
+    ├── setup/            # Scripts for setup runs (when bundle/value state changes)
     │   └── 01-install-deps.sh
-    ├── select/           # Scripts to run every time workspace is opened
+    ├── select/           # Scripts to run on each new terminal attach
     │   └── 01-status.sh
     └── remove/           # Scripts to run before workspace deletion
         └── 01-cleanup.sh
@@ -180,10 +180,10 @@ A bundle is a directory (typically `.gitspace/`) containing:
 
 ### Using Bundle Values in Scripts
 
-Bundle values are passed to scripts as environment variables:
+Bundle values are passed to scripts as environment variables using the configured bundle keys:
 
-- `SPACE_VALUE_<KEY>` - Regular values from input steps
-- `SPACE_SECRET_<KEY>` - Secret values from secret steps (fetched from OS keychain)
+- `<KEY>` - Regular or secret value using the exact `configKey` from `bundle.json`
+- Legacy aliases `SPACE_VALUE_<KEY>` / `SPACE_SECRET_<KEY>` are also provided for compatibility
 
 **Example script:**
 
@@ -195,12 +195,12 @@ WORKSPACE_NAME=$1
 REPOSITORY=$2
 
 # Access bundle values
-if [ -n "$SPACE_VALUE_TEAMNAME" ]; then
-  echo "Welcome, $SPACE_VALUE_TEAMNAME team!"
+if [ -n "$TEAMNAME" ]; then
+  echo "Welcome, $TEAMNAME team!"
 fi
 
 # Access secrets (stored securely in OS keychain)
-if [ -n "$SPACE_SECRET_APIKEY" ]; then
+if [ -n "$APIKEY" ]; then
   echo "API Key configured"
 fi
 ```
@@ -363,9 +363,9 @@ inside each workspace so they can vary by branch:
 ```
 ~/gitspace/<project-name>/workspaces/<workspace-name>/.gitspace/
 └── scripts/
-    ├── pre/       # Run before setup (terminal)
-    ├── setup/     # Run once on workspace creation
-    ├── select/    # Run every time workspace is opened
+    ├── pre/       # Deprecated: run before setup (migrate to setup/)
+    ├── setup/     # Run when setup state requires refresh
+    ├── select/    # Run on each new terminal attach
     └── remove/    # Run before workspace deletion
 ```
 
@@ -375,15 +375,15 @@ inside each workspace so they can vary by branch:
 2. Scripts run **alphabetically** (use `01-`, `02-` prefixes)
 3. **Working directory**: The workspace directory
 4. **Arguments**: `$1` = workspace name, `$2` = repository name
-5. **Environment**: Bundle values available as `SPACE_VALUE_*` and `SPACE_SECRET_*`
+5. **Environment**: Bundle values available by key name (for example `REGION`, `PULUMI_ACCESS_TOKEN`)
 
 #### Script Phases
 
 | Phase | When | Use Case |
 |-------|------|----------|
-| `pre/` | Once, before setup | Copy .env files, create directories |
-| `setup/` | Once, on workspace creation | Install dependencies, initial build |
-| `select/` | Every workspace open | Git fetch, status checks |
+| `pre/` | Deprecated | Move scripts into ordered `setup/` files |
+| `setup/` | When setup state changes | Install dependencies, initial build |
+| `select/` | Every new terminal attach | Git fetch, status checks |
 | `remove/` | Before deletion | Cleanup, notifications |
 
 ### Environment Variables
@@ -393,8 +393,9 @@ inside each workspace so they can vary by branch:
 export SPACES_CURRENT_PROJECT="my-app"
 
 # Available in scripts (from bundle onboarding):
-# SPACE_VALUE_<KEY>    - Regular values
-# SPACE_SECRET_<KEY>   - Secret values (from OS keychain)
+# <KEY>                - Value by bundle config key name
+# SPACE_VALUE_<KEY>    - Legacy alias for regular values
+# SPACE_SECRET_<KEY>   - Legacy alias for secret values
 ```
 
 ## Directory Structure
@@ -592,7 +593,7 @@ Error: GitHub CLI is not authenticated
 
 ### Bundle secrets not available
 
-If `SPACE_SECRET_*` variables are empty, ensure:
+If expected bundle key environment variables are empty, ensure:
 1. You completed the onboarding secret steps
 2. Your OS keychain service is running (libsecret on Linux, Keychain on macOS)
 

package/docs/CONNECTION.md

@@ -4,7 +4,7 @@ This document describes how GitSpace handles WebSocket connections, disconnectio
 
 > **Related:** See [PROTOCOL.md](./PROTOCOL.md) for message/frame format, [REMOTE-DESIGN.md](./REMOTE-DESIGN.md) for security model.
 
-> **Implementation Note:** The web client (`src/web/`) currently lacks the
+> **Implementation Note:** The web client tooling (`web/`) currently lacks the
 > auto-reconnection logic described below. While the relay connection has a
 > 15-second heartbeat, neither the relay nor terminal connections implement
 > exponential backoff reconnection. This is a known gap - disconnections

package/docs/REMOTE-DESIGN.md

@@ -293,14 +293,18 @@ Key responsibilities:
 **Role:** User interface, decryption endpoint
 
 ```
-src/web/src/
-├── App.tsx                     # Main application
+web/
+├── index.html                  # Vite entry document
+└── main.tsx                    # Lightweight web entrypoint
+
+src/
+├── app.web.tsx                 # Main web application
 ├── hooks/
-│   ├── useRelayConnection.ts   # WebSocket + machine list
-│   └── useTerminal.ts          # Terminal session management
+│   ├── useRelayConnection.web.ts
+│   └── useTerminal.web.ts
 ├── components/
-│   └── Terminal.tsx            # xterm.js wrapper
-└── lib/crypto/                 # Client-side X3DH + encryption
+│   └── SessionTerminal.web.tsx
+└── session/crypto/             # Client-side X3DH + encryption
 ```
 
 Key responsibilities:
@@ -319,10 +323,11 @@ src/
 ├── commands/connect.ts         # CLI connect command
 ├── tui/
 │   ├── app.tsx                 # TUI application
-│   ├── adapters.ts             # Machine provider adapters
-│   └── hooks/useRemoteMachines.ts
-└── shared/providers/
-    └── RemoteMachineProvider.ts
+│   ├── hooks/useRemoteMachines.ts
+│   └── hooks/useRemoteTerminal.ts
+└── shared/
+    ├── relay/                  # Shared relay directory client/hooks
+    └── session/                # Shared session backends + engine
 ```
 
 ---

package/docs/ROADMAP.md

@@ -159,7 +159,7 @@ VM-per-workspace isolation using Lima. Works on all Apple Silicon (M1/M2/M3+).
 - `src/core/lima/manager.ts` - VM lifecycle (start/stop/status)
 - `src/core/lima/config.ts` - Generate Lima YAML from workspace config
 - `src/core/lima/connection.ts` - Connect to tmux-lite inside VM
-- `src/shared/providers/LimaMachineProvider.ts` - MachineProvider implementation
+- `src/session/backends/lima-session-backend.ts` - Session backend implementation
 
 **Session Lifecycle:**
 1. User selects workspace in TUI

package/docs/SITE_DOCS_FIGMA_MAKE.md

@@ -297,7 +297,7 @@ Script execution rules:
 - Scripts run alphabetically (use `01-`, `02-` prefixes)
 - Working directory: The workspace directory
 - Arguments: `$1` = workspace name, `$2` = repository name
-- Environment: Bundle values available as `SPACE_VALUE_*` and `SPACE_SECRET_*`
+- Environment: Bundle values available by key name (for example `REGION`, `PULUMI_ACCESS_TOKEN`)
 
 Example script (`.gitspace/scripts/select/01-status.sh`):
 ```bash
@@ -377,14 +377,15 @@ Using bundle values in scripts:
 ```bash
 #!/bin/bash
 # Values available as environment variables:
-# SPACE_VALUE_<KEY>   - Regular values from input steps
-# SPACE_SECRET_<KEY>  - Secret values from secret steps (from OS keychain)
+# <KEY>               - Value by bundle config key name
+# SPACE_VALUE_<KEY>   - Legacy alias for regular values
+# SPACE_SECRET_<KEY>  - Legacy alias for secret values
 
-if [ -n "$SPACE_VALUE_TEAMNAME" ]; then
-  echo "Welcome, $SPACE_VALUE_TEAMNAME team!"
+if [ -n "$TEAMNAME" ]; then
+  echo "Welcome, $TEAMNAME team!"
 fi
 
-if [ -n "$SPACE_SECRET_APIKEY" ]; then
+if [ -n "$APIKEY" ]; then
   echo "API Key configured"
 fi
 ```
@@ -629,7 +630,7 @@ gssh identity init --label "My Device"
 
 ### Bundle/Secrets Issues
 
-**"SPACE_SECRET_* variables are empty"**
+**"Bundle key variables are empty"**
 1. Ensure you completed onboarding secret steps
 2. Check OS keychain is accessible:
    - macOS: Keychain Access should be running
@@ -959,8 +960,8 @@ Bundles allow teams to share onboarding configurations. Place in `.gitspace/`:
 
 **Using values in scripts:**
 ```bash
-echo "Team: $SPACE_VALUE_TEAMNAME"
-echo "Has API key: $SPACE_SECRET_APIKEY"
+echo "Team: $TEAMNAME"
+echo "Has API key: $APIKEY"
 ```
 
 ---