Groove SPEC §8.1 discovery panel (AffineScript) + frozen-backend dialect keep-alive

[hyperpolymath]

Summary

Phase 2 of the joinery program (standards#252-adjacent estate line; follows the merged Phase-1 set: cleave#4, groove#6, burble#153, gossamer#104, spline#4, standards#478). PanLL gains the discovery panel groove SPEC §8.1 asks for — authored in AffineScript per the 2026-07-09 estate ruling (new panels are AffineScript, not ReScript) — and the frozen-legacy backend gets the minimal wire-dialect keep-alive patch approved after a PMI review.

Changes

• src/ui/tea/groove_discovery.affine (new): the SPEC §8.1 discovery UI — discovered systems, active connections with lease modes (SPEC v0.3 §4.6), mesh topology, hash-linked attestation chain — in the sibling .affine TEA idiom (linear Model/Msg, list-consuming refreshes so stale rows cannot survive a transition). Authored-canonical, awaiting toolchain, like the other 17 .affine modules: the ReScript chain deliberately gains no new panel wiring; the runnable form today is groove/harness/groove-panel-template/panel.html against a live provider.
• src-gossamer/src/groove.rs (frozen-legacy keep-alive, constants + manifest string only):
  • manifest gains "mode":"active" (SPEC §2.1.1); feedback capability retyped to the registered dogfood-feedback; health-mesh type now registered in groove-registry (groove-repo PR pairs with this one)
  • MESH_PROBE_PORTS [6473, 8080, 8081, 8091-8093] probed a moved service (verisimdb → 6475) and three unmapped ports — the mesh view was factually wrong. Now the registry's groove-discovery surfaces [6465, 6470, 6473, 6475, 6480, 9000, 9090] (two-plane rule: app-plane URLs like VeriSimDB's :8080 API are deliberately unchanged)
  • stale Tauri comment corrected to Gossamer
• src-gossamer/STATUS.adoc: records the owner decision (2026-07-09, after a PMI review) that wire-dialect keep-alive is a permitted change class — so this question never needs re-litigating at a dialect bump.
• HISTORICAL banners on GROOVE_PANLL_RESEARCH_SUMMARY.md and TRANSMUTABLE_PANEL_ARCHITECTURE.md (2024 Mistral-Vibe era; superseded-by pointers to the joinery canon; kept for provenance, never deleted).

RSR Quality Checklist

Required

• Tests pass — no runtime code path changed that local tooling can exercise; .affine modules await the toolchain (same status as the existing 17); groove.rs is constants/manifest-string only
• Code is formatted (matches sibling idiom)
• Linter is clean
• No banned language patterns (panel is AffineScript per estate ruling — no new ReScript/TS)
• No unsafe blocks
• No banned functions
• SPDX license headers present on new files (MPL-2.0)
• No secrets or credentials

As Applicable

• Documentation updated (HISTORICAL banners; STATUS.adoc policy line)
• .machine_readable/STATE.a2ml — unchanged (panel activates with the AffineScript toolchain or panel-clades; flagged below)

Testing

• Runnable §8.1 verification path: browser harness (groove/harness/groove-panel-template/panel.html) against a live reference provider (cargo run -p groove-provider) — the harness now hashes attestations with real WebCrypto SHA-256 (groove-repo PR).
• groove.rs changes are constants + a static string; the frozen backend's build is keep-alive-covered by its existing CI.

Flags for the owner

• The panel's PanLL-native activation lands with the AffineScript build path (or panel-clades, whichever first — the latter still gated on the Axiom.jl decision).
• The paired groove-repo PR registers health-mesh and carries PROOFS-1 + signing vectors; merge order is flexible (nothing here breaks without it — the type is only validated repo-side there).

🤖 Generated with Claude Code

https://claude.ai/code/session_01ECjSL2nqzn3qJEzA28V4m5

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud