Object-level `permissions` is declared but never emitted

Repo: viewer
Labels: bug, protocol

Summary

PublishedObject.permissions is part of the documented contract and is declared in the plugin's
TypeScript types, but the viewer never writes a permissions key at the object level.

Evidence

indra/newview/llpublishedobjectmgr.cpp:

• Item-level permissions are emitted (~line 714–718):

  const LLPermissions& perms = item->getPermissions();
  perm_entry["next_owner"] = static_cast<S32>(perms.getMaskNextOwner());
  entry["permissions"]     = perm_entry;
  

• buildPublishedObjectLLSD (~728) and buildObjectListLLSD (~762) emit owner_id,
  can_save_back and others, but no permissions.

Impact

Clients cannot determine object-level permissions from object.publish or object.list, and
must infer them or fall back to per-item permissions.

Proposed fix

Emit permissions (owner, next_owner) at the object level in both builders.

Start in indra/newview/llpublishedobjectmgr.cpp at buildPublishedObjectLLSD and buildObjectListLLSD, after reviewing the existing item-level permissions emission around lines 714–718. Trace how object data is assembled and confirm the documented PublishedObject shape. Done means both builders emit object-level permissions with owner and next_owner values for object.publish and object.list.