feat: per-bullet rewrite affordance inside reconstructed-resume view (C)

[s-annam]

Summary

Re-attach the per-bullet "Suggest a rewrite" affordance inside the Reconstructed Resume view, on flagged bullets, in context under their role — replacing the standalone placement it had under the retired PerBulletFeedback surface.

This is the deferred final piece of the resume-view pivot. It reuses the existing WebGPU/Qwen2-1.5B pilot (landed in #39) — no new model work; this issue is about placement and wiring the rewrite control into the new view.

Depends on A (the view + inline bullet flags must exist). Independent of B (editing) — can land before or after.

Scope

In:

• Surface the existing rewrite affordance on flagged bullets within ReconstructedResume, in context (under the owning role).
• Reuse the existing WebGPU-gated rewrite pilot: keep WebGPU-only gating, hide the CTA on unsupported browsers, lazy-load the heavy runtime on explicit click (never silent-degrade) — same discipline as feat(webllm): per-bullet "Suggest a rewrite" pilot — WebGPU-only, Qwen2-1.5B #39.
• Flagged bullets only (passing bullets don't need it).

Out:

• Any change to the rewrite model / prompt / quality.
• Cloud or desktop rewrite providers (stay at Recruidea).
• Accepting a rewrite back into the editable parse (interaction with B) — if in scope, scope it explicitly here at implementation time; default v1 is rewrite-as-suggestion only.

Reuse analysis

Capability = "suggest a rewrite for a bullet." Already owned by the #39 pilot. This issue re-homes that control into the new view — pure reuse + reposition, no parallel surface, no new capability.

Acceptance

• Rewrite affordance appears on flagged bullets inside ReconstructedResume, in role context.
• WebGPU gating + lazy-load behavior preserved from feat(webllm): per-bullet "Suggest a rewrite" pilot — WebGPU-only, Qwen2-1.5B #39.
• No regression in the rewrite pilot itself.
• npm run test + npm run typecheck green.

Blocked by: #57 (A) (Reconstructed Resume view + inline flags).

[s-annam]

Implementation Complete — 7d5e94d

Acceptance Criteria

• Rewrite affordance on flagged bullets inside ReconstructedResume, in role context — RewriteButton re-homed into the flagged branch of ResumeBulletRow (ReconstructedRole.tsx).
• WebGPU gating + lazy-load preserved from feat(webllm): per-bullet "Suggest a rewrite" pilot — WebGPU-only, Qwen2-1.5B #39 — RewriteButton reused unchanged; WebGPU-only gate (null return on unsupported) + lazy-load-on-click intact.
• No regression in the rewrite pilot — rewrite-bullet.test.ts + capability.test.ts pass.
• npm run test + npm run typecheck green — typecheck clean, 270/270 tests.

Additional Changes

• Suggestion-only (per epic gate decision) — no write-back into the useEditableParse editable parse; no coupling to feat: inline editing in reconstructed-resume view (B — contact + role headers, in-memory) #58.
• Flagged bullets only; passing bullets get no rewrite control.
• Minimal layout change: flagged block wrapped flex-col so the rewrite control sits below the badge row.