The stranger install — download, run, onboarded

A released binary, dropped into a foreign repo, profiles it and installs the toolkit without a checkout.

The release pipeline embeds stories and skills into the cross-compiled binary and smokes it in a scratch git repo before shipping. A stranger downloads the release binary, runs `kitsoki` inside their own repo, and onboarding profiles the project, installs the agent toolkit, and registers the MCP server automatically — no source checkout, no manual setup step.

Question

Can a developer try Kitsoki without a source checkout?

Watch for

A released binary runs inside an existing repo and writes auditable setup.

Why it matters

The product path starts from the user repo, not from Kitsoki internals.

▶

demo video not rendered in this build make demo-feature FEATURE=stranger-install