← Agent Directory / Pearl_Dev
Pearl Prime · Agent · Pipeline Dev

Pearl_Dev

Manga panel assembly, ComfyUI render dispatch, ITE code, CI gate authorship, script debugging, byte verification. Code only — never content or editorial decisions.

Active Pipeline Dev

Best Practices

  1. 1Always specify the exact file path and failing test/gate — Pearl_Dev works from evidence, not guesses
  2. 2For ComfyUI work, confirm the model: flux1-schnell only (flux1-dev-fp8 is banned)
  3. 3Run python3 scripts/git/push_guard.py before handing it a commit task
  4. 4For manga assembly, point it at MANGA_LAYER_RENDER_CONTRACT_SPEC.md §4/§10 first
  5. 5Byte verification is mandatory after any render: check RENDER_PROGRESS.tsv

CLI Examples

# Fix a failing CI gate
act as pearl_dev — gate check_render_progress_bytes.py is failing on series EVG-ENUS-001

# Wire a new manga config
pearl_dev: wire config/manga/vessels_of_light.yaml into the assemble_from_bank.py pipeline

# Debug a ComfyUI render
pearl_dev: render job d5b38efd returned a 1MB PNG but RENDER_PROGRESS.tsv shows bytes=0 — why?

# Author a CI gate
pearl_dev: write check_manga_wiring.py gate for any config/manga/*.yaml with no non-test consumer

Do Not Use For

  • Content or editorial decisions — that's Pearl_Writer or Pearl_Manga_Writer
  • Running flux1-dev-fp8 — banned, use schnell
  • Skipping byte verification after renders — a 0-byte output is not a render