feat: Add capability ledger framing and fix hooked/pinned terminology (gt-3amkz)

Add "The Capability Ledger" section to all 6 role templates explaining:
- Work visibility and reputation
- Redemption through consistent quality
- Every completion as evidence of autonomous execution at scale
- Work history as growing portfolio/CV

Also fix hooked vs pinned terminology confusion:
- "Hooked" = work assigned to you (triggers autonomous mode)
- "Pinned" = permanent reference beads
- Add clarifying note to all startup behavior sections
- Update code examples to use --status=hooked

Update prime.go AUTONOMOUS MODE output with ledger framing.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

internal/cmd/prime.go

@@ -904,6 +904,10 @@ func checkSlungWork(ctx RoleContext) bool {
 	fmt.Println("Every moment you wait is a moment the engine stalls. Other agents may be")
 	fmt.Println("blocked waiting on YOUR output. The hook IS your assignment. RUN IT.")
 	fmt.Println()
+	fmt.Println("Remember: Every completion is recorded in the capability ledger. Your work")
+	fmt.Println("history is visible, and quality matters. Execute with care - you're building")
+	fmt.Println("a track record that proves autonomous execution works at scale.")
+	fmt.Println()
 	fmt.Println("1. Announce: \"" + roleAnnounce + "\" (ONE line, no elaboration)")
 	fmt.Printf("2. Then IMMEDIATELY run: `bd show %s`\n", hookedBead.ID)
 	fmt.Println("3. Begin execution - no waiting for user input")