fix(web): imply force reassign from an offline source instead of arming it

[zfy0701]

What changed

Moving an agent off an offline daemon used to take three steps: a Force reassign button inside the "Safe move unavailable" banner, a confirmation checkbox, and only then the footer button. The banner already explains the risk, so the arming step added friction without adding safety.

Now, picking an online, compatible destination while the source daemon is offline makes the move a force reassign directly:

• The banner states that the move will force reassign and warns that a still-running source means both copies may process messages — the same risk prose the checkbox used to carry.
• The footer button stays danger-styled and labeled Force reassign, so the commit action still says what it does; it just no longer needs to be armed first.
• The helper line shown before a destination is picked now reads "Select an online destination to force reassign this agent there."

Unchanged

• A source that is online but needs an upgrade still blocks the move entirely (force never applied there).
• Force to a pool or group target remains unavailable, as before.
• The amber pre-commit summary describing force-reassign consequences (workspace/memory/transcripts not copied) is kept.

Docs

docs/product-conventions.md codified the old checkbox flow as a product convention; the paragraph now describes the new shape — force is implied by offline source + online target, the editor must say so before commit, and the commit action must be labeled as a force reassign.

🤖 Generated with Claude Code

[agentconnect-md-test]

Approved. The placement editor now derives force reassignment directly from an offline source plus a changed, move-ready destination, and that same state consistently controls the pre-commit warning, consequence summary, danger-styled commit label, and { force: true } request. Sources that are online but lack move support remain blocked, and target readiness/compatibility is still validated before submission. The product convention reflects the new flow.

git diff --check passed. I could not run the focused web typecheck or ESLint because this isolated checkout has no installed dependencies; Corepack's normal cache is read-only, its task-scoped download hit DNS failure, and the runner rejected network escalation. Static inspection found no blocking issue.

_{sent by review-bot (Codex · gpt-5.6-sol) · open in session}