fix(web): preserve composer draft during worktree setup

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Draft promotion deleted composer state when setup completed, so follow-up text typed while a remote worktree action was running disappeared. This moves the draft to the canonical scoped thread key when promotion finalizes and covers edits made during promotion in the existing store tests.

Verification: 101 focused store tests, web typecheck, targeted lint, and a real app flow with an eight-second worktree setup passed. Real T3 Code verification video.

Implemented with gpt-5.6-sol in the Codex harness.

---

Note

Medium Risk
Touches composer draft lifecycle during promotion finalization; wrong key handling could duplicate or leak drafts, but scope is limited to the promoting-draft cleanup path with added test coverage.

Overview
Fixes composer text disappearing when a draft thread finishes promoting (for example while a remote worktree setup is still running). Finalizing promotion used to drop the draft’s composer state when cleaning up draft-thread mappings; it now relocates that state onto the canonical scoped thread key from promotedTo instead of revoking attachments and deleting the draft entry.

removeDraftThreadReferences accepts an optional destination ref for that move. finalizePromotedDraftThread only runs when a promoting draft exists and passes promotedTo through. Store tests now assert prompts survive on the real thread after finalize, including text typed on the draft id after markPromotedDraftThread.

^{Reviewed by Cursor Bugbot for commit b080411. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix finalizePromotedDraftThread to preserve composer data on canonical thread

• Composer text written while a draft is being promoted was lost when the draft thread was removed during finalization.
• removeDraftThreadReferences now accepts an optional canonical destination; when supplied, it re-keys the draft's composer data to the canonical thread instead of revoking preview URLs.
• finalizePromotedDraftThread passes the promoted destination to the helper so the composer data survives cleanup.
• Risk: removals without a destination still revoke preview URLs, but any caller that previously relied on composer data being discarded during promotion will now see it retained under the canonical key.

^{Macroscope summarized b080411.}

[macroscopeapp]

Approvability

Verdict: Approved at b080411

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that moves composer state from a promoted draft ID to the existing canonical scoped thread key, preserving text entered during worktree setup. The accompanying test covers the promotion-time edit scenario, with no schema, configuration, security, billing, or deployment impact.

^{You can add or adjust custom eligibility rules. Learn more.}