This draft covers failures visible in the current account, Dashboard, project, and invitation flows. Installer-specific requirements and recovery steps still need verification against a current packaged release.
Do not guess from website copy. Record the operating system/version, Misaki build/version, distribution source, exact system message, and whether the app ever opened. Confirm you are using a current trusted build, then report the failure with those facts. Do not disable operating-system protections as a generic fix.
Complete the required sign-in fields and submit again. If the values are present but the same validation remains, record the active form and screenshot because the field state may not have committed.
The MCP server did not resolve a local profile. Sign in through the desktop app on the same machine and profile/data directory, then reconnect the MCP client and call list-projects again.
Use a name beginning with a letter and containing only the characters accepted by the visible form. File and project validation are related but not identical, so keep the full message and the surface that produced it.
Choose another name. Project names must be unique within the current user's projects.
Return to the Dashboard and try once more after confirming connectivity and the intended profile. If it repeats, do not create a replacement project with the same intended content; record the project identity and investigate its local/remote availability first.
“Profile not found.” — the email does not resolve to an existing account; the person must sign up first.
“Can not invites project your self.” — the entered email is the current owner's account.
“User all ready invited.” — access already exists.
“User invited successful” — the invitation was accepted by the service; verify it appears for the intended user/project.
Removing or leaving changes access, not existing content history.