/**
 * Application Scaffolder (output port)
 *
 * Produces a ready-to-code project tree at a given repository path so
 * the agent's first turn starts on a flat, dependency-installed,
 * theme-ready project — no `bunx shadcn init`, no flatten gymnastics,
 * no package-manager bootstrap inside an agent turn.
 *
 * The port is deliberately narrow and presentation-agnostic:
 *   - No Node types (`fs`, `ChildProcess`, `URL`) leak into the
 *     signature — the use-case that depends on this port must remain
 *     runnable in any environment where a `ScaffoldResult` can be
 *     produced.
 *   - No bash strings, no package-manager names, no template paths —
 *     those are infrastructure concerns owned by the adapter.
 *
 * Adapters live in `infrastructure/services/scaffolding/`.
 *
 * @see `CreateApplicationUseCase` for the single caller.
 */
export {};
