feat: stabilize OpenSim interactions and landmarks

docs/grid-agent-acceptance.md

@@ -111,9 +111,9 @@ hash. Do not record vendor presets or identifiers. Exercise, in order:
 5. As a privileged user, build only on controlled land, record transaction and
    object recovery IDs locally, verify no currency operation exists, and delete
    every created prim through the ownership-checked cleanup path.
-6. Accept a controlled landmark offer, use a short bounded folder schedule,
-   teleport, then disable the schedule. Capture the synthetic scene and ask
-   one visual question. Record the endpoint
+6. Create and catalog a current-location landmark, accept a controlled landmark
+   offer, use a short bounded folder schedule, teleport, then disable the
+   schedule. Capture the synthetic scene and ask one visual question. Record the endpoint
    capability fallback if image input is rejected.
 7. Gracefully stop. Confirm no pending approvals, scheduled jobs, inventory
    offers, owned test prims, tasks, sockets, or sessions. List any unavoidable

docs/grid-agent-landmarks.md

@@ -1,9 +1,11 @@
 # Landmark intake, teleport, and roaming
 
 Landmark authority is private. Public chat and non-allow-listed IM can neither
-accept offers nor see teleport/schedule tools. The policy layer seals the
-authenticated avatar into every mutation; tool schemas contain a catalog
-selector or bounded interval, never an avatar, region, coordinate, inventory
+accept offers nor see create/teleport/schedule tools. An authorized agent can
+create and catalog a landmark for its current position in the standard
+Landmarks inventory folder. The policy layer seals the authenticated avatar
+into every mutation; tool schemas contain only a landmark name, catalog
+selector, or bounded interval, never an avatar, region, coordinate, inventory
 folder, or L$ field.
 
 The live adapter subscribes through the original LibreMetaverse compatibility