project init uses brokerd launch directory for repository identity

[VladimirBrejcha]

Problem

With a healthy resident brokerd launched from one directory, running the documented newcomer flow from a different fresh repository writes the project file in the caller repository but can derive repoRoot, the default project name, and the default project ID from the daemon launch directory.

Reproduction

1. Start brokerd with disposable host and state paths from directory A.
2. Create and enter fresh repository B.
3. Run simbroker project init without path flags.
4. Inspect the response and the known-project registration.

The file is written under B, while project identity can describe A.

Expected

The CLI resolves both the project file and repository root from caller context before direct or service-backed dispatch. The daemon launch directory must not influence project identity. Repeated init should return a recovery command for B, and the next capacity check should discover the new project ID while retaining public path redaction.

Safety and acceptance

Use only temporary broker state, sockets, host configuration, and simulated inventory. Cover direct and resident-service behavior, explicit aligned path flags, repeat init, and the following capacity lookup.