feat: add conversation history to invoke TUI

[notgitika]

Description

Invoke now preserves and displays full conversation history like the dev screen, instead of showing only the latest message pair. Also pins the log file link in the header.

Now consistent with dev invoke experience in the TUI

Related Issues

Documentation PR

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

Manually tested CLI invoke flow post running build

• I ran npm run test:all
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	8.09%	532 / 6568
🔵	Statements	7.78%	543 / 6979
🔵	Functions	5.47%	73 / 1334
🔵	Branches	6.05%	230 / 3800

Generated in workflow #260 for commit 5504a9c by the Vitest Coverage Report Action

[aidandaly24]

approved

[agentcore-cli-automation]

Reviewed post-merge. Just one observation for posterity (no action needed since this PR is already merged):

• Color preservation on wrapped lines: In this PR, formatConversation returns a single string and the renderer detects user messages by checking line.startsWith('> ') after wrapping (InvokeScreen.tsx ~line 314 in the diff). For a user message that wraps to multiple lines, only the first wrapped line keeps its > prefix, so continuation lines get rendered as the assistant color (green). DevScreen solved this by using a ColoredLine[] representation through wrapColoredLines, preserving color on continuations. Looks like this was subsequently addressed in feat(invoke,dev): add exec mode for running shell commands in runtimes #750, where InvokeScreen was refactored to use wrapColoredLines as well — so no follow-up needed.

• Code duplication: wrapLine / wrapText / formatConversation were copy-pasted from DevScreen.tsx. Worth extracting to a shared util in a future cleanup pass (the post-feat(invoke,dev): add exec mode for running shell commands in runtimes #750 code still has parallel implementations across the two screens).

The magic-numbers nit was already raised in the inline thread and acknowledged for a future PR. Otherwise this looks fine.

[github-actions]

Thanks for the report, @agentcore-cli-automation — feedback like this is exactly
how we catch the things we missed. Because this PR is already
closed, the team won't see follow-up comments here.

Would you mind opening a new issue so we can track it properly?
https://github.com/aws/agentcore-cli/issues/new/choose

If this is a security issue, please report it privately via
https://aws.amazon.com/security/vulnerability-reporting/ instead
of a public issue.