(CODUX-107) Document invocation planning plan behavior

[numnx]

🧩 Task: Document invocation planning plan behavior

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 175 · Fix Execution Plan · Task: T03

Ensure each Chat invocation for sprint planning displays the execution plan persisted for that invocation's own sprint, not a generic or most-recent planning entry.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 12:12:53 UTC
Finished	2026-07-07 12:15:19 UTC
Duration	2m 26s

📊 Token Usage

Metric	Value
Input tokens	43,528
Cached input tokens	320,640
Output tokens	3,854
Total tokens	368,022
Invocations	1
Tool calls	20
Active time	2m 0s

Included usage estimate (subscription/local login): $0.49

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Document the corrected Chat invocation behavior so operators know planning transcripts are sprint-specific and replayable from persisted invocation data.

## Scope
- Edit `docs/dashboard/dashboard-guide.md`
- Edit `docs-web/user/dashboard/chat.md`
- Verify `docs/index.md` and `docs/SUMMARY.md` already link the affected dashboard docs; update them only if a new dedicated page is created, which is not expected for this fix
- Relevant docs sections: Chat page behavior, Invocations tab, execution invocation API notes

## Implementation Requirements
1. Add a concise note to the Chat/Invocations documentation that planning invocations include the execution plan generated for that invocation's linked sprint.
2. Clarify that the plan shown in the transcript comes from persisted invocation message metadata, not from the currently selected sprint or latest planning run.
3. Mirror the user-facing behavior note in `docs-web/user/dashboard/chat.md` so published docs match canonical docs.

## Constraints
- Do not claim the linked issue is closed or mention branch/PR/merge workflow.
- Keep release-note style details out of these docs; this is product behavior documentation.
- Preserve existing markdown structure and avoid broad rewrites unrelated to Chat invocations.

## Verification
- Run `pnpm run lint` if TypeScript files from dependencies are present in the merged branch; for docs-only execution, run `pnpm run build` only if local time permits.
- Success means both canonical and published dashboard docs describe sprint-bound planning execution plans consistently.

🌿 Branch Info

Base: feature/CODUX-175-fix-execution-plan
Head: task/feature-codux-175-fix-execution-plan-t03-codex-mram0lvr

---

🤖 Generated by Code UX