feat(catalog): register the rpg-lemonade-tng and rpg-munchers-tng twins #313

Merged
binjovi-bot merged 1 commit from feat/rpg-twins-registration into trunk 2026-09-14 12:35:45 +00:00
Owner

Register the rpg-lemonade-tng and rpg-munchers-tng twins

The twins recover rpg-lemonade and rpg-munchers from the routine source loss those deploys apply, through the same ibmi-rpg pipeline (same images, libraries and pub400-rpg target). seanfarm's onboarding (PR #729) and binjovi's allowlist change (v0.1.735) are live.

  • bundle.json: two v20 entries cloned from the originals; repository, authority prefix and recipe config renamed; projects stay sorted.
  • recipes/rpg-*-tng/recipe.json: the original recipes with the twin's name and save file (LEMTNGSF, MUNTNGSF); same scenarios so the reels compare; no loss_profile.
  • recipes/ibmi-rpg/artifacts allowlist and manifest regexes, and the Dockerfile source stages, admit both names.
  • object-store.json: candidates, media, staging and release resources plus the 30-day candidate expiry for both.
  • scripts/check loops and the five-name set; README and the browser reel test list six rpg projects.

Local: scripts/check passes (with make format); tests/object-store-test passes; test-artifacts needs the cluster-only binjovi-package-stage binary and fails identically on trunk here.

https://claude.ai/code/session_01HPdKaFBKQVs8hzfgXMrnwV

## Register the rpg-lemonade-tng and rpg-munchers-tng twins The twins recover rpg-lemonade and rpg-munchers from the routine source loss those deploys apply, through the same ibmi-rpg pipeline (same images, libraries and `pub400-rpg` target). seanfarm's onboarding (PR #729) and binjovi's allowlist change (v0.1.735) are live. - `bundle.json`: two v20 entries cloned from the originals; repository, authority prefix and recipe config renamed; projects stay sorted. - `recipes/rpg-*-tng/recipe.json`: the original recipes with the twin's name and save file (`LEMTNGSF`, `MUNTNGSF`); same scenarios so the reels compare; no `loss_profile`. - `recipes/ibmi-rpg/artifacts` allowlist and manifest regexes, and the Dockerfile source stages, admit both names. - `object-store.json`: candidates, media, staging and release resources plus the 30-day candidate expiry for both. - `scripts/check` loops and the five-name set; README and the browser reel test list six rpg projects. Local: `scripts/check` passes (with `make format`); `tests/object-store-test` passes; `test-artifacts` needs the cluster-only `binjovi-package-stage` binary and fails identically on trunk here. https://claude.ai/code/session_01HPdKaFBKQVs8hzfgXMrnwV
feat(catalog): register the rpg-lemonade-tng and rpg-munchers-tng twins
Some checks failed
binjovi/ci Binjovi will not build this: its base branch must be trunk. Retarget the pull request.
be90e4b54a
The twins recover rpg-lemonade and rpg-munchers from the routine source
loss those deploys apply, and they build, release and deploy through the
same ibmi-rpg pipeline: the same worker, publisher and render images,
the same libraries, the same pub400-rpg target.

- bundle.json: two v20 entries cloned from their originals (repository,
  authority prefix and recipe config renamed; the projects stay sorted).
- recipes/rpg-lemonade-tng and recipes/rpg-munchers-tng: the original
  recipes with the twin's project name and its own save file (LEMTNGSF,
  MUNTNGSF); the same scenarios, so the reels compare; no loss_profile,
  a twin never breaks anything.
- recipes/ibmi-rpg: the artifacts allowlist and both manifest regexes,
  and the Dockerfile's source stages, admit both names.
- object-store.json: candidates, media, staging and release resources
  and the 30-day candidate expiry for both.
- scripts/check: the rpg recipe loops and the name set (five projects);
  README and the browser reel test list the six rpg projects.

Claude-Session: https://claude.ai/code/session_01HPdKaFBKQVs8hzfgXMrnwV
binjovi-bot deleted branch feat/rpg-twins-registration 2026-09-14 12:35:46 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/binjovi-plans!313
No description provided.