docs: clarify RoleBead semantics in agent bead creation
Added comments explaining that RoleBead establishes a naming convention for the canonical location of role definitions. The referenced bead may not exist yet - this enables tooling like gt doctor to check for and scaffold missing role beads. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -445,6 +445,9 @@ func (m *Manager) initAgentBeads(rigPath, rigName, prefix string, isFirstRig boo
|
||||
continue // Already exists
|
||||
}
|
||||
|
||||
// RoleBead establishes the canonical bead ID for this agent's role definition.
|
||||
// The bead may not exist yet - this declares the naming convention so tooling
|
||||
// (like gt doctor) can check for missing role beads and scaffold them.
|
||||
fields := &beads.AgentFields{
|
||||
RoleType: agent.roleType,
|
||||
Rig: agent.rig,
|
||||
|
||||
Reference in New Issue
Block a user