hiiu init

hiiu init [path]
hiiu init --yes [path]

The onboarding command. It runs the whole sequence: analyse, propose, confirm, build, verify.

Arguments and flags #

[path]	The repo or app directory to set up. Default .

No command-specific flags. Every global flag applies, and --yes is the one that matters here.

It shows you the facts before it asks anything #

The facts about your repository and the proposed configuration print before any question. Correct facts about your own repo are the moment hiiu earns the right to ask for a decision, so it never asks first.

In a terminal the ask is one confirm. Everywhere else the non-interactive rule decides: --yes accepts the proposal and proceeds, and no --yes outside a terminal is exit 3 immediately rather than a hang.

The crawl is a loop, not a pass #

After the build it crawls, and every refused request is treated as a missing endpoint. Those feed back as sightings, a rebuild infers them into the contract, the world grows what serves them, and the re-crawl measures whether the gap closed.

The loop is bounded at three rounds. Round one discovers what the contract missed, round two proves the inference closed it, and a third round still finding new gaps means the app mints requests faster than templates collapse them. That is a report for a human rather than a reason to keep going.

What v0 does not do #

Named rather than implied:

• It does not prompt per decision. Accepting a proposal wholesale is not the same as answering its questions, so the persona stays unset and the manifest records decisionsConfirmed: false.
• It does not open a browser tab, despite the summary line saying so. There is no served surface to open yet. It names the next command instead.

Exit codes #

Code	When
0	Analysed, built and verified
3	Not a supported app, or it needed an answer and could not ask
4	The app failed to build
5	A route did not render, or gaps remained after the last round

Example #

hiiu init --yes ./apps/web