Skip to content

ci: upstream-sync workflow + ZAP duplex port 9999#1

Merged
hanzo-dev merged 3 commits into
mainfrom
feat/upstream-sync
Apr 27, 2026
Merged

ci: upstream-sync workflow + ZAP duplex port 9999#1
hanzo-dev merged 3 commits into
mainfrom
feat/upstream-sync

Conversation

@hanzo-dev
Copy link
Copy Markdown
Member

Adds upstream-sync GitHub Actions workflow + ZAP port standardization. Branch cut from origin/main.

ZAP binary protocol duplex RPC standardizes on :9999 across every
service. Lux validator staking/RPC ports (9630/9631 mainnet, 9650/9651
devnet) are unchanged — those are luxd network protocol ports, not ZAP.

One ZAP port everywhere (was a mix of 9651/9652/9653/9633/9900).
Periodic sync from just-every/code (the canonical upstream Hanzo dev tracks).
Every 6h: fetches upstream, attempts merge, opens PR with automerge label
if clean, otherwise opens an issue listing conflicting paths. Bot does not
resolve content conflicts.
- delete upstream-merge.yml (1106 lines, auto-merge, polled every 30 min)
  in favour of single upstream-sync workflow
- upstream points to openai/codex (matches LLM.md), not just-every/code
- weekly cron Mon 06:00 UTC (was every 6h)
- branch named upstream-sync/<UTC-date>
- always opens draft PR, never auto-merges
- on conflict, commits markers in place and opens draft PR labelled conflict
  so the branch is checkoutable for human resolution
- LLM.md documents the new flow

One way: there is now exactly one upstream-sync entry point.
@hanzo-dev hanzo-dev merged commit 649d0fe into main Apr 27, 2026
2 of 5 checks passed
@hanzo-dev hanzo-dev deleted the feat/upstream-sync branch April 27, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant