docs: point Groove protocol refs at hyperpolymath/groove-protocol (#93)

Companion to hyperpolymath/standards#228 —
Groove Protocol was extracted from `standards/groove-protocol/` into a
top-level repo `hyperpolymath/groove-protocol` 2026-05-28 (matches SNIFs
/ typed-wasm precedent for named-boundary tools).

## Files updated

- `UNIFIED-ZIG-API-STACK.adoc` — 2 references
- `zig-ecosystem/connectors/zig-groove-bridge/README.adoc` — 1 reference
- `zig-ecosystem/connectors/zig-groove-bridge/src/main.zig` — 2
references
-
`zig-ecosystem/connectors/zig-groove-bridge/.machine_readable/6a2/ECOSYSTEM.a2ml`
— 1 reference

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

UNIFIED-ZIG-API-STACK.adoc

@@ -357,7 +357,7 @@ edge_mod.linkSystemLibrary("zig_api", .{});
   Import `ZigApi.ABI.Types` and `ZigApi.ABI.Connector` from `zig-api.ipkg`
   (add it as a dependency in the edge repo's `.ipkg`).  Extend, do not fork.
 . *Use the Groove protocol* for inter-service communication wherever possible
-  (see `standards/groove-protocol/`).  `zig-groove-bridge` in
+  (see `hyperpolymath/groove-protocol`).  `zig-groove-bridge` in
   `developer-ecosystem/zig-ecosystem/connectors/zig-groove-bridge/` is the
   reference consumer — study `src/main.zig` before writing your own discovery
   or attachment logic.
@@ -389,7 +389,7 @@ edge_mod.linkSystemLibrary("zig_api", .{});
 | `developer-ecosystem/bridge-nginx-zig/`
 
 | Groove protocol spec
-| `standards/groove-protocol/`
+| `hyperpolymath/groove-protocol` (GitHub)
 
 | rsr-template-repo
 | `hyperpolymath/rsr-template-repo` (GitHub)

zig-ecosystem/connectors/zig-groove-bridge/.machine_readable/6a2/ECOSYSTEM.a2ml

@@ -18,7 +18,7 @@ tier = "edge-protocol-layer"
 
 [related-projects]
 projects = [
-  { name = "standards/groove-protocol", relationship = "Groove protocol reference" },
+  { name = "hyperpolymath/groove-protocol", relationship = "Groove protocol reference" },
   { name = "developer-ecosystem/zig-api", relationship = "Will integrate as consumer of foundation" },
   { name = "gossamer", relationship = "potential Groove service consumer" },
   { name = "burble", relationship = "potential Groove service consumer" },

zig-ecosystem/connectors/zig-groove-bridge/README.adoc

@@ -96,7 +96,7 @@ To run integration tests meaningfully, one or more of these services should be r
 - **BoJ Server** (port 7700)
 - **ECHIDNA** (port 8081)
 
-Consult the Groove protocol reference at `standards/groove-protocol/` for service configuration.
+Consult the Groove protocol reference at `hyperpolymath/groove-protocol` (GitHub) for service configuration.
 
 == Architecture
 

zig-ecosystem/connectors/zig-groove-bridge/src/main.zig

@@ -8,7 +8,7 @@
 // across all 12 API types.  Attach to any Groove-aware service with a single
 // call; detach cleanly when done.
 //
-// Groove protocol reference: standards/groove-protocol/
+// Groove protocol reference: hyperpolymath/groove-protocol (GitHub)
 //
 // Usage:
 //   const bridge = @import("zig-groove-bridge");
@@ -85,7 +85,7 @@ const KnownService = struct {
 };
 
 /// Services the bridge probes first, before the open Groove discovery range.
-/// Derived from the canonical PORT-REGISTRY in standards/groove-protocol/.
+/// Derived from the canonical PORT-REGISTRY in hyperpolymath/groove-protocol.
 const KNOWN_SERVICES: []const KnownService = &.{
     .{ .name = "hypatia",    .port = 9090 },
     .{ .name = "stapeln",    .port = 4010 },