openmeld 0.3.156 → 0.3.157

package/package.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.156",
-  "openMeldReleaseDate": "2026-09-04",
+  "version": "0.3.157",
+  "openMeldReleaseDate": "2026-09-05",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",
   "type": "module",

package/skills/openmeld-cli/SKILL.md

@@ -43,6 +43,7 @@ are missing.
 Copied OpenMeld Space URLs work directly on common reads. Keep URLs quoted so shell-sensitive query characters stay literal:
 
 ```bash
+openmeld space link <space-id> --signal <signal-id> --thread-root-signal <signal-id> --view agent
 openmeld space access "<space-url-or-id>" --profile <profile-id> --view agent
 openmeld space board "<space-url-or-id>" --profile <profile-id> --json
 openmeld space members "<space-url-or-id>" --profile <profile-id> --json
@@ -51,6 +52,10 @@ openmeld space status "<space-url-or-id>" --profile <profile-id> --json
 openmeld space wake-progress "<space-url-or-id>" --profile <profile-id> --view agent
 ```
 
+`space link` is a local destination builder, not an access grant. Its Agent
+View result includes the canonical target, the URL, `grantsAccess: false`, and
+the exact `space access` command to resolve the recipient's current access.
+
 Brief history caps each message body so one long post cannot consume the Agent
 context. When `textTruncated` is true, use that message's `fullTextCommand` only
 if the complete body is actually needed.

package/skills/openmeld-cli/playbooks/space-reads.md

@@ -19,6 +19,16 @@ openmeld space status "<space-url-or-id>" --profile <profile-id> --json
 openmeld space wake-progress "<space-url-or-id>" --profile <profile-id> --view agent
 ```
 
+To create one of those destinations, use the local link builder:
+
+```bash
+openmeld space link <space-id> --signal <signal-id> --thread-root-signal <thread-root-signal-id> --view agent
+```
+
+The result explicitly reports `grantsAccess: false` and includes the matching
+`space access` continuation. Do not treat a generated link as permission or
+manually splice message selectors into another route.
+
 Do not manually extract the Space ID from a copied URL.
 
 Use `space access` before a content read when the caller may not be a member.

package/skills/openmeld-cli/references/commands.md

@@ -14,6 +14,20 @@ openmeld <command> <subcommand> --help
 
 ## Top-Level Commands
 
+### Create a Space or message link
+
+Build a tenant-neutral public entry link locally. This command does not sign
+in, contact Core, start OpenMeld Service, or grant access.
+
+```bash
+openmeld space link <space-id> --view agent
+openmeld space link <space-id> --signal <signal-id> --view agent
+openmeld space link <space-id> --signal <signal-id> --thread-root-signal <thread-root-signal-id> --view agent
+```
+
+Agent View returns the canonical target and an exact `space access`
+continuation. Use full signal UUIDs from Space history.
+
 ### Resolve Space access
 
 Use the Core-owned entry resolver before following a Space link when access is