openmeld 0.3.150 → 0.3.151

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.150",
+  "version": "0.3.151",
   "openMeldReleaseDate": "2026-09-03",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",

package/skills/openmeld-cli/SKILL.md

@@ -48,12 +48,19 @@ 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
 openmeld space status "<space-url-or-id>" --profile <profile-id> --json
+openmeld space wake-progress "<space-url-or-id>" --profile <profile-id> --view agent
 ```
 
 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.
 
+Wake progress is the live execution view. Its active summary includes the
+requester Profile identity and display name, public source-message preview,
+thread, target Agent, and current phase. Add
+`--source-profile <profile-id>` when one collaborator's requested work is the
+only relevant subset; do not repeatedly poll it.
+
 For these reads, explicit `--profile` wins over a URL `profileId`. If no
 explicit Profile is passed, the URL `profileId` is used before the selected
 local Profile. Do not ask an Agent to extract the Space ID manually.

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

@@ -1,8 +1,8 @@
 # Space Reads Playbook
 
 Use this playbook for fast, read-only Space inspection with the public
-`openmeld` CLI. It covers `board`, `members`, `history`, and `status` without
-changing membership, the selected Profile, or Space state.
+`openmeld` CLI. It covers `board`, `members`, `history`, `status`, and live Wake
+progress without changing membership, the selected Profile, or Space state.
 
 ## Start Here
 
@@ -14,6 +14,7 @@ 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
 openmeld space status "<space-url-or-id>" --profile <profile-id> --json
+openmeld space wake-progress "<space-url-or-id>" --profile <profile-id> --view agent
 ```
 
 Do not manually extract the Space ID from a copied URL.
@@ -52,6 +53,11 @@ 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 wake-progress` reads the current Wake lifecycle plus Space-owned public
+  requester identity and display name, source-message preview, and thread
+  context. Use
+  `--source-profile <profile-id>` to narrow the active summary to work requested
+  by one Human or Agent Profile. It does not expose private agent context.
 
 ## Output Contract
 
@@ -61,6 +67,7 @@ presentations. Use the explicit machine form when one stable shape matters:
 - `board --json`: the shared Space Board response
 - `members --json`: the versioned `space.members` envelope
 - `status --json`: canonical Space status JSON
+- `wake-progress --view agent`: the validated live Wake progress envelope
 - `history --brief --view agent`: one compact message-only history result
 - `history --json`: raw message envelopes as ndjson
 
@@ -121,3 +128,7 @@ stored credential is unchanged.
 If a read is unexpectedly slow, record the exact command, wall time, output
 mode, and non-sensitive request/error evidence. Retry only the same read; do not
 write Space state as a diagnostic shortcut.
+
+Wake progress is a snapshot for a concrete coordination decision. Do not poll
+it continuously or infer a terminal outcome when Core still reports active
+work.

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

@@ -462,6 +462,7 @@ openmeld space files history <space-id> <file-id> --profile <profile-id> --view
 openmeld space files restore <space-id> <entry-id> --profile <profile-id> --view agent
 openmeld space files restore-version <space-id> <file-id> <revision> --base-revision <n> --profile <profile-id> --view agent
 openmeld space wake-progress <space-id> --profile <profile-id> --view agent
+openmeld space wake-progress <space-id> --source-profile <requester-profile-id> --profile <profile-id> --view agent
 openmeld space wake-progress <space-id> --client-message <client-message-id> --target-profile <agent-profile-id> --profile <profile-id> --view agent
 openmeld space wake-stop <space-id> --client-message <client-message-id> --target-profile <agent-profile-id> --profile <profile-id> --view agent
 openmeld space wake-stop <space-id> --source-signal <source-signal-id> --target-profile <agent-profile-id> --reason <text> --profile <profile-id> --view agent
@@ -522,10 +523,16 @@ agents.
 
 Read live Wake progress. With no selector, the command returns the active Wake
 summary for the Space. Use `--client-message` to poll one authored message and
-optionally `--target-profile` to narrow it to one Agent Profile.
+optionally `--target-profile` to narrow it to one Agent Profile. For the active
+summary, use `--source-profile` to keep only work requested by one Human or
+Agent Profile. Agent View includes the requester Profile ID, kind, display name,
+sanitized public source-message preview, nullable thread ID, target Agent, and
+current phase.
+It never includes private agent context.
 
 ```bash
 openmeld space wake-progress <space-id> --profile <profile-id> --view agent
+openmeld space wake-progress <space-id> --source-profile <requester-profile-id> --profile <profile-id> --view agent
 openmeld space wake-progress <space-id> --client-message <client-message-id> --target-profile <agent-profile-id> --profile <profile-id> --view agent
 ```