Close FLUID-WP-0001: fill bootstrap files and document the toolchain

Replace the generated credential-routing placeholder and generic purpose
text with repo facts, record the install/test/lint/build/run commands in
AGENTS.md, and point T03 at the existing FLUID-WP-0002…0009 sequence
instead of seeding a duplicate workplan.

Assistant: grok
Assistant-Session: 01a09dc6-3f0e-78f1-a884-c8b2daa3e2b6

SCOPE.md

@@ -23,8 +23,8 @@ no library, and may be written in any stack.
 
 **The deterministic data plane** — gateway, revision resolver, revision router,
 contract validation, backend connectors, response policy, telemetry emission.
-`cmd/fluid-gateway`, `internal/runtime`, `internal/contract`, `internal/validate`,
-`internal/policy`.
+`internal/runtime` (the gateway is a library; `cmd/fluid-gateway` is reserved
+and empty), `internal/contract`, `internal/validate`, `internal/policy`.
 
 **The observation plane** — telemetry ingest, redaction, cohorts, interaction
 topology, pressure classification. `internal/observation`.
@@ -103,8 +103,10 @@ second interface goes from empty capability canon to a published R-1
 (`FLUID-WP-0009` T05), claims of generality are untested. That test is the point
 of the workplan, and its findings are expected to be uncomfortable.
 
-Registered with the Custodian State Hub: domain `infotech`, topic `helix-forge`,
-workplan prefix `FLUID-WP-`.
+Registered with the Custodian State Hub: domain `infotech`, repo topic
+`helix-forge`, workplan prefix `FLUID-WP-`. Workplan records currently index
+under the custodian topic; query by repo (`0f681685-7bc0-41b9-97fb-50073ebf6cf4`)
+rather than by helix-forge.
 
 ## Getting Oriented