@wipcomputer/wip-ldm-os 0.4.85-alpha.3 → 0.4.85-alpha.30

package/README.md

@@ -22,7 +22,19 @@ Open your AI and paste this:
 ```
 Read https://wip.computer/install/wip-ldm-os.txt
 
-Check if LDM OS is already installed. If it is, run ldm install --dry-run and show me what I have and what's new.
+Use the install document and live local checks as the source of truth.
+Do not search memory or prior notes for this install. Do not pre-load context from `MEMORY.md`, `crystal_search`, local skill dev guides, or other local memory before fetching the install document.
+Do not run GitHub commands during this install flow. Do not run or request approval for `gh release`, `gh api`, or `gh search`. If release notes are not available from local or npm metadata, say that and do not fetch them from GitHub.
+
+Check if LDM OS is installed (`which ldm && ldm --version`). Branch.
+
+If installed: run `ldm status`, check available npm tracks from the install document, and show me the version table, what's new for each component, and which stable/current, beta, and alpha versions are available. Then ask:
+- Do you have questions?
+- Want to see a dry run?
+
+If yes to dry run, use the selected track's dry-run path from the install document.
+
+If I say install, use the selected track's install path from the install document, then run `ldm doctor`.
 
 If not, walk me through setup and explain:
 
@@ -35,7 +47,13 @@ Then ask:
 - Do you have questions?
 - Want to see a dry run?
 
-If I say yes: Install the CLI first (npm install -g @wipcomputer/wip-ldm-os) and then run ldm install --dry-run.
+If yes to dry run, install the CLI first using the selected track's bootstrap command from the install document.
+
+Then run:
+`ldm init --dry-run`
+
+If I say install, run:
+`ldm init`
 
 Show me exactly what will change. Don't install anything until I say "install".
 ```
@@ -105,6 +123,8 @@ The OS connects your AIs. Add-ons are what they actually use. Each one is a full
 ## More Info
 
 - [Architecture, principles, and technical details](TECHNICAL.md)
+- [Hosted MCP and relay source](src/hosted-mcp/README.md)
+- [Hosted relay self-host guide](src/hosted-mcp/docs/self-host.md)
 
 ## License
 

package/SKILL.md

@@ -27,6 +27,102 @@ metadata:
 
 # LDM OS
 
+## Source of truth
+
+Memory policy for install flows: do not consult `MEMORY.md`, do not run `crystal_search`, and do not search prior notes when this skill is invoked, including in any parallel or batched exploration step. The only context sources for this install flow are `https://wip.computer/install/wip-ldm-os.txt` and the live local commands that document prescribes. Read that document and run those commands. Do not pre-load other context.
+
+Use this install document and live local checks as the source of truth. Do not search memory or prior notes for this install.
+
+Do not run GitHub commands during the install-state flow. Do not run or request approval for `gh release list`, `gh release view`, `gh api repos/*`, `gh search`, or any other GitHub query unless the user explicitly asks for release notes. Install-state answers should come from local commands, `ldm status`, and npm package metadata.
+
+## Tracks
+
+LDM OS ships on three npm dist-tags. Each tag is just a name pointing at a specific version. Show the user the installed version and the available tracks in plain English. Do not paste raw JSON.
+
+- **stable** (`ldm install`) ... npm `@latest`. Use this only when `@latest` resolves to a non-prerelease version. Default for production releases.
+- **beta** (`ldm install --beta`) ... npm `@beta`. Prerelease track. Stabilization candidates.
+- **alpha** (`ldm install --alpha`) ... npm `@alpha`. Canary track. Earliest access; expect breakage.
+
+### Pick the right track
+
+Run this to get the dist-tags. Read the output and translate it into track names and versions.
+
+```bash
+npm view @wipcomputer/wip-ldm-os dist-tags --json
+```
+
+The npm `latest` tag is the stable/current track for user language. It is not guaranteed to be the newest prerelease. If `latest` points at a prerelease, explain that a stable release is not available yet.
+
+User language maps to tracks like this:
+
+- `stable`, `current`, or `latest` means `ldm install`
+- `beta` or `latest beta` means `ldm install --beta`
+- `alpha` or `latest alpha` means `ldm install --alpha`
+
+Dry-run commands use the same selected track:
+
+- stable/current/latest: `ldm install --dry-run`
+- beta/latest beta: `ldm install --beta --dry-run`
+- alpha/latest alpha: `ldm install --alpha --dry-run`
+
+Install commands use the same selected track:
+
+- stable/current/latest: `ldm install`
+- beta/latest beta: `ldm install --beta`
+- alpha/latest alpha: `ldm install --alpha`
+
+First-time CLI bootstrap commands use the same selected track:
+
+- stable/current/latest: `npm install -g @wipcomputer/wip-ldm-os`
+- beta/latest beta: `npm install -g @wipcomputer/wip-ldm-os@beta`
+- alpha/latest alpha: `npm install -g @wipcomputer/wip-ldm-os@alpha`
+
+The `ldm install --<track>` command self-updates the LDM CLI to the matching npm dist-tag before running the install. **Do not run `npm install -g @wipcomputer/wip-ldm-os@latest` ahead of an alpha or beta install:** `@latest` resolves to the stable dist-tag and will downgrade an alpha-pinned CLI to stable.
+
+If the user already named a track, do not force a generic chooser. Show the exact package, available version, track, and command you will run. Then wait for dry-run or install consent as appropriate.
+
+If the user has not named a track, show what is installed and what is available, then ask which track they want to dry run or install.
+
+Never pin a specific prerelease version in an install command, such as `@wipcomputer/wip-ldm-os@0.4.85-alpha.29`. Use the moving track flags.
+
+### How to phrase the track to the user
+
+The README prompt should stay short. This install document owns the detailed track rules.
+
+When the user asks for install state, say this first:
+
+> You have `<LOCAL>` installed. Available: stable/current `<NPM_LATEST_OR_NONE>`, beta `<NPM_BETA_OR_NONE>`, alpha `<NPM_ALPHA_OR_NONE>`.
+
+If no local install exists, say:
+
+> LDM OS is not installed. Available: stable/current `<NPM_LATEST_OR_NONE>`, beta `<NPM_BETA_OR_NONE>`, alpha `<NPM_ALPHA_OR_NONE>`.
+
+Then continue with the setup explanation and ask whether the user has questions or wants a dry run.
+
+If the user named a track, answer directly:
+
+> You asked for `<TRACK>`. The available `<TRACK>` version is `<VERSION>`. The dry-run command is `<COMMAND>`.
+
+If the user says `stable`, `current`, or `latest` and npm `@latest` is a prerelease, say:
+
+> Stable is not available yet. The stable/current track currently points at prerelease `<NPM_LATEST>`. Available prerelease tracks are beta `<NPM_BETA_OR_NONE>` and alpha `<NPM_ALPHA_OR_NONE>`. Which track do you want?
+
+Do not treat public install docs as beta-only or alpha-only. Alpha, beta, and stable are all public npm tracks. Disclose risk and let the user choose.
+
+Track risk language:
+
+- stable/current/latest: normal public path, once it is a real non-prerelease release.
+- beta: public prerelease path.
+- alpha: canary path, likely rougher, but installable if the user asks for it.
+
+#### Anti-patterns ... do NOT print any of these.
+
+- Do not print raw `npm view ... dist-tags` JSON.
+- Do not use `latest` as a synonym for newest prerelease.
+- Do not give a hardcoded single-track recommendation when the user asked what is available.
+- Do not force a generic chooser after the user already said `latest alpha`, `alpha`, `latest beta`, `beta`, `stable`, `current`, or `latest`.
+- Do not run `gh release list` during install-state detection.
+
 ## Step 1: Check if installed
 
 ```bash
@@ -62,12 +158,16 @@ Always a table. Every component with an update gets its own row.
 
 **Do NOT skip this step.**
 
-```bash
-gh release list --repo wipcomputer/<repo-name> --limit 5 --json tagName,name --jq '.[]'
-gh release view <tag> --repo wipcomputer/<repo-name> --json body --jq .body
-```
+Use the output of `ldm status`, installed package metadata, and npm metadata. Do not use GitHub commands here.
+
+If npm metadata for a package does not include release notes:
+- Show the version difference, for example `wip-repos v1.9.69 -> v1.9.70`.
+- Say "release notes not available from local metadata."
+- Do not fetch from GitHub. Do not run `gh release`, `gh api`, `gh search`, or any other GitHub query.
+- Do not infer release-note content from package descriptions, commit messages, or repo READMEs.
+- If the user wants release-note details, wait for an explicit request in plain language. An approval dialog is not a user request.
 
-Translate release notes to user language. Every bullet answers "what changed for ME?"
+Translate available update information to user language. Every bullet answers "what changed for ME?" If the status output does not include enough detail for a component, say that clearly and do not invent release notes.
 
 Good: "Your AIs now explain what LDM OS actually does when you ask them to install it"
 Bad: "Restored rich product content to SKILL.md"
@@ -83,15 +183,23 @@ Show 2-3 bullets per component. Then:
 
 Do you have questions? Want to see a dry run?
 
-```bash
-ldm install --dry-run
-```
+Use the selected track from **Pick the right track**:
+
+- stable/current/latest: `ldm install --dry-run`
+- beta/latest beta: `ldm install --beta --dry-run`
+- alpha/latest alpha: `ldm install --alpha --dry-run`
 
 Don't install until the user says "install".
 
+Use the selected track from **Pick the right track**:
+
+- stable/current/latest: `ldm install`
+- beta/latest beta: `ldm install --beta`
+- alpha/latest alpha: `ldm install --alpha`
+
+Then verify with:
+
 ```bash
-npm install -g @wipcomputer/wip-ldm-os@latest
-ldm install
 ldm doctor
 ```
 
@@ -117,10 +225,11 @@ Read [references/SKILLS-CATALOG.md](references/SKILLS-CATALOG.md). Present the i
 
 Do you have questions? Want to see a dry run?
 
-Install the CLI first:
-```bash
-npm install -g @wipcomputer/wip-ldm-os
-```
+Install the CLI first using the selected track from **Pick the right track**:
+
+- stable/current/latest: `npm install -g @wipcomputer/wip-ldm-os`
+- beta/latest beta: `npm install -g @wipcomputer/wip-ldm-os@beta`
+- alpha/latest alpha: `npm install -g @wipcomputer/wip-ldm-os@alpha`
 
 If npm/node is not installed: Node.js 18+ from https://nodejs.org first.
 
@@ -161,6 +270,19 @@ ldm doctor --fix
 - **Dry-run first.** Always. Only install when the user says "install".
 - **Never touch sacred data.** crystal.db, agent data, secrets, state files are never overwritten.
 
+## Track caveats
+
+Tell the user, scaled to the track they're on:
+
+- **alpha**: canary path, earliest access, breakage possible. Use only when the user explicitly opts in.
+- **beta**: stabilization candidate. Same shape as alpha but feature-frozen for the cut.
+- **stable**: production. The user should be on this unless they've asked otherwise.
+
+Roadmap caveats that apply to every track right now:
+
+- Registry source-type migration is mid-flight. After Phase 2 ships, `ldm status` will categorize every extension by source type (`npm` / `git` / `bundled` / `private`). Until then, some entries appear under "Untracked extensions" with a `ldm doctor --reclassify-sources` remediation pointer.
+- LDM OS is the canonical pattern source for child packages (Codex Remote Control, future tools). Install-prompt structure changes here propagate downstream; child packages should not lead the parent.
+
 ## Reference files
 
 For detailed information, read these on demand (not on every activation):