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

pressure/P-register-mismatch.yaml

@@ -1,45 +0,0 @@
-# Seed pressure record.
-#
-# Measured directly rather than observed from telemetry. The intent (section 13)
-# permits a structural constraint to found a hypothesis without waiting for
-# repetition, and this one is structural: it is a property of what a hall entry
-# is, not of how anyone has used the interface.
-fluid_pressure:
-  schema_version: "0.1"
-
-  id: "P-register"
-  interface_id: "helix-forge-telegram-publishing"
-
-  class: "repeated_expectation_mismatch"
-
-  first_seen: "2026-09-04T00:00:00Z"
-  last_seen: "2026-09-04T00:00:00Z"
-
-  affected_cohorts:
-    - "telegram-subscribers"
-
-  frequency:
-    observations: 94
-    independent_consumers: 1
-
-  severity: 0.8
-  confidence: 1.0
-
-  summary: >
-    A hall-of-helix entry is written for a colleague reading a repository: a
-    considered first-person account under fixed headings, median body 5767
-    characters, with 80 of 94 entries exceeding Telegram's 4096-character
-    single-message limit. A channel post reaches a stranger scrolling. These
-    are different pieces of writing for different readers, and publishing the
-    first as the second serves neither. The length figures are the visible
-    symptom; the mismatch is one of register and audience, and it would remain
-    if the limit were ten times larger.
-
-  evidence_refs:
-    - "measurement:hall-of-helix/entries@2026-09-04"
-    - "canon:fluid-telegram/TelegramCapabilityCanon.md#PUB-02"
-
-  status: "ANALYZING"
-
-  linked_hypotheses:
-    - "H-tg-visual"