Repo-qualify collision-prone agent names

[miyaontherelay]

Summary

• centralize agent-role naming and repo-qualify GitHub implementer, reviewer, workflow, and lazy babysitter identities
• preserve byte-compatible Linear names while keeping prompts, retries, resume/restart, registry, reaper, and lifecycle consumers aligned
• isolate demonstrated same-number cross-repo orchestration state, PR caches, publication guards, and babysitter state
• add concurrent multi-repo collision and lifecycle regressions

Validation

• focused triage/orchestrator tests: 299/299 passed
• full npm test: 38 files, 747/747 passed
• npm run build
• npm pack --dry-run (262 files; naming helper artifacts included)
• git diff --check

Integration

Rebased onto af1499b after PR #80 merged. The sole test overlap preserves both the awaited clarification counter assertion from #80 and the repo-qualified reviewer expectation. Independent post-rebase shadow audit approved the exact candidate.

Known residual

Repositories with the same basename under different owners can still share the existing basename-derived suffix. This matches the pre-existing implementer convention and is outside the scope of this issue.

Fixes #82

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!