npm - @bytetrue/byspace - Versions diffs - 0.2.0-beta.4 → 0.2.0 - Mend

@bytetrue/byspace 0.2.0-beta.4 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (39) hide show

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/_expo/static/js/web/index-ba698ed4743a3ed98c16928de3e54cb1.js.br ADDED Viewed

Binary file

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/_expo/static/js/web/index-ba698ed4743a3ed98c16928de3e54cb1.js.gz ADDED Viewed

Binary file

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/index.html CHANGED Viewed

@@ -85,6 +85,6 @@
   <body>
     <noscript>You need to enable JavaScript to run this app.</noscript>
     <div id="root"></div>
-  <script src="/_expo/static/js/web/index-38ca1829d34e8fa57f6076abc4391d37.js" defer></script>
+  <script src="/_expo/static/js/web/index-ba698ed4743a3ed98c16928de3e54cb1.js" defer></script>
 </body>
 </html>

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/index.html.br CHANGED Viewed

Binary file

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/index.html.gz CHANGED Viewed

Binary file

package/node_modules/@bytetrue/byspace-server/dist/skills/byspace/SKILL.md ADDED Viewed

@@ -0,0 +1,147 @@
+---
+name: byspace
+description: BySpace reference for managing agents and worktrees. Load whenever you need to create agents, send them prompts, or manage worktrees.
+---
+BySpace is a daemon that supervises AI coding agents on your machine. Control it through tools or a CLI.
+## Worktrees
+**`create_worktree`** — same target union as `create_agent.workspace.source.worktree.target`:
+- From a PR: `{ target: { kind: "checkout-pr", githubPrNumber: 503 } }`.
+- Branch off a base: `{ target: { kind: "branch-off", worktreeSlug: "foo", branchName: "fix/foo", baseBranch: "main" } }`.
+- Checkout an existing branch: `{ target: { kind: "checkout-branch", branch: "feat/bar" } }`.
+Returns `{ branchName, worktreePath, workspaceId }`. Pass `cwd` to target a specific repo.
+In `branch-off`, `worktreeSlug` controls the worktree path slug and `branchName` controls the git branch. If `branchName` is omitted, BySpace defaults it from `worktreeSlug`. The returned `branchName` is authoritative; checkout and PR flows may return a branch name that differs from any requested slug.
+**`list_worktrees`** — current repo (or pass `cwd`).
+**`archive_worktree`** — `{ worktreePath }` or `{ worktreeSlug }`. Removes worktree and branch.
+## Agents
+**`create_agent`** — required: `relationship`, `workspace`, `title`, `provider` (`claude/opus`, `codex/gpt-5.4`, …), `initialPrompt`. Common: `notifyOnFinish`, `settings`, `labels`. Returns `{ agentId, … }`.
+Initial runtime settings live under `settings`: `modeId`, `thinkingOptionId`, and provider-specific `features`. For Codex fast mode, pass `settings: { features: { "fast_mode": true } }` when creating the agent.
+To create a new worktree and launch an agent in it, use `create_agent.workspace.source.kind = "worktree"`. Use `create_worktree` separately only when you need a worktree without launching an agent, or when you need a split flow; in a split flow, pass the returned `workspaceId` to `create_agent` with `workspace: { kind: "existing", workspaceId }`.
+### Agent relationships
+`relationship` controls parentage only:
+- `{ kind: "subagent" }` — child under your subagents track. Use for advisors, committee members, planners, implementers, auditors, loop workers, and any agent whose lifetime belongs to your task.
+- `{ kind: "detached" }` — root/sibling agent. Use for handoffs and fire-and-forget delegations the user may continue after you are archived.
+`workspace` controls placement only:
+- `{ kind: "current" }` — same workspace as the caller, with optional `cwd`.
+- `{ kind: "existing", workspaceId: string, cwd?: string }` — attach to an existing workspace, usually from `create_worktree`.
+- `{ kind: "create", source: { kind: "directory", path?: string } }` — new workspace rooted at a directory.
+- `{ kind: "create", source: { kind: "worktree", cwd?: string, target: { kind: "branch-off", worktreeSlug?: string, branchName?: string, baseBranch?: string } } }`
+- `{ kind: "create", source: { kind: "worktree", cwd?: string, target: { kind: "checkout-branch", branch: string } } }`
+- `{ kind: "create", source: { kind: "worktree", cwd?: string, target: { kind: "checkout-pr", githubPrNumber: number } } }`
+Agent-scoped `create_agent` defaults `notifyOnFinish` to true. Set it to `false` only for truly fire-and-forget agents.
+**`send_agent_prompt`** — `{ agentId, prompt }`. Use for follow-ups to an existing agent. Agent-scoped prompt calls default to `background: true` and `notifyOnFinish: true`; top-level calls default to blocking with no callback. For a synchronous follow-up, pass `background: false` and use the returned result.
+**`update_agent`** — `{ agentId, name?, labels?, settings? }`. Use `settings` for runtime changes on an existing agent: `modeId`, `model`, `thinkingOptionId`, and provider-specific `features`. For Codex fast mode, pass `settings: { features: { "fast_mode": true } }`.
+**`list_agents`** — filter by `cwd`, `statuses`, `sinceHours`, `includeArchived`.
+**`archive_agent`** — `{ agentId }`. Interrupts if running, removes from active list.
+## Provider discovery
+**`list_providers`** — compact provider availability and modes.
+**`list_models`** — full model list for one provider. Use only when you need model IDs or thinking options; the list can be large.
+**`inspect_provider`** — compact provider capability and feature inspection. Required: `provider`; pass `cwd` when you are not in an agent-scoped session. Optional: `settings` with draft `model`, `modeId`, `thinkingOptionId`, and `features`.
+Only set feature IDs returned by `inspect_provider`. For Codex fast mode, look for `fast_mode` and pass `settings: { features: { "fast_mode": true } }` to `create_agent` or `update_agent`.
+## Schedules and heartbeats
+**`create_schedule`** — starts a new agent on a cron cadence. Required: `prompt`, `cron`, `provider`. Optional: `timezone`, `name`, `cwd`, `maxRuns`, `expiresIn`. Use when the recurring work should live in fresh agents.
+**`create_heartbeat`** — sends you a prompt on a cron cadence. Required: `prompt`, `cron`. Optional: `timezone`, `name`, `maxRuns`, `expiresIn`. Use for reminders, PR/build babysitting, and status checks that should return to this conversation.
+## Models
+`claude/sonnet` (default), `claude/opus` (harder reasoning), `codex/gpt-5.4` (frontier coding), `claude/haiku` (tests only).
+## Orchestration preferences
+User-specific configuration at `~/.byspace/orchestration-preferences.json`. **Before any BySpace skill chooses a provider or creates an agent, it must read this file.** Reading means an actual file read, not relying on these examples or defaults. Never hardcode a provider string in another skill — resolve through this file.
+Two parts:
+- `providers` — map of role categories to provider strings. Pass straight to `create_agent`'s `provider` field.
+- `preferences` — freeform string array. Read on startup; weave into agent prompts contextually.
+Categories: `impl`, `ui`, `research`, `planning`, `audit`. Skills pick the category that matches the role they're launching.
+```json
+{
+  "providers": {
+    "impl": "codex/gpt-5.4",
+    "ui": "claude/opus",
+    "research": "codex/gpt-5.4",
+    "planning": "codex/gpt-5.4",
+    "audit": "codex/gpt-5.4"
+  },
+  "preferences": [
+    "Claude Opus is the right choice for anything artistic or human-skill-oriented: copywriting, naming, UX copy, visual design, styling. Codex is the workhorse for mechanical work."
+  ]
+}
+```
+If the file is missing, use sensible defaults and tell the user once.
+## Waiting
+Agents take time — 10–30+ minutes is routine. Favor asynchronous workflows.
+For agent-scoped `create_agent` and background `send_agent_prompt`, leave `notifyOnFinish` omitted or set it to `true` unless the work is truly fire-and-forget. You will get notified when the target agent finishes, errors, or needs permission. Move on to other work. The notification arrives on its own.
+Don't poll `list_agents` or `get_agent_status` to "check on" a running agent. The notification will tell you.
+## CLI parity
+The `byspace` CLI is a thin wrapper over the same daemon. Same surface:
+```bash
+byspace run --provider codex/gpt-5.4 --mode full-access --worktree feat/x "<prompt>"
+byspace send <agent-id> "<follow-up>"
+byspace ls
+byspace worktree ls
+byspace schedule create --cron "*/15 * * * *" "ping main build"
+```
+Discover with `byspace --help` and `byspace <cmd> --help`.
+## Ops and debugging
+Daemon-client architecture: the daemon owns agent lifecycle, state, and the WebSocket API. The hosted Web app and CLI are clients.
+|                | Default                                                           |
+| -------------- | ----------------------------------------------------------------- |
+| Listen address | `127.0.0.1:6777` (override `BYSPACE_LISTEN`)                      |
+| Home           | `~/.byspace` (override `BYSPACE_HOME`)                            |
+| Daemon log     | `$BYSPACE_HOME/daemon.log`                                        |
+| Agent state    | `$BYSPACE_HOME/agents/<id>.json`                                  |
+| Worktrees      | `$BYSPACE_HOME/worktrees/` (or `worktrees.root` in `config.json`) |
+| PID file       | `$BYSPACE_HOME/byspace.pid`                                       |
+| Health         | `GET http://127.0.0.1:6777/api/health`                            |
+Debug order:
+1. `tail -n 200 ~/.byspace/daemon.log`.
+2. `byspace daemon status` for liveness.
+3. `curl -s localhost:6777/api/health` if the CLI itself is suspect.
+**Never restart the daemon without explicit user approval** — it kills every running agent, including, often, the one asking.

package/node_modules/@bytetrue/byspace-server/dist/skills/byspace-advisor/SKILL.md ADDED Viewed

@@ -0,0 +1,64 @@
+---
+name: byspace-advisor
+description: Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.
+user-invocable: true
+argument-hint: "[--provider <name>] <question or topic>"
+---
+# BySpace Advisor
+Single agent. Reads the situation you're in. Gives a judgment. You decide what to do — the advisor doesn't drive the work.
+**User's request:** $ARGUMENTS
+## Prerequisites
+Read the **byspace** skill. Before choosing a provider, read `~/.byspace/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the advisor until you have read it.
+## Picking the advisor
+1. **User named one** (`--provider claude/opus`) → use it.
+2. **Otherwise** resolve from preferences — pick the category that matches the question:
+   - Design / approach question → `planning`
+   - "Did I miss something" review → `audit`
+   - "Is this even right" → `research`
+3. **Contrast helps.** If your own provider matches what preferences would pick, swap to a different family on purpose — fresh perspective is the point.
+## The briefing
+The advisor has zero context. Make it self-contained:
+- The question, sharply.
+- What you've considered and what you've ruled out.
+- Relevant files by path (don't paste — let the agent read).
+- Explicit ask: "give me a recommendation, with reasoning."
+End with the no-edits suffix:
+```
+This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.
+```
+## Forwarded skills
+If `$ARGUMENTS` contains another skill reference — `/unslop`, `/unslop-risk`, `$unslop`, etc. — the user is asking the advisor to run that skill against the current task. Examples:
+- `/byspace-advisor /unslop` → advisor runs `/unslop` on the current diff.
+- `/byspace-advisor /unslop-risk` → advisor does an unslop-risk review.
+- `/byspace-advisor $diagnose this build failure` → advisor invokes `/diagnose`.
+Parse the forwarded skill name out of `$ARGUMENTS` (`/<name>` or `$<name>`). In the briefing, tell the advisor explicitly:
+```
+Invoke the `<name>` skill against this task. Load it via the Skill tool before doing anything else.
+```
+Pass through any remaining arguments after the skill name as the skill's own input. The advisor — not you — runs the skill; you're still just the orchestrator handing it the work.
+## Launch and synthesize
+Create the advisor agent via BySpace with a `[Advisor] <topic>` title and the briefing as the initial prompt. Wait for it to finish. Read its response. Synthesize for the user — the advisor's verdict + your recommendation.
+## Persistent advisor
+If the user wants ongoing input ("keep this advisor for the next few decisions"), don't archive after the first reply. Send follow-ups when you need another take. Archive when the user says they're done, or when the topic shifts and a fresh context would serve better.

package/node_modules/@bytetrue/byspace-server/dist/skills/byspace-committee/SKILL.md ADDED Viewed

@@ -0,0 +1,83 @@
+---
+name: byspace-committee
+description: Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.
+user-invocable: true
+---
+# Committee Skill
+Two agents from contrasting providers, fresh context, planning a solution in parallel. They stay alive for review after implementation.
+The purpose is to step back, not double down. The committee may propose a completely different approach.
+**User's additional context:** $ARGUMENTS
+## Prerequisites
+Read the **byspace** skill. Before choosing committee members, read `~/.byspace/orchestration-preferences.json` unless the user explicitly named providers in this request. Do not create committee agents until you have read it.
+Contrast is the point of a committee, so pick across providers deliberately using the configured preferences rather than hardcoded defaults.
+## Composition
+Two members with different reasoning styles, selected from orchestration preferences:
+- one planning/research-strength provider
+- one contrasting high-reasoning provider
+Override only when the user explicitly asks for different members.
+## Hard rules
+- **No edits.** Every prompt to a committee member ends with the no-edits suffix:
+  ```
+  This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.
+  ```
+- **Trust the wait.** Do not poll, send hurry-ups, or interrupt. GPT-5.4 can reason 15–30 minutes; Opus does extended thinking. Long waits mean it found something worth thinking about.
+- **You are the middleman.** Drive plan → implement → review without yielding to the user, except for divergences that need their call.
+## Phase 1: Plan
+Write a problem-level prompt:
+- High-level goal and acceptance criteria
+- Constraints
+- Symptoms (if a bug)
+- What you tried and why it failed
+- Explicit: "do root cause analysis"
+- Explicit: "state assumptions, ask why three levels deep, check whether you're patching a symptom or removing the problem"
+Create both agents in parallel via BySpace with `[Committee] <task>` titles and the same prompt. Wait for both — not just whichever finishes first.
+Read both responses. Challenge them — do not accept at face value:
+- "Why does <underlying thing> happen? Symptom or cause?"
+- Verify any assumption the plan makes about the code.
+- "What did you considered and reject?"
+Send follow-ups until the plan addresses root cause.
+Synthesize:
+- Convergence → unified plan.
+- Significant divergence → involve the user.
+Confirm the merged plan with both members. Multi-turn until consensus.
+## Phase 2: Implement
+Default: implement yourself. If the user said **"delegate"**, launch one impl agent and pass the merged plan.
+The committee stays clean — not involved in implementation.
+## Phase 3: Review
+Send the diff to the committee:
+> Implementation is done. Review changes against the plan. Flag drift or missing pieces. <no-edits suffix>
+Apply feedback yourself, or send to the impl agent. Repeat 2 → 3 until consensus.
+After ~10 iterations without convergence, start a fresh committee with the full history of what was tried — the current committee's context may have drifted too far.

package/node_modules/@bytetrue/byspace-server/dist/skills/byspace-handoff/SKILL.md ADDED Viewed

@@ -0,0 +1,71 @@
+---
+name: byspace-handoff
+description: Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.
+user-invocable: true
+---
+# Handoff Skill
+Transfer the current task — context, decisions, failed attempts, constraints — to a fresh agent. The receiving agent starts with **zero context**, so the handoff prompt must be a self-contained briefing.
+**User's arguments:** $ARGUMENTS
+## Prerequisites
+Read the **byspace** skill. Before choosing a provider, read `~/.byspace/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the receiving agent until you have read it.
+## Parsing arguments
+1. **Provider** — explicit user request first; otherwise resolve from `impl` preference (or `ui` if the task is styling-only).
+2. **Worktree** — "in a worktree" / "worktree" → create a worktree via BySpace with a short branch name derived from the task, based on the current branch.
+3. **Task description** — anything else the user said.
+## The handoff prompt
+The receiving agent has zero context. Include:
+```
+## Task
+[Imperative description.]
+## Context
+[Why this task exists, required context.]
+## Relevant files
+- `path/to/file.ts` — [what it is and why it matters]
+## Current state
+[What's done, what works, what doesn't.]
+## What was tried
+- [Approach] — [why it failed or was abandoned]
+## Decisions
+- [Decision — rationale]
+## Acceptance criteria
+- [ ] [Criterion]
+## Constraints
+- [Must-not / must-preserve]
+```
+**Preserve task semantics.** Investigate-only → "DO NOT edit files." Fix → "implement the fix." Refactor → "refactor, not rewrite." Carry the user's exact intent.
+## Launch
+Create the agent via BySpace with a `[Handoff] <task>` title, the briefing as initial prompt, and `relationship: { kind: "detached" }`.
+Use `workspace` for placement:
+- No worktree: `workspace: { kind: "current" }`.
+- Worktree: `workspace: { kind: "create", source: { kind: "worktree", target: { kind: "branch-off", worktreeSlug: "<short-task-slug>", branchName: "fix/<short-task-slug>" } } }`.
+- Existing worktree already created by `create_worktree`: `workspace: { kind: "existing", workspaceId: "<returned-workspace-id>" }`.
+Do not use `workspace: { kind: "current", cwd: "<worktreePath>" }` to place a handoff in a worktree; that keeps the agent in the caller's workspace with only a different runtime cwd.
+Leave `notifyOnFinish` omitted unless the user explicitly wants no callback.
+Handoff agents are siblings/root agents, not your subagents. They must survive you being archived and must not appear in your subagent track.
+Don't wait by default — the user decides whether to follow along or move on. Tell them the agent ID and how to follow along (the byspace skill explains).

package/node_modules/@bytetrue/byspace-server/dist/skills/byspace-loop/SKILL.md ADDED Viewed

@@ -0,0 +1,45 @@
+---
+name: byspace-loop
+description: Run an agent loop until an exit condition is met. Use when the user says "loop", "babysit", "keep trying until", "check every X", "watch", or wants iterative autonomous execution.
+user-invocable: true
+---
+# BySpace Loop Skill
+A loop is a worker/verifier cycle: launch a worker → check verification → repeat until done or limits hit. Use for "keep trying", "babysit", or "watch this until X."
+**User's arguments:** $ARGUMENTS
+## Prerequisites
+Read the **byspace** skill. Before choosing worker or verifier providers, read `~/.byspace/orchestration-preferences.json` unless the user explicitly named providers in this request. Do not start the loop until you have read it.
+Loops are a CLI primitive: `byspace loop run`. Manage with `byspace loop ls`, `byspace loop inspect <id>`, `byspace loop logs <id>`, `byspace loop stop <id>`.
+## Your job
+1. Understand the user's intent from `$ARGUMENTS` and the conversation.
+2. **Worker prompt** — self-contained, concrete about what to do this iteration, explicit about what counts as progress.
+3. **Verification** — pick the right shape:
+   - Shell check (`--verify-check`) for objective criteria a command can answer (`gh pr checks --fail-fast`, `npm test`).
+   - Verifier prompt (`--verify`) for judgment ("Return done=true only if all tests pass and the changed files are coherent. Cite the command and the outcome.").
+   - Both, when shell rules out the obvious failures and the verifier judges the rest.
+4. **Providers** — `--provider` for the worker, `--verify-provider` for the verifier. From preferences unless the user named them. For implementation loops, pair worker and verifier on different providers — each catches the other's blind spots.
+5. **Sleep** — `--sleep` only when polling something external. Otherwise let it run as fast as the loop completes.
+6. **Stops** — set a sensible `--max-iterations` and/or `--max-time`. Open-ended loops are how runaways happen.
+7. **Archive** — `--archive` keeps agents after each iteration for inspection.
+8. Launch with `byspace loop run`.
+## Common shapes
+**Babysit a PR** — worker checks PR state and fixes issues; shell check is `gh pr checks <n> --fail-fast`; sleep 2m; max-time 1h.
+**Drive tests to green** — worker investigates failures and fixes code; shell check is the test command; verifier confirms all tests pass; max-iterations 10.
+**Cross-provider implementation** — worker on `impl` provider, verifier on a different provider; verifier checks changed files, runs typecheck and tests; max-iterations and max-time both bounded; archive on so iterations can be inspected.
+## Prompt rules
+**Worker** — self-contained, concrete (commands, files, branches, tests, PRs, systems), explicit about what counts as progress this iteration.
+**Verifier** — checks facts, doesn't suggest fixes, cites commands/outputs/file evidence, specific about what "done" means.

package/node_modules/@bytetrue/byspace-server/package.json CHANGED Viewed

@@ -1,12 +1,13 @@
 {
   "name": "@bytetrue/byspace-server",
-  "version": "0.2.0-beta.4",
+  "version": "0.2.0",
   "private": true,
   "description": "BySpace backend server",
   "files": [
     "dist/server",
     "dist/src",
     "dist/scripts",
+    "dist/skills",
     "!dist/**/*.map",
     "README.md",
     ".env.example"
@@ -36,7 +37,7 @@
     "clean": "node ../../scripts/clean-package-dist.mjs",
     "build": "npm run build:lib && npm run build:scripts",
     "build:clean": "npm run clean && npm run build",
-    "build:lib": "tsc -p tsconfig.server.json --incremental false && node -e \"const fs=require('node:fs'); fs.mkdirSync('dist/server/server/speech/providers/local/sherpa/assets',{recursive:true}); fs.copyFileSync('src/server/speech/providers/local/sherpa/assets/silero_vad.onnx','dist/server/server/speech/providers/local/sherpa/assets/silero_vad.onnx'); fs.cpSync('src/terminal/shell-integration','dist/server/terminal/shell-integration',{recursive:true}); fs.cpSync('src/terminal/shell-integration','dist/src/terminal/shell-integration',{recursive:true}); fs.copyFileSync('src/terminal/terminal-ts-loader.mjs','dist/server/terminal/terminal-ts-loader.mjs');\"",
+    "build:lib": "tsc -p tsconfig.server.json --incremental false && node -e \"const fs=require('node:fs'); fs.mkdirSync('dist/server/server/speech/providers/local/sherpa/assets',{recursive:true}); fs.copyFileSync('src/server/speech/providers/local/sherpa/assets/silero_vad.onnx','dist/server/server/speech/providers/local/sherpa/assets/silero_vad.onnx'); fs.cpSync('src/terminal/shell-integration','dist/server/terminal/shell-integration',{recursive:true}); fs.cpSync('src/terminal/shell-integration','dist/src/terminal/shell-integration',{recursive:true}); fs.copyFileSync('src/terminal/terminal-ts-loader.mjs','dist/server/terminal/terminal-ts-loader.mjs'); fs.cpSync('../../skills','dist/skills',{recursive:true});\"",
     "build:scripts": "tsc -p tsconfig.scripts.json --incremental false && node -e \"const fs=require('node:fs'); fs.mkdirSync('dist/scripts',{recursive:true}); fs.copyFileSync('scripts/mcp-stdio-socket-bridge-cli.mjs','dist/scripts/mcp-stdio-socket-bridge-cli.mjs');\"",
     "prepack": "npm run build:clean && npm --prefix ../.. run build:daemon-web-ui",
     "start": "node dist/scripts/supervisor-entrypoint.js",

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@bytetrue/byspace",
-  "version": "0.2.0-beta.4",
+  "version": "0.2.0",
   "description": "BySpace CLI - control your AI coding agents from the command line",
   "repository": {
     "type": "git",
@@ -21,9 +21,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@bytetrue/byspace-client": "0.2.0-beta.4",
-    "@bytetrue/byspace-protocol": "0.2.0-beta.4",
-    "@bytetrue/byspace-server": "0.2.0-beta.4",
+    "@bytetrue/byspace-client": "0.2.0",
+    "@bytetrue/byspace-protocol": "0.2.0",
+    "@bytetrue/byspace-server": "0.2.0",
     "@clack/prompts": "^1.0.0",
     "chalk": "^5.3.0",
     "commander": "^12.0.0",
@@ -50,11 +50,11 @@
     "@lezer/yaml": "^1.0.4",
     "@replit/codemirror-lang-csharp": "^6.2.0",
     "lezer-elixir": "^1.1.2",
-    "@bytetrue/byspace-highlight": "0.2.0-beta.4",
+    "@bytetrue/byspace-highlight": "0.2.0",
     "zod": "^4.4.3",
     "base64-js": "^1.5.1",
     "tweetnacl": "^1.0.3",
-    "@bytetrue/byspace-relay": "0.2.0-beta.4",
+    "@bytetrue/byspace-relay": "0.2.0",
     "@agentclientprotocol/sdk": "^0.17.1",
     "@anthropic-ai/claude-agent-sdk": "^0.3.195",
     "@anthropic-ai/sdk": "^0.104.2",

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/_expo/static/js/web/index-38ca1829d34e8fa57f6076abc4391d37.js.br DELETED Viewed

Binary file

package/node_modules/@bytetrue/byspace-server/dist/server/web-ui/_expo/static/js/web/index-38ca1829d34e8fa57f6076abc4391d37.js.gz DELETED Viewed

Binary file