Go-Sphere Makefiles

Keep go-sphere repositories consistent at their public Make target boundary without forcing their internal build graphs to be identical.

Desired Contract

Every Go repository should expose these common targets when they apply:

• deps-update: update direct, non-replaced dependencies and tidy the module.
• tidy: tidy without depending on a surrounding workspace.
• fmt: apply repository-owned formatting.
• test: run the repository's complete default test path.
• lint: run non-mutating formatting checks and applicable analyzers.
• check: perform the normal non-release green gate.

Repositories may retain build, verify, generation, compatibility, release, benchmark, deployment, or other specialized targets. Do not delete or flatten them merely to make files look identical.

Inspect Before Editing