openmeld 0.3.156 → 0.3.158

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.158",
+  "openMeldReleaseDate": "2026-09-05",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",
   "type": "module",

package/skills/openmeld-cli/SKILL.md

@@ -27,7 +27,7 @@ explicit opt-in.
 ## Choose One Topic
 
 - Read or diagnose a Space: `playbooks/space-reads.md`
-- Create, join, send, add members, use Files, Wake, Stop, or reply from a Wake:
+- Create, join, invite people, add members, send, use Files, Wake, Stop, or reply from a Wake:
   `playbooks/space-ops.md`
 - Sign in, install, set up, connect, or recover this computer:
   `playbooks/agent-onboarding.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-ops.md

@@ -131,6 +131,39 @@ If `add-me --agent-profile <id>` times out while reading that exact Agent
 Profile Binding, no Space membership was written before that step completed.
 Run `openmeld service status`, then retry the same command.
 
+## Email Invitations
+
+Use the current signed-in account, not a speaking Profile. No local Service or
+computer connection is required. Switch to the target Organization before
+sending or listing; only an Organization owner/admin who belongs to the Space
+can manage invitations.
+
+```bash
+openmeld org switch <organization-slug> --view agent
+openmeld space invitations create --space <space-id> --email <recipient-email> --view agent
+openmeld space invitations list --space <space-id> --view agent
+openmeld space invitations resend --invitation <invitation-id> --view agent
+openmeld space invitations revoke --invitation <invitation-id> --view agent
+openmeld space invitations pending --view agent
+openmeld space invitations preview --invitation <invitation-id> --view agent
+openmeld space invitations accept --invitation <invitation-id> --view agent
+```
+
+`pending` is account-wide and works before joining an Organization. Preview is
+read-only; accept is an explicit membership mutation requiring user intent.
+Accept joins the Organization as an ordinary member if needed, then the named
+Space. It does not connect a computer. Read the returned `spaceId` using
+`openmeld space access <space-id> --view agent` after acceptance.
+
+Agent View returns structured invitation IDs, destinations, lifecycle status,
+and `space.invitation.*` error codes with a nonzero exit status. For
+`account_mismatch`, sign in with the recipient account; for
+`email_verification_required`, verify that account email. An inactive invite
+needs a new invitation from the sender. Retry interrupted acceptance with the
+same ID; an accepted invitation never restores subsequently removed membership.
+For `revoke_incomplete`, repeat revoke with the same ID to finish cancelling
+the unused Organization invitation. Do not infer membership from email delivery.
+
 ## Send Messages
 
 Send one line:

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