Document: always run packaging in background (nohup/&)
BetterLeaks / scan (push) Successful in 54s

Packaging can exceed 900s timeout; must run as background job.
Added example command with nohup and log redirect.
This commit is contained in:
Dolon (Agent)
2026-03-24 22:00:01 +00:00
parent 4dc5bab471
commit e86492e900
2 changed files with 10 additions and 2 deletions
+3 -2
View File
@@ -59,8 +59,9 @@ Run **A-G** variants and **try each single up to 7 moderation rejects** before f
## Finalization and Packaging of one wealth tier (Poor, Modest, etc.) of Courtesans
**Tier-agnostic packager script:** `/home/rick/.openclaw/workspace/scripts/finalize_courtesan_tier.py`
- Example: `python3 scripts/finalize_courtesan_tier.py --tier Modest`
- Uses OpenCV for passport thumbnails; run with the OpenCV venv if needed: `~/.openclaw/workspace/.venv-opencv/bin/python scripts/finalize_courtesan_tier.py --tier Modest`
- Example: `nohup ~/.openclaw/workspace/.venv-opencv/bin/python scripts/finalize_courtesan_tier.py --tier Modest > logs/finalize_modest.log 2>&1 &`
- **Always run in background** (nohup/&) — packaging can exceed 900-second command timeout
- Uses OpenCV for passport thumbnails
Prerequisite: The human user has selected favorites across all dress stages and for each arrival lobby type (A-C), and possibly put some files into Topless Plus, with at most one image per courtesan scene. **Exception:** for **Topless / Topless Plus / Undressed**, multiple favorites are allowed if they are explicitly numbered with bracketed indices (e.g., `[1]`, `[2]`, `[3]`). The objective here is for the DM to be able to pick a courtesan (or courtesans) according to the player's wishes quickly at the table, and then open one image, and be able to progress through the scene narrative by just tapping the arrow-right button. This means that every courtesan (or courtesan double, or twins, or courtesan triple) need their own folder for that arrow-right to work. Coincidentally, the stages of undress come in alphabetical order, so naming the files from the stage-of-undress in a folder named from the courtesan will accomplish this goal by pressing arrow-right. Therefore, as ACTIONS, we create this folder structure under the respective Wealth Tier (Poor, Modest, etc): First, a new folder alongside the dress stages: "Per Courtesan". In that folder, we create up to four folders named exactly "Singles", "Doubles", "Triples", and "Twins" (according to if those exist in the wealth tier). Inside the Singles folder, we create -- per courtesan -- a folder with their name, exactly, spaces for underscores. No runhex or other decoration. If we know the scene setting, we add that in parentheses, like so: "Tilda Ashcroft (sauna)". Inside the Doubles folder, we create -- per courtesan pair and scene -- a folder with their names, exactly, spaces for underscores and comma-space between. Since we know the scene setting for doubles, we add that in parentheses, like so: "Tilda Ashcroft, Orla Brookmere (straw pallet)". Inside the Triples folder, we create -- per courtesan triplet and scene -- a folder analogous to the Doubles folder, with all three names. Example: "Brynhild Starweave, Gudrun Moonbraid, Idunn Stormlace (velvet divan)". Inside the Twins folder, we create per courtesan twin pair and scene a folder somewhat analogous to the Doubles folder, but since they share last name, it's going to be "Name1 and Name2 LastName (scene)". Example: "Freydis and Frida Highfrost (fire alcove)". These are the four first structures. Inside EACH FOLDER FOR COURTESAN(S), we COPY the respective dressed stage of that courtesan(s) and dress level. We start with Dressed, then Teasing, then Teasing More (with space, like that), then Topless. These files are called exactly that inside the named courtesan(s) folder: Dressed.jpg, Teasing.jpg, "Teasing More.jpg", et cetera. Then we have a logic gate. If the human user wanted "Underwear L" or "Underwear S" as the final stage, we copy that one file (named "Underwear L.jpg" or "Underwear S.jpg", and ignore the "Topless Plus" and "Undressed" (but Arrival still needs copying per below). If the human user wanted "Undressed" as the final stage, we check if there is a "Topless Plus" and copy that in as "Topless Plus.jpg", and then the respective "Undressed.jpg". Finally, we copy in the Arrival images. They are named "Arrival (Lobby type X).jpg" where X is the A to C. If there are stairs, the file is named "Arrival (Lobby type X, with stairs).jpg". It's okay if one particular lobby type doesn't exist as a file, just ignore it then. Same with other missing files. It'll still work.
**ArrivalAll packaging (tier root):** place the selected **ArrivalAll** overview images **directly in the tier folder** (same level as passport photos, not inside Per Courtesan). When tier has both genders, generate three sets and name packaged finals: `Arrival (Men, Lobby type A/B/C).jpg`, `Arrival (Ladies, Lobby type A/B/C).jpg`, `Arrival (All, Lobby type A/B/C).jpg`. Add `with stairs` suffix if applicable. The raw composites are generated as `ArrivalAllMen_A1-C6`, `ArrivalAllLadies_A1-C6`, `ArrivalAllSingles_A1-C6` (18 images each); human selects the best per letter.
+7
View File
@@ -256,6 +256,13 @@ Run automated preflight checks:
**Requires:**
- OpenCV venv: `~/.openclaw/workspace/.venv-opencv/bin/python`
**IMPORTANT:** Always run in background (nohup/&) — packaging can exceed 900-second command timeout.
**Example:**
```bash
nohup ~/.openclaw/workspace/.venv-opencv/bin/python scripts/finalize_courtesan_tier.py --tier Comfortable > logs/finalize_comfortable.log 2>&1 &
```
**Actions:**
1. Create **`Per Courtesan/`** folder structure (Singles/Doubles/Triples/Twins)
2. Copy stage files per courtesan/scene into named folders