[antoinetoussaint-byte]

The first reusable-publisher dispatch failed at GHCR: run 38146017589 reported denied: installation not allowed to Write organization package. The job was defined in core, while this package grants Actions access to service-object-storage. Nothing was pushed or tagged.

• Hack — owner-approved STOPGAP pending core#770: restore this repository's own publishing job from fcd9d9e4~1:.github/workflows/publish-gateway-image.yml, which published 0.0.14. All five action SHA pins are unchanged. The real fix is core's composite action planned for 0.18.2; adopt it here and delete this copy once it ships.
• Fix — retain the review hardening: checkout uses persist-credentials: false and full history. The default-branch refusal shell is copied verbatim from core v0.18.1 and runs before login/build. Publication remains dispatch-only, with job-scoped package write permission, stable-version validation, two platforms and push by digest. Keep the current gateway-image.json-<version> artifact contract.
• Fix — keep tests and docs accurate: restore executable version-validation tests, exercise the refusal against real Git history (including a non-main default branch and a misleading tag), and read platform coverage from the restored build step. Update README.md, AGENTS.md and the image declaration comment with the stopgap and removal plan. Shellcheck's literal-Markdown warning is annotated at the existing summary echo.

All other #90 adoption remains: core v0.18.1, callertoken, strict image-lock parsing, shared evidence, and the CI/agent-release workflow pins.

Validation: actionlint passes; original action pins and exact upstream refusal text checked. go build ./..., go vet ./... and go mod tidy -diff pass. Focused workflow tests and go test -race ./... pass. CI run 38157329762 is green on aa0b5a8f37fd96d8577e69146216566f3f9790e7: all six jobs passed (build/vet/tidy, unit tests, race, MinIO + GCS-emulator integration, agent runtime e2e, and image SBOM). Live publication is deliberately unverified. The dispatch-only agent conformance suite and generated-workspace codefly ci run are not rerun for this workflow-only change; S3, real GCS/IAM and Azure are not exercised.

Coordinator release sequence after review and merge: codefly publish --dry-run (expect 0.0.15) → dispatch publish-gateway-image.yml on main with version=0.0.15 → commit its gateway-image.json-0.0.15 artifact as gateway-image.json in a reviewed PR → codefly publish patch. Do not publish the agent before adopting the new lock. This PR performs no merge, dispatch, publish or tag.

Refs #89.