Specialist agent identity evidence

The retained Issue #20 was created with the maintenance opt-out marker so it remains stable. Each comment was posted through that account's own Forgejo token.

Account	Role	Forgejo profile capture
glm-maintainer	Coordinator and router
designer-agent	Visual and accessibility specialist
coding-agent	Implementation and test specialist
docs-agent	Documentation specialist
security-agent	Release security and supply-chain specialist	Generated profile evidence is captured during the release-branch E2E verification.
review-agent	Independent reviewer

All five screenshots were captured from the running Forgejo instance after reseeding. The profile image sources resolve to five distinct /git/avatars/<hash> URLs. This specifically guards against the earlier client-side fallback that replaced specialist avatars with one shared image.

Mention-driven delegation

Issue #21 is the retained end-to-end proof for the actual orchestration order:

1. glm-maintainer classifies the Issue and visibly mentions @docs-agent.
2. Only after the mention is published, the docs-agent job enters running and adds the 👀 reaction.
3. docs-agent creates PR #22, adds 🚀, and posts its own completion comment.