القائمة
Do not treat opaque runtime handles as stable roster identities
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
{what this skill teaches agents}
Validate Squad avatar regressions with alias-resolution probes and source assertions around reset paths.
Use stable agent identity fields for metadata joins and reserve instance ids for runtime bookkeeping.
Render live sub-agent badges from resolved identity, current model, and active work state.
Protect persisted voice selections when async voice lists reload or the active TTS engine changes.
Replay extension state only after the webview page declares its own ready flag.
| name | opaque-agent-id-mapping |
| description | Do not treat opaque runtime handles as stable roster identities |
| domain | integration-testing |
| confidence | high |
| source | earned |
This applies when UI code tries to decorate runtime agent events with roster metadata. If the runtime emits opaque handles like agent-call_H but the roster is keyed by durable slugs like howard-the-duck, a direct lookup on agentId will still miss.
displayName or persistent roster names before falling back to raw internal IDs.agentId already equals the roster slug.howard-the-duck; runtime event ID: agent-call_H → direct agentId lookup fails without translation.event displayName → roster display name from translated identity → agentName → raw agentId.agentId is automatically the same as a roster slug.