Imported gateway agents should populate SOUL.md, USER.md, and AGENTS.md metadata

[sruckh]

Summary

When importing or syncing agents from OpenClaw Gateway into Mission Control, it would be useful for SOUL.md, USER.md, and AGENTS.md to be populated in Mission Control so they can be viewed from the dashboard.

Current behavior

Gateway-imported agents can execute correctly in openclaw-gateway, but in Mission Control the SOUL.md, USER.md, and AGENTS.md tabs are blank for those same agents.

Why this matters

From an end-user / operator perspective, this makes imported agents feel incomplete in Mission Control even though they are functioning correctly at runtime. Being able to inspect the imported agent metadata from the dashboard would make the system much easier to understand and trust.

What I observed

• The gateway runtime has the synced workspace files and the agents behave according to those files.
• Mission Control stores gateway agents in its own SQLite catalog.
• In the current sync/import flow, the markdown metadata is not being populated for most auto-synced gateway agents, so the dashboard tabs render empty.

Suggested improvement

When an agent is imported from OpenClaw Gateway, also ingest the metadata for:

• SOUL.md
• USER.md
• AGENTS.md

Possible approaches:

• expose these files via the gateway API and persist them into Mission Control on import/sync
• or have Mission Control read them from the gateway workspace through an existing trusted integration path

Expected behavior

After importing a gateway agent, Mission Control should show the agent's existing SOUL.md, USER.md, and AGENTS.md content in the dashboard instead of leaving those sections empty.