openmeld 0.3.155 → 0.3.157

package/package.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.155",
-  "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

@@ -40,10 +40,11 @@ are missing.
 
 ## Common Space Reads
 
-Copied OpenMeld Space URLs work directly on the four frequent read commands.
-Keep a URL quoted so shell-sensitive query characters stay literal:
+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
 openmeld space history "<space-url-or-id>" --profile <profile-id> --kind text --brief --limit 20 --view agent
@@ -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

@@ -1,15 +1,17 @@
 # Space Reads Playbook
 
 Use this playbook for fast, read-only Space inspection with the public
-`openmeld` CLI. It covers `board`, `members`, `history`, `status`, and live Wake
-progress without changing membership, the selected Profile, or Space state.
+`openmeld` CLI. It covers entry resolution, `board`, `members`, `history`,
+`status`, and live Wake progress without changing membership, the selected
+Profile, or Space state.
 
 ## Start Here
 
-All four commands accept either a 64-character Space ID or a complete OpenMeld
+All commands accept either a 64-character Space ID or a complete OpenMeld
 Space URL. Quote URLs so shell-sensitive query characters stay literal:
 
 ```bash
+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
 openmeld space history "<space-url-or-id>" --profile <profile-id> --kind text --brief --limit 20 --view agent
@@ -17,8 +19,25 @@ 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.
+Its `resolution.view` answers whether content may be shown; its independent
+`resolution.participation` answers whether the Profile can participate. Follow
+the structured `viewAction` for sign-in, password, owner contact, or target
+continuation. Do not turn `contact_space_owner` into an invented join request:
+that product flow does not exist yet.
+
 ## Acting Profile
 
 For these reads, identity resolves in this order:
@@ -53,6 +72,8 @@ openmeld space status "<space-url-or-id>" --profile <profile-id> --json
   window without presence noise. Use anchored or raw history only when needed.
 - `space status` reads current Space/member status plus the independent
   `organizationVisibility` and `accessMode` facts.
+- `space access` reads the Core-owned entry decision for the target and current
+  identity. It does not read messages or change membership.
 - `space wake-progress` reads the current Wake lifecycle plus Space-owned public
   requester identity and display name, source-message preview, and thread
   context. Use
@@ -65,6 +86,7 @@ Adjacent Agent View commands intentionally retain their existing compatible
 presentations. Use the explicit machine form when one stable shape matters:
 
 - `board --json`: the shared Space Board response
+- `access --json`: the canonical shared Space entry resolution
 - `members --json`: the versioned `space.members` envelope
 - `status --json`: canonical Space status JSON
 - `wake-progress --view agent`: the validated live Wake progress envelope
@@ -119,9 +141,11 @@ data or a successful read.
 
 ## Performance And Freshness
 
-These commands must read current authorized projections. Never make them look
-fast by caching stale Space data, skipping sign-in or Profile authorization, or
-turning a timeout into success. The CLI may reuse the same already-remotely-
+These commands must read current authorized projections. `space access` is the
+intentional public preflight and may run without sign-in so Core can return the
+safe anonymous outcome; content reads still require their normal authorization.
+Never make reads look fast by caching stale Space data or turning a timeout into
+success. The CLI may reuse the same already-remotely-
 validated session within one command while still checking that the locally
 stored credential is unchanged.
 

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

@@ -14,6 +14,34 @@ 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
+not already known. This read does not join the Space or change local Profile
+selection.
+
+```bash
+openmeld space access "<space-url-or-id>" --profile <profile-id> --view agent
+openmeld space access "<space-url-or-id>" --password <space-password> --json
+```
+
+Copied links preserve `focusSignalId` / `signalId` and
+`focusThreadRootSignalId` / `threadRootSignalId` in the resolved target.
+
 ## Current Local Session To Space Teammate
 
 When the user asks you to add this Codex or Claude Code session to a Space, use