A user reported FlareCode said it pushed a branch, but GitHub showed different, near-empty work — the agent's real commits never left the box. We fixed the publish path so "done" means done.
What changed
- Pushes the agent's actual work. Managed publish pushes the current commit to the canonical
flarecode/task-*branch, so your work lands even if the agent strayed onto a differently-named local branch — or a fresh project defaulted its local branch tomaster. - Verifies the push landed. After pushing, we confirm the remote branch tip matches the commit we sent. A rejected or partial push now surfaces a real failure with detail instead of a silent "success," and the result carries the exact landed commit.
- Recovers a deleted repo. Shipping an agent whose original GitHub repo was removed now rebuilds a fresh repo from your durable workspace instead of dead-ending on an error.
- No more raw error blobs. API failures render as human copy — a repo-target error reassures you your work is safe in the workspace backup instead of printing
{"error":"…"}on the card. - Collapsible publish logs. The publish and deploy progress pane can be hidden once it's done while keeping the result link visible, so it no longer stays pinned over the preview.
Why
The whole point is to keep moving: review, ship, share in one motion. That only works if the ship step is honest about what actually happened.