chore(release): realign develop with main after the #673 promotion

[beyondnetPeru]

Pull Request Summary

Sync-back after the #673 promotion. Zero file changes — git diff develop..main is empty. The single commit is the merge node GitHub created on main when #673 landed.

Without it, develop sits one commit behind main and every branch cut from it starts behind too. This is phase 2 of the pre-push release macro, done as a PR because develop is protected — the same step as #671 and as db596547 before it.

With this merged, both branches of this repository converge and the BeyondNetCode organisation is fully in sync: beyondnetcode/ums already has main and develop on the same commit, with no divergence in either direction.

Before you submit

• Sign-off (DCO): the only commit is a GitHub-generated merge node; there is nothing authored here to sign.
• Conventional Commits: title follows the convention, matching chore(release): realign develop with main after the #670 promotion #671 and db596547.
• Agnosticism: no content change at all.
• Bilingual: no documents touched.

Linked ADRs / Issues

• Follows #673 (promotion that repaired the agent-runtime image build)
• Precedents: chore(release): realign develop with main after the #670 promotion #671 after chore(release): promote develop to main — security hardening, audited ADRs and two guards that stopped lying #670, db596547 after chore(repo): pin Node at the root, and drop a Sponsor button that leads nowhere #637

What the reviewer should know

Nothing here changes a line, so any red check belongs to the branch state rather than to this change — the case the PR template calls "ours, not yours".

One thing worth noting for the next cycle: this is the third realignment PR in a row, because every promotion leaves develop one merge node behind. The pre-push macro was written to do both phases in one go, but branch protection on develop and main means the push path it takes cannot apply here. Either the macro learns to open PRs, or these follow-ups stay manual — worth choosing on purpose.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[github-actions]

📊 Bilingual Coverage Impact

PR Changes

• Paired EN/ES files modified: 0
• New EN files needing ES translation: 0

Repository Coverage

Metric	Value
Total EN files	527
Total ES files	497
Paired files	0
Coverage	0%

✅ Good: All EN changes have ES counterparts.

---

Generated by GitHub Actions

[beyondnetPeru]

Superseded by #677: the promotion from develop carries the real fix for the agent-runtime image build (mkdir -p .harness/bin — the destination directory is gitignored and absent on a clean checkout), so main will be repaired directly rather than synced back from a main that still cannot build.

The red Build & Push Services (GHCR) check on this PR was TRUE about main, not stale — which is why it was not merged. A fresh sync-back will follow #677.