oysterun 1.6.0-beta.26 → 1.6.0-beta.28

package/README.md

@@ -176,7 +176,7 @@ Oysterun/
   dev/client/          Host-served web client source
   docs/                  Product, design, auth, mock, and TODO docs
   local notes            Gitignored working notes, reports, and ad hoc verification files
-  temp/                  Local export output from tool_scripts/export_key_files.sh
+  temp/                  Local export output from OysterunTeam/tool_scripts/export_key_files.sh
   test-results/          Playwright output
   tool_scripts/          One-off local utilities
   investigation-repos/   Reference repos used for research only
@@ -185,7 +185,7 @@ Oysterun/
 Folders you can usually ignore when reading product code:
 
 - gitignored operational notes: plans, reports, and ad hoc verification files
-- `temp/`: export bundles created by `tool_scripts/export_key_files.sh`
+- `temp/`: export bundles created by `OysterunTeam/tool_scripts/export_key_files.sh`
 - `test-results/`: Playwright run output such as `.last-run.json`, traces, screenshots, and other browser-test artifacts
 - `investigation-repos/`: external reference code, not the Oysterun runtime itself
 
@@ -262,8 +262,7 @@ Default local URLs when you run `npm start` or `npm run dev` directly with the c
 Port notes:
 
 - production default is `8802` in `~/.oysterun/config.json`
-- staging uses `9902`
-- disposable test slots use `3022`, `3302`, `4022`, and `4402`
+- task and development Hosts use a custom stack with an explicit `--port`
 - phone app verification can use any running Host port; point the app at the actual user-approved port for that run
 - backend URL default is `http://localhost:8000`
 - Host config is stored in `~/.oysterun/config.json`
@@ -277,8 +276,7 @@ For local repo development, you can launch the backend and Host together with th
 
 ```bash
 cd <repo-root>
-./tool_scripts/dev_up.sh
-./tool_scripts/dev_up.sh --stack staging
+./tool_scripts/dev_up.sh --stack <name> --port <host_port> --backend_port <backend_port>
 ```
 
 What it does:
@@ -286,7 +284,7 @@ What it does:
 - rebuilds `dev/client/web/index.html`
 - starts the selected development backend in reload mode
 - starts the selected Host in watch mode
-- uses `staging` by default
+- requires a named custom stack (there is no default)
 - syncs the stack-owned Host port before start
 - stops both when you press `Ctrl-C`
 
@@ -322,9 +320,9 @@ Convenience wrappers are also available at:
 Stack-specific usage:
 
 ```bash
-~/Projects/start_oysterun.sh --stack staging
-~/Projects/restart_oysterun.sh --stack staging
-~/Projects/stop_oysterun.sh --stack staging
+~/Projects/start_oysterun.sh --stack <name> --port <port>
+~/Projects/restart_oysterun.sh --stack <name>
+~/Projects/stop_oysterun.sh --stack <name>
 ```
 
 What they do:
@@ -335,7 +333,7 @@ What they do:
 - do not initialize backend runtime state
 - use `production` by default
 - keep production Host config under `~/.oysterun/config.json`
-- keep staging/test Host config under `~/.oysterun-stacks/<stack>/host/config.json`
+- keep custom stack Host config under `~/.oysterun-stacks/<stack>/host/config.json`
 - write PID files under `~/.oysterun/run/` or `~/.oysterun-stacks/<stack>/run/`
 - write logs under `~/.oysterun/logs/` or `~/.oysterun-stacks/<stack>/logs/`
 
@@ -343,15 +341,11 @@ Important:
 
 - this is more convenient than `tmux` for manual start/stop/restart
 - these scripts use temporary `launchctl submit` jobs unless you explicitly install the persistent LaunchAgents
-- for persistent login-time auto-start and crash auto-restart on `8802` and `9902`, use `./tool_scripts/install_oysterun_launch_agents.sh`
+- for persistent login-time auto-start and crash auto-restart on `8802`, use `./tool_scripts/install_oysterun_launch_agents.sh` (add `--stack <name>` for a custom stack)
 - these scripts use stable non-watch commands; use `./tool_scripts/dev_up.sh` when you want backend + Host live auto-reload during active repo development
 - `./tool_scripts/dev_up.sh` is the only startup path that initializes backend runtime state
-- the supported preset stacks are `production`, `staging`, `test1`, `test2`, `test3`, and `test4`
-- `production` uses Host `8802`
-- `staging` uses Host `9902`
-- `test1..test4` use Host `3022`, `3302`, `4022`, and `4402`
-- `./tool_scripts/dev_up.sh` is for staging-oriented repo development and uses backend `9000`
-- set `OYSTERUN_STAGING_LAN_HOST=<your_lan_ip>` if the staging stack should advertise a different LAN IP than `192.168.0.188`
+- `production` is the only preset stack and uses Host `8802`; every other stack is a custom stack with its own `--port`
+- `./tool_scripts/dev_up.sh` needs `--backend_port` for its development backend
 
 ### 3. Use the web client
 
@@ -361,11 +355,7 @@ For the default production Host, open:
 http://localhost:8802/app
 ```
 
-For staging, open:
-
-```text
-http://localhost:9902/app
-```
+For a custom stack, open `http://localhost:<port>/app`.
 
 The web client is served by the Host service. There is no separate frontend dev server to start.
 
@@ -451,10 +441,10 @@ cd <repo-root>
 ./tool_scripts/restart_oysterun.sh
 ```
 
-For staging:
+For a custom stack:
 
 ```bash
-~/Projects/restart_oysterun.sh --stack staging
+~/Projects/restart_oysterun.sh --stack <name>
 ```
 
 ### Frontend restart
@@ -600,7 +590,7 @@ Browser and ad hoc verification artifacts in this repo have usually been kept as
 
 `temp/` is mainly used by:
 
-- `tool_scripts/export_key_files.sh`
+- `OysterunTeam/tool_scripts/export_key_files.sh`
 
 That script creates export folders and zip files like:
 

package/bin/oysterun.mjs

@@ -137,7 +137,7 @@ function parseUninstallArgs(args = []) {
     } else if (arg === "--stack") {
       const value = args[index + 1];
       if (!value) {
-        throw new Error("--stack requires production, staging, or all");
+        throw new Error("--stack requires production or all");
       }
       options.stack = value;
       index += 1;
@@ -150,9 +150,9 @@ function parseUninstallArgs(args = []) {
 
   if (
     options.stack !== null &&
-    !["production", "staging", "all"].includes(options.stack)
+    !["production", "all"].includes(options.stack)
   ) {
-    throw new Error("--stack must be production, staging, or all");
+    throw new Error("--stack must be production or all");
   }
   if (options.confirm !== null && options.confirm !== "DELETE") {
     throw new Error("config deletion requires --confirm DELETE exactly");
@@ -241,7 +241,7 @@ Usage:
   oysterun service:lifecycle-status
   oysterun service:status
   oysterun service:logs [--follow]
-  oysterun service:uninstall [--stack production|staging|all]
+  oysterun service:uninstall [--stack production|all]
   oysterun <module> <action> [options]
 
 Product modules:
@@ -257,7 +257,7 @@ Chat transcript reads:
   History read authority does not authorize send, loop, profile or lifecycle.
 
 Session tags:
-  sessions start|resume|branch-resume [--tags 'first,second' | --clear-tags]
+  sessions start|resume [--tags 'first,second' | --clear-tags]
   sessions profile update [--tags 'first,second' | --clear-tags]
   --clear-tags creates or saves an untagged Session; empty --tags is invalid.
   Omitted start tags inside a Session copy the authenticated parent's name.
@@ -278,7 +278,7 @@ function printUninstallHelp() {
 
 Usage:
   oysterun uninstall [--confirm DELETE] [--keep-config] [--dry-run]
-  oysterun uninstall --stack production|staging|all [options]
+  oysterun uninstall --stack production|all [options]
 
 Behavior:
   - Stops/removes managed Oysterun service state where available.
@@ -289,7 +289,7 @@ Behavior:
   - Without DELETE (including --keep-config), preserves config and CLI package.
   - --keep-config and --confirm DELETE cannot be combined.
   - --dry-run prints the selected services/config and exact CLI/npm/prefix plan.
-  - --stack all removes production and staging services, but only the selected
+  - --stack all removes the production service, but only the selected
     config directory and the launching CLI package.
 `);
 }

package/dev/client/connectivity/managed-host-browser.mjs

@@ -57,7 +57,7 @@ const TRANSPORT_ENDPOINT_CLASSES = Object.freeze([
   "auth",
   "other",
 ]);
-const REPORTED_DIAGNOSTIC_EVENTS = new Set([
+export const REPORTED_DIAGNOSTIC_EVENTS = new Set([
   "managed_webrtc_connect_failed",
   "managed_webrtc_connected",
   "managed_webrtc_fallback_bootstrap",