fix(binjovi): authorize onboarded status writes #124

Merged

binjovi-bot merged 1 commit from fix/binjovi-write-scope-onboarding into trunk

2026-09-01 09:01:08 +00:00

sean commented

2026-09-01 08:49:41 +00:00

Owner

Cause

The Binjovi project catalog and status dispatcher are correct. n8n and BuildKit have repository collaborator grants, but the short-lived Forgejo authorized integration omits their repository IDs. Forgejo therefore refuses status writes while Builds can still finish and remain selectable.

The status dispatcher completes an outbox effect only after Forgejo accepts the write. Its 30-second repair loop will retry the pending effects after this scope repair deploys.

Fix

authorize n8n, BuildKit, argo-workflows, Athens, Gibson, and pkg-host in authorized_integ_resource_repo
bump the rerunnable bootstrap Job to binjovi-forgejo-integration-v14
require every repository with a binjovi-bot collaborator grant to be resolved, bound, and present in the integration scope

Red-green evidence

Red: bash tests/binjovi.sh failed with FAIL: Binjovi write integration does not resolve argo-workflows.

Green:

bash tests/binjovi.sh
kustomize build kubernetes/flux/infrastructure/binjovi
bash tests/check.sh
git diff --check

No imperative cluster action is required. Merge and deploy this repair before retrying the n8n and BuildKit release batch.

## Cause The Binjovi project catalog and status dispatcher are correct. n8n and BuildKit have repository collaborator grants, but the short-lived Forgejo authorized integration omits their repository IDs. Forgejo therefore refuses status writes while Builds can still finish and remain selectable. The status dispatcher completes an outbox effect only after Forgejo accepts the write. Its 30-second repair loop will retry the pending effects after this scope repair deploys. ## Fix - authorize n8n, BuildKit, argo-workflows, Athens, Gibson, and pkg-host in `authorized_integ_resource_repo` - bump the rerunnable bootstrap Job to `binjovi-forgejo-integration-v14` - require every repository with a `binjovi-bot` collaborator grant to be resolved, bound, and present in the integration scope ## Red-green evidence Red: `bash tests/binjovi.sh` failed with `FAIL: Binjovi write integration does not resolve argo-workflows`. Green: - `bash tests/binjovi.sh` - `kustomize build kubernetes/flux/infrastructure/binjovi` - `bash tests/check.sh` - `git diff --check` No imperative cluster action is required. Merge and deploy this repair before retrying the n8n and BuildKit release batch.

sean added 1 commit

2026-09-01 08:49:41 +00:00