chore: set the repository up as a meshStack go-satellite - #3
Open
grubmeshi wants to merge 1 commit into
Open
Conversation
The CLI itself is not written yet, but the machinery that builds and tests it can be proven first. A satellite has to carry a descriptor at its root, publish its unit coverage where meshfed-release will look for it, and ask that repository to run the acceptance suite against a real backend, because a whole meshStack cannot run in a public repository's CI. This is the smallest repository that does all three. Nothing here is usable yet: the binary prints one line and exits, and the acceptance suite only asks a local dev stack for /mesh/info. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes this repository a meshStack satellite before any CLI code lands, so the meshfed-release lane can be proven end to end: a
meshstack-satellite.gradle, the dispatch workflow, thecovdata-unitcoverage contract, and one acceptance test that asks the backend for/mesh/info.Paired by branch name with meshcloud/meshfed-release#11008, which registers this repository.
The
feature/cli-satellitepush trigger intest-acceptance.ymlis temporary and marked so:pull_request_targetreads that file from the base branch, andmaindoes not have it yet. Delete it before merging.