`runique start`

On startup, runique start reads src/main.rs and looks for the presence of .with_admin(:

// src/main.rs
RuniqueApp::builder(config)
    .with_admin(|a| a.routes(admins::routes("/admin")))
    // ...

Detection is done by simple string search in the source file. It works even if the line is commented out (// .with_admin(...)).

The path to main.rs is configurable: runique start --main src/main.rs

runique start runs, in order, on the same thread:

1. Generation — reads src/admin.rs, parses admin!{}, rewrites src/admins/
2. cargo fmt --all
3. cargo run --release — blocking until program exit

runique start
  ├── generate_admin(src/admin.rs) → rewrites src/admins/
  ├── cargo fmt --all
  └── cargo run --release          → HTTP server (blocking)

An earlier design ran generation on a separate thread in parallel with cargo run: this created a race condition (the build could pick up a half-written admin.rs, failing unreproducibly). The flow is now strictly sequential to eliminate that. There is no continuous watching: to regenerate after changing src/admin.rs, run runique start again.