docs/BUILDER_PATH_AND_MANIFEST_AUTO_CAPTURE.md

# Builder path and manifest auto-capture

`BUILD-USB.cmd` and `TEST-WITHOUT-USB.cmd` must be executed from inside the extracted JackAILocal Builder folder.

They must not be copied alone to the target USB key.

Correct structure:

```text
JackAILocal-Builder-v12/
├── BUILD-USB.cmd
├── TEST-WITHOUT-USB.cmd
├── client-builder/
│   └── windows/
│       └── JackAILocal-USB-Builder.ps1
├── manifest-input/
├── webui/
├── config/
└── windows/
```

The builder automatically looks for Gradio-generated build manifests in:

1. The extracted builder folder.
2. `manifest-input/` inside the extracted builder folder.
3. The user's `Downloads` folder.

Expected filename pattern:

```text
jackailocal-build-manifest-*.zip
```

The user does not extract the manifest ZIP. The builder reads it directly.

After the target USB/SSD is built, the customer only uses:

```text
START-HERE.cmd
```

The target USB does not need the `client-builder/` folder.