The editor: project assets, agents hear edits, agent marks seen

Project assets in the inspector: a Unity scene's asset fields (materials, textures, sprites, clips, animation clips, controllers, physics materials, fonts, text assets, meshes) pick from the project's files of that type, found by scanning Assets and its .meta GUIDs, named as scenes name them ({"asset": "guid:fileID"}, with the type's main-object file ID); meshes also offer Unity's built-in primitives. Labels show the file ("Assets/Materials/Ball.mat", "Sphere (built-in)"). Text fields have room for a value.
Agents hear about a person's edits: a GET on /mcp with Accept: text/event-stream opens the Streamable HTTP event stream (written on the socket, an event at a time); while one is open the editor reads the subscribed resources twice a second and sends notifications/resources/updated for those that changed.
Agent marks looked at (--screenshot --mark <name> marks an object as an agent's work): the rings read, the names now sit on a pill in the agent's color.
Tests: Coin Dash's materials and Unity's meshes are offered with their keys and labels; picking another material for the Player in the inspector writes its {"asset"}; a client subscribed to tassix://scene gets the update on its event stream after a person renames an object.
Not yet: handles and grid drawn over objects; sub-assets (meshes inside models, sprites in sheets) and prefabs in the asset picker.