Chat drawer sometimes shows “Proposed editor update is ready…” without rendering an “Apply update” button

[knightedcodemonkey]

Summary

In the AI chat drawer, assistant responses can show proposal status text (“Proposed editor update is ready. Review and apply below.”), but no Apply action buttons are rendered. This creates a dead-end UX where the user is told an editor update is ready but cannot apply it.

Current Behavior

1. User sends a prompt asking for code changes.
2. Assistant response indicates a proposed editor update is ready.
3. Message renders without any Apply update button(s) (Component, Styles, or combined apply).

Expected Behavior

1. If a proposal exists, the message should render the corresponding Apply action(s).
2. If a proposal cannot be parsed, status text should not claim an update is ready.
3. User should never see a “ready to apply” message without an actionable control.

Repro Steps

1. Open app with valid GitHub token and writable repo selected.
2. Open AI Chat and submit a prompt requesting editor updates.
3. Observe a response with “Proposed editor update is ready. Review and apply below.”
4. In some runs, no Apply button appears under that assistant message.

Impact

• Blocks primary chat-to-editor workflow.
• Confusing UX and reduced trust in assistant actions.
• Forces manual copy/paste fallback.

Suspected Area

• Proposal extraction / normalization path in:
  • proposals.js
• Rendering gate for apply actions in:
  • drawer.js

Likely Root Cause

Mismatch between detected “proposal-ready” state and parsed proposal payload shape. Tool-call payload variations (or partially structured arguments) may pass the “ready” signal but fail proposal extraction, preventing action button render.

Acceptance Criteria

1. When proposal-ready status appears, at least one matching Apply button is visible.
2. No false-positive proposal-ready messages without actions.
3. Handles payload shape variations robustly (or degrades gracefully with clear error/status).

Optional Diagnostics to Add

1. Temporary debug logging for parsed proposal targets/content presence.
2. Message-level fallback status if proposal parsing fails after tool calls are returned.