Skip to content

Preserve chat transcript and board-load recovery state - #2828

Merged
Chris0Jeky merged 1 commit into
mainfrom
issue-2004/chat-recovery-truth
Sep 9, 2026
Merged

Preserve chat transcript and board-load recovery state#2828
Chris0Jeky merged 1 commit into
mainfrom
issue-2004/chat-recovery-truth

Conversation

@Chris0Jeky

Copy link
Copy Markdown
Owner

A successful chat submission could lose the visible user instruction when the follow-up transcript read failed. Keep the submitted instruction beside the assistant reply until an authoritative refresh succeeds. Failed board-option reads now have a persistent error and explicit retry, reducing recovery effort while preserving explicit submission and board selection.

Refs #2004. This is a bounded recovery slice, not completion of the full issue.

Validation at 040c94d against 22fcac4:

  • Author: four red regressions before implementation; 89 focused tests passed; full frontend 6,237 passed / 3 skipped; typecheck, scoped lint, build and diff checks passed.
  • Fresh independent Terra review: SHIP; independently ran both changed test files, 41 tests passed; no confirmed HIGH/CRITICAL.
  • Browser flow has not been exercised for this slice. Hosted CI is pending.
  • One non-blocking display duplication case after successful bind followed by another failed refresh is tracked at Automation Chat produces prose, never proposals — the chat workflow needs re-thinking #2004 (comment). It does not resend a server action.

No canonical STATUS or MASTERPLAN edit; coordinator ownership remains reserved. Source and review evidence are recorded in the local milestone checkpoint.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 9, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-09T13:24:45.453025Z 040c94d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Chris0Jeky Chris0Jeky moved this from Pending to Review in Taskdeck Execution Sep 9, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 040c94d231

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread frontend/taskdeck-web/src/components/chat/ChatMessageList.vue
@Chris0Jeky

Copy link
Copy Markdown
Owner Author

Coordinator cleanup: verified local and remote head 040c94d, clean tracked state, and ignored inventory containing only disposable frontend dist/ and node_modules/. Worker confirmed no worktree processes or runtime listeners. Removed the completed worktree with plain git worktree remove; branch and all five changed files remain preserved remotely. No unique ignored artifacts required copying. Full-suite evidence was author tool session 62294 (6237 passed, 3 skipped, exit 0); no file-backed log was produced. Fresh review independently ran 41 tests. Human-action file remains unchanged.

@Chris0Jeky

Copy link
Copy Markdown
Owner Author

Delivery is now held for combined candidate #2830 at 3923500 on main06bd4d18e. It preserves the reviewed source commit, passed the full combined backend9096/5skip and frontend6243/3skip suites, browser SC-005, builds/lint/doc links, and fresh Terra integration review. Do not merge sources independently while the combined exact-base/head hosted gate qualifies. Once #2830 lands, coordinator will verify inclusion and reconcile these source PRs. Existing tracked MEDIUMs remain open; no new feature changes added.

@Chris0Jeky
Chris0Jeky merged commit d5469fc into main Sep 9, 2026
35 checks passed
@Chris0Jeky
Chris0Jeky deleted the issue-2004/chat-recovery-truth branch September 9, 2026 14:13
@github-project-automation github-project-automation Bot moved this from Review to Done in Taskdeck Execution Sep 9, 2026
@Chris0Jeky

Copy link
Copy Markdown
Owner Author

Delivered through #2830, merged as cca0716. Main tree c73859a9ba712192935fc13586260ab61a9fb22c exactly equals qualified39235004b; all three source heads are verified ancestors. GitHub automatically marked #2827/#2828/#2829 merged through preserved commits. Required ci-required.yml run34358736114 passed at the exact head/base, fresh Terra review passed and no unresolved threads remained. Tracked MEDIUMs remain follow-ups; no full parent-issue completion claim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant