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
This commit is contained in:
parent
f7af151f37
commit
1e9481e108
23 changed files with 995 additions and 128 deletions
|
|
@ -23,7 +23,7 @@ fails with a Telegram `400`.
|
|||
3. If the bot was removed entirely, re-add it and re-run one test publication.
|
||||
|
||||
A human must do this. The Daimon is forbidden from changing channel membership
|
||||
or permissions (`InterfaceEvolutionIntent.md` §7).
|
||||
or permissions (`InterfaceEvolutionIntent.md` IEI-2 §7).
|
||||
|
||||
## Rolling back a revision
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue