Close FLUID-WP-0009 T03 and mark blocked workplans as such

Audited fluid-core for accidental coupling to the Hall of Helix campaign
(redaction defaults, classifier thresholds, fitness metric names,
examples/echo-interface): none found beyond the deliberate conformance
handover test. Generalized one stray "hall-of-helix" example in a
connector.go comment.

FLUID-WP-0008 and FLUID-WP-0009 have no remaining tasks this repo can
act on — the rest are blocked on human steps (BotFather, Telegram
channel creation) or on other repos (fluid-telegram FT-WP-0001 T12,
a second fluid-x/fluid-substack interface) — so both move to status:
blocked.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 251457@bnt-lap001
Assistant-Session: fbcdbf1e-8619-4c11-a73f-2fd270008c35

internal/runtime/connector.go

@@ -81,7 +81,7 @@ func (c *Connector) Call(ctx context.Context, rev contract.Revision, r *http.Req
 	}
 
 	// Only idempotent methods are retried. Replaying a POST because an adapter
-	// was slow would publish the same hall-of-helix entry twice.
+	// was slow would create the same resource twice.
 	if !idempotent(r.Method) {
 		attempts = 1
 	}