feat: Key agent table config dump off agent name for primary record selection

[NOVA-Openclaw]

Overview

The agent table config dump (used by agent-config-sync and bootstrap context) currently does not key off the agent name when determining which record to include as the primary entry in the agents list.

Desired Behavior

When generating the agent configuration list (e.g. for openclaw.json agents.list[] or bootstrap context), the system should use the agents.name column as the key to determine which record is the primary/canonical entry for each agent.

Current Behavior

The config dump does not distinguish which agent record should be treated as primary when multiple records or configurations could apply.

Acceptance Criteria

• Agent table config dump keys off agents.name to select the primary record
• Each agent name maps to exactly one primary configuration entry
• Existing agents continue to work without manual intervention after the change

Related

• agents table in nova_memory database
• agent-config-sync system in cognition/
• Bootstrap context loading (agent_bootstrap_context table)