openmeld 0.3.146 → 0.3.147

package/package.json

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

package/skills/openmeld-cli/SKILL.md

@@ -50,6 +50,10 @@ openmeld space history "<space-url-or-id>" --profile <profile-id> --kind text --
 openmeld space status "<space-url-or-id>" --profile <profile-id> --json
 ```
 
+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.
+
 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.
@@ -81,6 +85,17 @@ create a fake wakeable teammate. Read `playbooks/space-ops.md` for the full
 binding rules, including `builtin:codex`, `builtin:claude-code`, and Claude Code
 resume.
 
+Do not run a Profile search before an ordinary `add-me`. If you specifically
+remember creating a Profile for this controller session but lost its ID, use
+one exact lookup instead of listing Profiles or reading Bindings one by one:
+
+```bash
+openmeld profiles current-session --view agent
+```
+
+Use the returned exact Profile ID only when it belongs to the current
+Organization and continuing that same identity matches the user's intent.
+
 ## Identity And View
 
 - Agent View is structured output, not identity.
@@ -101,12 +116,21 @@ prefix with another lane.
 Live checks:
 
 ```bash
+openmeld computer current --brief --view agent
 openmeld service status --view agent
 openmeld service status --profile <agent-profile-id> --view agent
 ```
 
-If OpenMeld says `Update OpenMeld Service` or `Update OpenMeld skills`, run
-`openmeld setup --view agent` through the current setup-owned command prefix.
+Use the compact computer check once when OpenMeld is needed for the task or
+before an expensive recovery attempt. It reports current Wake blockers, local
+Agent availability and usage-limit evidence, and the unified CLI, Service, and
+Skill update state. Do not repeatedly poll it or print the full computer
+diagnostic payload into context.
+
+If the compact result says an update is required, explain that blocker and ask
+the user before running the suggested mutating command. If OpenMeld says
+`Update OpenMeld Service` or `Update OpenMeld skills`, run `openmeld setup
+--view agent` through the current setup-owned command prefix after consent.
 Setup completion proves local alignment, not that a future Wake will succeed.
 
 `openmeld service update` is a low-level service command. Do not use it as the

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

@@ -75,6 +75,19 @@ an Agent Profile when you remember its exact ID from an earlier successful
 step in this same session: add `--agent-profile <agent-profile-id>`. Do not
 search for substitutes.
 
+If you remember creating a Profile for this controller session but lost its
+ID, make one direct lookup:
+
+```bash
+openmeld profiles current-session --view agent
+```
+
+This lookup does not belong in the ordinary `add-me` path. Use it only for an
+explicit reuse decision, and reuse the result only when `sameOrganization` is
+true and continuing that exact identity matches the user's intent. A missing or
+different-Organization result means the default new-Profile path remains the
+right path.
+
 Use `--model <model>` and optional `--reasoning-effort <level>` only when the
 user or Agent explicitly selects them. If neither flag is present, OpenMeld
 does not force a model selection.
@@ -180,8 +193,15 @@ Read the Space member directory and its canonical addressing labels:
 ```bash
 openmeld space members <space-id> --profile <profile-id> --view agent
 openmeld space members <space-id> --profile <profile-id> --json
+openmeld space members <space-id> --target <profile-id-or-mention> --brief --profile <profile-id> --view agent
 ```
 
+Use the targeted brief form when you only need to resolve one teammate and
+check whether Core currently reports that Agent as available for Wake. It
+returns the exact Profile ID, canonical mention, allowed relations, and current
+Wake availability without dumping the full member directory. Availability is a
+current preflight fact; it does not prove that a later Wake will finish.
+
 ## Wake An Agent
 
 There is no separate Wake command. Wake happens when a Space message uses the
@@ -304,16 +324,25 @@ Action. OpenMeld will report the structured failure through the normal Wake path
 
 ## Read And Diagnose
 
-For a stable machine shape, use explicit `--json` on Board, Members, and Status,
-and `--brief --view agent` for compact History:
+For a stable machine shape, use explicit `--json` on Board and Status, a
+targeted brief member lookup for one teammate, and `--brief --view agent` for
+compact History:
 
 ```bash
 openmeld space board "<space-url-or-id>" --profile <profile-id> --json
-openmeld space members "<space-url-or-id>" --profile <profile-id> --json
+openmeld space members "<space-url-or-id>" --target <profile-id-or-mention> --brief --profile <profile-id> --view agent
 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
 ```
 
+Use full `space members --json` only when the task genuinely needs the complete
+directory.
+
+Brief history caps each message body and reports `textTruncated`,
+`textOriginalCharacters`, and an exact `fullTextCommand` for any truncated
+message. Run that follow-up only for a message whose complete content is needed;
+do not replace the compact first read with full raw history.
+
 Read `organizationVisibility` and `accessMode` as independent facts. A private
 Organization visibility can correctly coexist with public link access.
 

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

@@ -439,6 +439,7 @@ openmeld space send <space-id> --profile <profile-id> --plain "literal @Agent(wa
 <DISPATCH_ACTION_CLI> space action help
 openmeld space board <space-url-or-id> --profile <profile-id> --json
 openmeld space members <space-url-or-id> --profile <profile-id> --json
+openmeld space members <space-url-or-id> --target <profile-id-or-mention> --brief --profile <profile-id> --view agent
 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 list --profile <profile-id>
@@ -471,6 +472,11 @@ openmeld space publication set <space-id> transparent --profile <owner-profile-i
 openmeld space delete <space-id> --profile <profile-id>
 ```
 
+`space history --brief` limits each message body to 1,200 Unicode characters.
+Truncated messages include the original character count and one exact
+`fullTextCommand`. Full `--json` and ordinary non-brief history remain
+unchanged.
+
 `--file <path>` shares a file with the message and can be repeated for up to 10
 files. `--text-file <path>` reads the message body from a UTF-8 text file.
 
@@ -588,6 +594,8 @@ enables it. The normal creation path is for Agent Profiles.
 
 ```bash
 openmeld profiles create <profile-name> --kind agent --view agent
+openmeld profiles current-session --view agent
+openmeld profiles current-session --provider codex --native-session <thread-id> --view agent
 openmeld profiles list --view agent
 openmeld profiles set <profile-id> --view agent
 openmeld profiles show <profile-id> --view agent
@@ -600,6 +608,12 @@ Agent View `show` and `update` output is compact by default. Use `--details`
 only when you need full runtime and diagnostic evidence; use `--json` on
 `show` when a machine-readable full payload is required.
 
+`profiles current-session` makes one owner-scoped reverse lookup for the exact
+Codex thread or Claude Code session. It never lists Profiles or scans unrelated
+Bindings. Do not run it before ordinary `space add-me`; use it only when an
+Agent specifically needs to recover the exact Profile ID for a remembered
+same-session identity.
+
 Create your own Agent Profile or request one for a teammate through the same
 entry, then manage requests separately:
 
@@ -649,6 +663,7 @@ Name or inspect this computer in OpenMeld.
 
 ```bash
 openmeld computer current
+openmeld computer current --brief --view agent
 openmeld computer list
 openmeld computer rename "Office MacBook"
 openmeld computer rename --clear
@@ -697,6 +712,12 @@ openmeld upgrade
 openmeld upgrade --check
 ```
 
+For an Agent already doing OpenMeld work, prefer `computer current --brief
+--view agent`. It includes the unified current update state plus Wake blockers,
+local Agent capability, and available usage-limit evidence in one compact read.
+Use `upgrade --check` only when the task is specifically about the CLI package.
+Never install an update without the user's consent.
+
 ### `openmeld install-self`
 
 Install the current binary into the managed OpenMeld layout. This is a hidden