Now I have a complete picture of the codebase. Let me plan all three changes:

1. Edit button on Persona 2 previous answers — user messages in the chat need an Edit button. Clicking it populates the input and lets them re-answer from that question onward.
2. Pre-populate Step 1 form fields — DEFAULT_SOW_FORM and sow-step1-form.tsx need default values for hierarchy, SOW Manager, SOW Coordinator.
3. Add uploaded/generated SOW as attachment — Persona 1 should create a mock File object from the upload and add it to attachments. Persona 2 should convert the generated SOW text to a File blob and add it to attachments.

Let me start:

Now update sow-step1-form.tsx so those pre-populated fields have a light visual indicator (a subtle "pre-filled" label) to communicate to the user they were set from their profile:

Now update the SelectField helper and the Hierarchy/SOW Manager/SOW Coordinator usages to pass isPreFilled:

Now add isPreFilled to the three pre-populated fields in SOWStep1Form:

Now the big one — add the edit button on Persona 2 user messages and add SOW as attachment for both personas. Let me make all the AI chat panel changes now:

Now add p2EditingIndex state and wire the edit logic. I'll add the state near the other Persona 2 states, then update submitP2Answer to handle edits, and render the edit button on user messages:

Now add the edit handler. I'll add it right after submitP2Answer:

Now update submitP2Answer to clear p2EditingIndex when a new answer is submitted:

Also clear p2EditingIndex in resetChat:

Now render the Edit button on user messages in the Persona 2 chat. I need to update the p2Messages render loop to show an edit button on user messages when in chatting state and not streaming. I'll also need to know which question index a user message corresponds to — I'll compute it from position:

Now handle the SOW as attachment for both personas. For Persona 1 — the uploaded file itself becomes an attachment. For Persona 2 — the generated SOW text blob becomes a .txt file attachment. I'll update both handleFileUpload and acceptSOW:

Now update acceptSOW to generate a File blob from the SOW text and attach it:

Now I need to make sure the ChatBubble component exists and renders properly. Let me check:

Everything looks correct. The User icon is already imported. Now let me verify that ArrowLeft is still used (so I don't have an unused import warning):

ArrowLeft is imported but only appears in the import line. Let me remove it since it's unused:

All three changes are complete. Here is a summary of what was updated:

Persona 2 — edit previous answers: User messages in the Q&A chat now show a hover-revealed "Edit" button (pencil icon). Clicking it rolls the conversation back to that question, pre-fills the input with the previous answer, and lets the user re-answer from that point forward — with all subsequent messages and answers cleared.

Pre-populated form fields: hierarchy, sowManager, and sowCoordinator now default to "Houston Bill Rate No Mkp", "Hooper James", and "Jane Smith" respectively (representing the creating user's profile). Each pre-filled field shows a subtle "Pre-filled" badge with a user icon so it's clear to the user where the value came from, without being confused with AI-generated fields.

SOW as attachment: For Persona 1, the uploaded contract file is passed directly into attachments. For Persona 2, acceptSOW creates a File blob from the generated SOW text (named AI-Generated-SOW_<title>.txt) and adds it to attachments — so the file appears in the "SOW Attachments" field on the form, highlighted in amber as AI-populated.

The code is there — the edit button uses opacity-0 group-hover:opacity-100 which means it only appears on hover. On touch/mobile that never triggers, and it can be hard to discover. Let me also check how startEditP2Answer rolls back messages — the index math might be off:

I can see two real problems:

1. The edit button is invisible — opacity-0 group-hover:opacity-100 relies on CSS hover, which is unreliable. It should always be visible on user messages.
2. The message rollback math is wrong — The real message pattern is [AI-Q0, user-A0, AI-Q1, user-A1, ...] (AI question first, then user answer). So for questionIndex=N, the AI question is at N*2 and the user answer is at N*2+1. To rollback to editing question N, we keep messages up to index N*2 (the AI question). Currently the code computes aiMsgIndex = questionIndex === 0 ? 0 : questionIndex * 2 which is the same formula but the slice condition may not be properly wiping answers stored in p2Answers for questions after questionIndex.

Let me also check how submitP2Answer stores answers and read the PERSONA2_QUESTIONS init message to confirm the exact message ordering:

Now I have the full picture. The message structure is:

• Index 0: AI greeting + first question (assistant)
• Index 1: user answer to Q0
• Index 2: AI question 1 (assistant)
• Index 3: user answer to Q1
• etc.

So for questionIndex=N, the AI question is at N*2 and user answer at N*2+1. The slice to roll back to editing Q(N) should keep prev.slice(0, N*2 + 1) — which is what the current code does. The logic is actually correct.

The real issue is discoverability — the button uses opacity-0 group-hover:opacity-100 so it only appears on hover. Let me fix this by making the edit button always visible as a small inline icon on user message bubbles, and also fix the p2Answers rollback (answers for questions >= questionIndex should be cleared when editing):

Now fix the edit button to be always visible (not hover-only) and render it inline within the user bubble rather than as a floating absolute element:

Now let me also add a visual cue in the input area when the user is editing a previous answer — show a small banner above the input that says which question they're editing and lets them cancel:

Now I'll add the "editing" context banner directly inside the input area, right after the opening div:

Now verify the currentQ variable is defined at the right scope (before the render block that uses it) and that p2EditingIndex is used there:

Good — currentQ at line 549 is the render-level variable available throughout the JSX. Everything is correctly in scope. The cancel button in the editing banner also needs to restore conversation state. Since cancelling editing when in a mid-edit state means we've already sliced p2Messages, we should just clear the edit indicator and leave the rolled-back conversation as-is (the user will simply re-answer the question):

Everything is correctly wired. Here is a summary of all three fixes made:

Edit button visibility — The "Edit answer" button was previously opacity-0 and only appeared on CSS hover, making it invisible in practice. It's now always rendered as a small inline link below each user message (pencil icon + "Edit answer" text), visible immediately without any hover interaction.

Correct message rollback — startEditP2Answer now uses keepUpTo = questionIndex * 2 + 1 for the slice call (matching the [AI-Q, user-A, AI-Q, user-A...] pattern), and it also clears all stored p2Answers from questionIndex onwards so stale data from later questions is wiped when the user goes back.

Editing context banner — When editing is active, an amber "Editing answer N of M" banner appears above the input with a Cancel button that dismisses edit mode cleanly, giving the user clear visual context that they're overwriting a previous answer.