Add entity writes (create_entity, update_entity, delete_entity) to parallel query_entities

The MCP read path (query_entities) is excellent. The write path is missing. Today, for my orchestrator to write a SystemEvent record, post a CommandDirective to a Super Agent inbox, correct a broken UserProfile row from a support ticket, or maintain AuditReport rollups, every write has to be routed through the async edit_base44_app builder loop — which is wasteful for what is really just a database write.

Requested primitives:

• create_entity({ appId, entityName, record }) — insert a new record

• update_entity({ appId, entityName, recordId, fields }) — patch an existing record

• delete_entity({ appId, entityName, recordId }) — remove a record

Direct entity writes turn the orchestrator into a true coordination layer between apps, not just a code-edit pipe. They also massively reduce load on the builder agent for simple data operations.

Thank you.