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
Completes the request path for FLUID-WP-0003 T01-T03 and T05-T07. The
gateway resolves a revision, routes to the adapter process, and records
what happened, without ever depending on the control plane to serve.
Three behaviours carry tests because the architecture rests on them:
Emit never blocks against a stalled sink (Blueprint 34.2), the gateway
keeps serving after control-plane loss (invariant 2), and backend
internals do not leak into error responses (5.7).
The connector retries only idempotent methods, so a slow adapter cannot
cause a hall-of-helix entry to be published twice, and breakers are
per-revision so a broken candidate does not take the stable revision
down with it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
