Replace hardcoded 'Daniel' user references with dynamic principal.name

[neilsoult]

Problem

Several files in the PAI codebase contain hardcoded references to "Daniel" as the user identity. When someone other than Daniel uses PAI, the system still refers to "Daniel" instead of the actual principal's name from settings.json.

Impact

Users who configure their own principal.name in settings.json still see "Daniel" in:

• Agent voice notification instructions (11 files)
• Variable names in hooks
• File name references

Affected Files

HIGH PRIORITY - Agent Files (Packs/pai-agents-skill/src/agents/)

All contain: "DO NOT SKIP - Daniel needs to hear you speak"

• Architect.md (line 76)
• Artist.md (line 72)
• ClaudeResearcher.md (line 91)
• CodexResearcher.md (line 78)
• Designer.md (line 73)
• Engineer.md (lines 74, 184)
• GeminiResearcher.md (line 91)
• GrokResearcher.md (line 77)
• Intern.md (line 94)
• Pentester.md (line 93)
• QATester.md (line 72)

MEDIUM PRIORITY - Hook Files

• Releases/v2.5/.claude/hooks/RelationshipMemory.hook.ts: Variable danielPreferences should be principalPreferences
• Releases/v2.5/.claude/skills/PAI/Tools/RelationshipReflect.ts: References ABOUT_DANIEL.md

Proposed Fix

Replace hardcoded "Daniel" user references with the principal name from settings.json:

1. Agent files: Change to "The principal needs to hear you speak" or use a placeholder that gets substituted
2. Variable names: Rename to generic names like principalPreferences
3. File references: Use ABOUT_PRINCIPAL.md or dynamic naming

Notes

• This does NOT affect:
  • Author attribution ("Author: Daniel Miessler") - these are correct
  • Voice name references ("Daniel" ElevenLabs voice) - these are correct
  • Repository URLs (danielmiessler/PAI) - these are correct

Only USER IDENTITY references that assume the user is named "Daniel" need to change.

---

Reported via PAI system analysis

[danielmiessler]

Thanks for reporting this! We've been doing a major restructuring of PAI's core systems, including a complete redesign of the hook architecture (consolidated from 22 to ~19 hooks), a rewritten Algorithm (now v0.5.1 with PRD-based verification), removal of the observability system, and numerous path/configuration fixes.

This specific issue is addressed by those changes. We're targeting a v3.0 release soon that will include all of this. We appreciate your patience and your help in identifying these issues — it directly informed our redesign work. Stay tuned!