Ground the repo docs and move presence provisioning to a declared spec

Align AGENTS.md with the FT-WP- prefix the hub already registered, and
rewrite INTENT.md and SCOPE.md, which were still the generated stubs and
carried none of the composed-post framing the interface is built around.

Fix two artifact inconsistencies: R-1's retry comment still described
POST /v1/hall-entries idempotent on entry_id, from before the reframe to
composed posts; and the seed pressure record listed only one of the two
hypotheses that cite it. Rename it to match its id.

Replace the manual T01-T03 route with FT-WP-0002. The Bot API cannot
create a bot or a channel, so provisioning is an MTProto client acting as
a designated operator account (Canon INT-03), driven from a declared
presence spec owned by the campaign. One bounded human bootstrap remains
and docs/provisioning.md says why it cannot be removed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1361245@bnt-lap001
Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a

presence/telegram.example.yaml

@@ -0,0 +1,44 @@
+# Worked example of a declared presence.
+#
+# The real instance belongs in pr-hall-of-helix/presence/telegram.yaml — this
+# copy exists so the schema has something to be read against, and so the
+# provisioner's tests have a fixture. Keep it in sync with the schema, not with
+# the campaign.
+presence:
+  schema_version: "0.1"
+  campaign: "hall-of-helix"
+  interface: "helix-forge-telegram-publishing"
+
+  bot:
+    name: "HelixForge"
+    username_preference:
+      - "HelixForgeBot"
+      - "HelixForgePublishBot"
+      - "HelixForgeHallBot"
+    about: >-
+      Notes from the Hall of Helix — the people and sessions building HelixForge.
+    description: >-
+      HelixForge turns intent into structure, structure into capability, and
+      capability into lasting progress. This channel carries short accounts of
+      the work and the people doing it, each linking back to the entry it was
+      written from.
+    avatar: "presence/assets/helixforge-avatar.png"
+
+  channels:
+    test:
+      title: "HelixForge — test"
+      description: "Private rendering checks. Nothing here is published."
+      visibility: private
+      admin_rights: [post_messages]
+
+    public:
+      title: "Hall of Helix"
+      description: >-
+        Short notes on the work going into HelixForge, and the people doing it.
+      visibility: public
+      username_preference:
+        - "hallofhelix"
+        - "halloftheHelix"
+      admin_rights: [post_messages]
+
+  linked_discussion_group: false