fix(project-context): Integrate PR #320 path fix and test hooks

[sylvansys]

Summary

• Integrated parent transcript path fix from PR fix(project-context): Apply parent transcript path fix from PR #312 #320 into task-state.ts
• Closed PR fix(project-context): Apply parent transcript path fix from PR #312 #320 after integration
• Tested prompt-based hooks via subagent execution

Changes

File: plugins/project-context/shared/hooks/utils/task-state.ts

Fixed the getTaskEdits function to correctly resolve parent transcript paths:

• Agent transcripts: .../project/{sessionId}/subagents/agent-{agentId}.jsonl
• Parent transcripts: .../project/{sessionId}.jsonl

The previous code only went up one directory level, causing "parent transcript not found" errors.

Test Results

Test	Result
Fix applied and committed	✅
PR #320 closed	✅
Subagent receives context/rules	✅
SubagentStart hooks fire	✅ (4x)
SubagentStop hooks fire	✅ (10x)
Subissue created	✅ (#322)

Test Plan

• Apply fix from PR fix(project-context): Apply parent transcript path fix from PR #312 #320
• Close PR fix(project-context): Apply parent transcript path fix from PR #312 #320
• Launch test subagent to verify hooks fire
• Verify subagent receives CLAUDE.md and rules context

Closes #321

🤖 Generated with Claude Code

[github-actions]

Constellos Review - PR feedback from your reviewer agents.

Requirements: ❌ 0 • ❌ 0 • ⏭️ 0

View agent prompt

Code Quality: ✅ 4 • ❌ 0 • ⏭️ 0

Check	Status	Reasoning
DRY Compliance	✅	No significant code duplication found. Utility functions are well-factored and reusable (e.g., file path getters, git operations). Both files follow similar state management patterns appropriately for their different domains (stacked branches vs task state).
YAGNI Compliance	✅	Code implements only what's needed for the stacked PR workflow. No speculative features or over-engineering detected. The comprehensive documentation and type definitions serve the actual implementation needs.
Modularity	✅	Both files demonstrate excellent separation of concerns with clear logical sections (constants, types, state management, git operations, PR operations, cleanup). Functions are single-purpose and well-organized. The task-state module properly separates context persistence from transcript analysis.
Maintainability	✅	Code is highly maintainable with comprehensive JSDoc comments, clear function names, explicit types, and well-structured organization. Each function has a clear purpose, parameters are well-documented, and error handling is consistent. The section separators make navigation easy.