Show release context in plan comment#

Plan phase complete. Technical plan is ready.

Problem#

When a task belongs to an active release, the plan comment posted at the end of the plan phase contains no release information. Developers and reviewers have no immediate visibility into which release a task is associated with, its RC branch target, or directive.

Task / Link#

Closes #470

Changes#

• release.service.ts: Expanded findActiveForTask() return type to include key, title, status, directive alongside existing releaseId, rcBranch, baseBranch
• github.service.ts: Added findCommentByPrefix() method that paginates issue comments and returns the first matching { id, body } or null
• phase-hooks.service.ts: Injected ReleaseService; updated onPlanComplete() to append a ## Release Context section (human-readable + collapsed JSON metadata) to the existing plan comment, with fallback to a standalone comment if the plan comment is not found
• phase-hooks.module.ts: Imported ReleaseModule to make ReleaseService available
• release.service.spec.ts: Updated findActiveForTask assertions to cover the new fields
• phase-hooks.service.spec.ts: Added tests for release-present (edit comment), release-present + no plan comment (standalone post), no release (simple comment), and service error fallback

Notes#

• If findCommentByPrefix returns null (plan comment not yet visible due to propagation lag), the release context is posted as a standalone comment — graceful fallback.
• findCommentByPrefix paginates at per_page=100 to handle issues with many comments.

Testing#

• Unit tests: all 804 pass (npm run test)
• Lint: zero warnings (npm run lint)