Finish the provisioner's remaining plane: honest check, adapter config, IEI-2

plan --check treated BotFather profile reassertion as drift, so a scheduled
check could never go quiet. Reassertion is now its own kind; a changed spec
digest is the drift signal. apply reasserts the profile, updates channel copy
when the spec changes, and is tested against a fake Telegram surface.

The adapter reads its chat id from resolved state and its token from OpenBao,
never the operator session. IEI-2 records that an approved provisioning plan
is not autonomous Daimon action.

Assistant: grok
Assistant-Session: 01a09d5a-92c1-7802-915b-92bee57fc9f0

InterfaceEvolutionIntent.md

@@ -1,8 +1,8 @@
 # Interface Evolution Intent — helix-forge-telegram-publishing
 
-**Document version:** IEI-1
+**Document version:** IEI-2
 **Status:** active
-**Last reviewed:** 2026-09-04
+**Last reviewed:** 2026-09-14
 
 ---
 
@@ -190,6 +190,11 @@ The Daimon must not autonomously:
 - publish to any chat other than those declared in the routing configuration;
 - publish a post about a person who has not consented, on either basis in §15.
 
+These prohibitions bind the Daimon acting autonomously. An operator-triggered
+provisioning tool that executes a plan a person has approved is not the Daimon
+and is not autonomous: it is how the presence is established, not a grant of
+authority to the request path.
+
 The last two matter most, and they are the reason composition sits outside this
 interface. A post is a condensation written in HelixForge's voice about a named
 person's work. It can flatter, it can misstate, and it can put a claim in
@@ -566,7 +571,13 @@ of scope, the first 100 subscribers, or annually.
 
 ### Last reviewed
 
-2026-09-04 (initial)
+2026-09-14 (IEI-2)
+
+### Amendments
+
+- **IEI-2** (2026-09-14): §7 now states that an approved, operator-triggered
+  provisioning plan is not autonomous Daimon action. The request-path
+  prohibitions are unchanged. Previous version: IEI-1 (2026-09-04).
 
 ---