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:
@@ -518,7 +518,7 @@ type AgentFields struct {
|
||||
Rig string // Rig name (empty for global agents like mayor/deacon)
|
||||
AgentState string // spawning, working, done, stuck
|
||||
HookBead string // Currently pinned work bead ID
|
||||
RoleBead string // Role definition bead ID
|
||||
RoleBead string // Role definition bead ID (canonical location; may not exist yet)
|
||||
}
|
||||
|
||||
// FormatAgentDescription creates a description string from agent fields.
|
||||
|
||||
Reference in New Issue
Block a user