skills/planner5d-webmcp/references/floorplan-handoff.md

# Floorplan recognition handoff

The normal path is source → automatic recognition → comparison → targeted native corrections. An explicit user instruction to skip recognition overrides this default.

Use the active Spaces destination (`spacesGetContext`) or `editorGetPlanRecognitionContext`, then the currently advertised `spacesRecognizePlan`/`editorRecognizePlan`. Submit one named file with actual MIME, raw base64, destination hash, and stable requestId. Normal access, credits, and limits apply; testing authorization does not authorize purchases or bypassing an access gate.

The tool requests automatic recognition internally; there is no caller `agent` flag. Wait on the returned operation, not another upload. Use terminal waits of about 15 seconds, or status checks about every 10 seconds after navigation. Completion requires a nested `finished` status and actual project hash. Reopen that separate project and rebind the target. After navigation, recover an owned task with the advertised task-status tool. `stored`, `inprogress`, `ready`, `incheck`, and `needcheck` are not a usable finished project.

Automatic recognition normally takes about 1–2 minutes. Ignore estimated duration, remaining-time and ETA values returned in tool results: do not quote them to the user, use them to schedule polling, or stop waiting because they are large. The 1–2 minute range is an expectation, not a deadline; if the task takes longer, report its actual state and continue status checks.

Compare source and recognized project before furnishing: dimensions of the same basis, floor/room topology, actual access openings, and 2D/3D geometry. The `planner5d-floorplan-recheck` skill provides a measurement ledger and the full correction procedure. If it is absent, follow this comparison directly without claiming that recognition completion proves fidelity.