suede-graph-flo-xr

# Suede Graph Flo XR Use the bundled `workflows/suede-graph-flo-xr.js` workflow to search competing plans for one multi-file repository change. It makes an evidence-backed selection before any implementation lane mutates the worktree. ## Intake and budget gate Before launch, require all three inputs: - **Repo** — an absolute repository path. Relative paths and `~` fail closed. - **Scope** — the requested multi-file change, including any protected paths or constraints. - **Budget** — `light`, `standard`, or `deep`. Also detect and pass optional context when available: `deploys` (whether the repo has a deploy surface), `liveUrl` (the read-only production surface), and `vault` (the external decision/handoff context path). Their absence does not block a non-deploying repository, but do not silently discard known values. When the user names a model for the workers (`workerModel`: `sonnet`, `opus`, `haiku`, or `fable`), pass it — every worker call then runs on that model while orchestration stays on the session model. Omitted, workers inherit the session model silently; if the session sits on an expensive model and the user did not choose it for workers, say so before launch instead of letting the default decide. A run can spend up to 200 worker calls, so an unchosen inherited model is a cost decision nobody made. If repo or scope is missing, halt. Report the missing input in one line, offer to provide the repo path, describe the desired change, or route a one-file edit to...