openmeld 0.3.75 → 0.3.77

package/package.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.75",
-  "openMeldReleaseDate": "2026-08-19",
+  "version": "0.3.77",
+  "openMeldReleaseDate": "2026-08-20",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",
   "type": "module",

package/skills/openmeld-cli/SKILL.md

@@ -449,6 +449,21 @@ openmeld agents repair --agent <agent-id> --view agent
 openmeld agents show <agent-id> --view agent
 ```
 
+Inspect every Computer connected to the current user's account, then read the
+current Computer's owner-only diagnostics:
+
+```bash
+openmeld computer list --view agent
+openmeld computer current --view agent
+```
+
+`computer list` returns the user's full Computer inventory and Local Agent
+snapshots. `computer current` adds current reply diagnostics, OpenMeld Tools
+versions and update state, and a File Access summary. The File Access summary
+contains the mode and selected-folder count, never local folder paths. These
+current-Computer diagnostics help explain whether a Local Agent is usable, but
+they do not replace an Agent Profile's authoritative readiness result.
+
 What setup means:
 
 - It makes this computer available to run local agents.
@@ -598,6 +613,37 @@ openmeld org directory --view agent
 openmeld org directory --json
 ```
 
+Use the directory before answering questions such as:
+
+- who belongs to the Organization and whether they are an owner, admin, or
+  member
+- which Human Profile represents a person
+- which Agent Profiles a member owns and whether one is currently ready for
+  work
+- when OpenMeld last accepted real Human activity from a member
+
+The response contains active members, Organization roles, user identity,
+Human Profiles, Agent Profiles, and an optional `lastActiveAt`. Agent Profiles
+are returned as Organization-level records; match an Agent Profile's
+`ownerUserId` to the member's `userId` instead of guessing from names.
+
+Treat a missing `lastActiveAt` literally: OpenMeld has no authoritative Human
+activity timestamp for that member. Never substitute a Computer heartbeat,
+login/session refresh, or Agent Activity timestamp.
+
+The directory is intentionally not a dump of every People drawer field. It
+does not expose Connected Channel management, private Computer paths or file
+access, Profile Report drafts or bodies, credentials, or private local-agent
+state. Use the Center Agent when approved Organization documents, Profile
+Report context, or another Organization-owned capability is needed. Use
+team-safe Computer reads only after resolving the exact member from the
+directory.
+
+For example, to find an admin who owns a ready Agent Profile, read the
+directory, filter members by `role`, then join Agent Profiles by `ownerUserId`
+and inspect their returned readiness. Do not infer role, ownership, or
+readiness from display names.
+
 Read or manage the Organization invite link:
 
 ```bash

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

@@ -139,6 +139,17 @@ openmeld org directory --view agent
 openmeld org directory --json
 ```
 
+The directory returns active members, roles, user identity, Human Profiles,
+Organization-level Agent Profiles, and optional authoritative Human
+`lastActiveAt` timestamps. Match Agent Profiles to members with `ownerUserId`.
+A missing `lastActiveAt` means that OpenMeld has no authoritative Human
+activity timestamp; do not replace it with Computer, session, or Agent
+Activity time.
+
+This command does not expose Connected Channel management, private Computer
+paths or file access, Profile Report drafts or bodies, credentials, or private
+local-agent state.
+
 ### `openmeld org invite-link`
 
 Read, create or reset, and revoke the active Organization invite link. OpenMeld