ci(release): finish the setup for the automated acceptance run after TestPyPI #1137

Summary

The acceptance job in publish-testpypi.yml (#1082, #1086) has never dispatched a run. On the 0.1.3 TestPyPI publish (run 38414583544) the job passed, but the acceptance (published) status on 30ad20f2 reads error: Not run: set ACCEPTANCE_REPO and ACCEPTANCE_DISPATCH_TOKEN (docs/releasing.md). The 0.1.3 acceptance run was done by hand instead (./run.sh --version 0.1.3 --index testpypi, passed).

Where

Three of the prerequisites in docs/releasing.md ("For the automated acceptance run") are missing:

• ACCEPTANCE_REPO repository variable is unset on this repo. It should be Donkey-Development-Kit/donkey-development-kit-acceptance.
• ACCEPTANCE_DISPATCH_TOKEN repository secret is unset. A fine-grained token scoped to the acceptance repository only, with Actions: read and write.
• published-gate.yml is not on the acceptance repo's default branch. main has no .github/workflows/published-gate.yml (only develop does), and GitHub rejects a workflow_dispatch for a workflow that isn't on the default branch.

Done when

• The next publish-testpypi.yml run dispatches published-gate.yml, and the acceptance (published) status on the release commit is success or failure, not error: Not run.

Notes

• The job's own conclusion is success even when it posts the error status, so the Actions run reads green. The status on the commit is the real signal, and the promotion PR shows it.
• The token and secret are a maintainer task (an org admin creates the fine-grained token).

Cross-surface impact

• core/llm/registry/tools/integrations: not affected
• TypeScript parity (planned): not affected
• Provisioning CLI: not affected
• Nextra docs site: not affected
• docs/verified-apis.md: not affected
• -acceptance repo: published-gate.yml needs to reach main