init verb

init: one command from a project to a wired AI client

Registers a project, indexes it and points Claude Code, VS Code and Cursor at its index, so an AI client can query it straight away. The verb is drag-lint init; it adds no logic of its own, it runs four existing verbs in order.

Running it

drag-lint init --project C:\Projects\MyApp\MyApp.dproj --dry-run   (print the four commands, run nothing)
drag-lint init --project C:\Projects\MyApp\MyApp.dproj

The four steps

1. register-project <proj> --apply -- adds the project's section to the manifest (a no-op when it is already registered).
2. index --project <proj> -- builds the project's index.
3. resolve-dbs --project <proj> -- finds the index that owns the project.
4. mcp-config --all --db <that index> -- writes the MCP entry for Claude Code, VS Code and Cursor (Register the MCP server); a client that is not installed is skipped.

Each step's output is echoed under a step n/4 heading. A failing step stops the run and its exit code is the verb's (a step that could not start, or timed out after an hour, is 1). Every step is safe to repeat, so a second init changes nothing.

Flags

• --project <file.dproj> -- required; the project file must exist (usage error, exit 2, otherwise).
• --dry-run -- prints the four commands and runs none of them: nothing is registered, indexed or written.
• --home-dir <dir> / --appdata-dir <dir> -- passed to step 4: where the client files are looked for (used by tests; the defaults are your user profile and %APPDATA%).

Tests: tests\autotest\run_init_verb.ps1 (scratch engine copy and scratch home; it asserts the real client files are unchanged).