fix(server): wake chat milestones when resource bindings recover

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/plans/2026-10-24-recurring-server-sleep-stack.md

@@ -1586,3 +1586,33 @@ their owning branches, and propagate. Their currently passing CI is not evidence
 against that missing idle-counter assertion. Then continue milestone configuration
 and alternate-receipt coverage, production registration/poll removal, the entire
 original inventory, older E2E/cleanup findings and final master reconciliation.
+
+## Configuration drain propagation and resource milestone producers
+
+Discord #17557 at 954a0faa75 and receiver #17572 at 8815dfad38 now carry the
+confirmed drain-hold repairs, following tool health #17554 at e685a0e7ef.
+The prerequisite #17561 inherited health at 05ac7835fc. Propagation reached
+#17576 a4bc3ea50e, #17578 05797e2b9f, #17580 82d023a3a0, #17583 f4f7e14f7a,
+#17586 920a951505, #17590 d626ff4b13, #17592 33ffff8a12, and #17606 9775b2bc4a.
+All 109 configuration lifecycle/protocol cases pass together after applying the
+tip schema to their disposable databases. See the configuration-worker drain
+repair document for individual causal failures and parent evidence.
+
+Slice 28 adds real inventory/lifecycle resource reactivation wakes. The two
+regressions fail before repair; all 90 milestone lifecycle/governed/resource cases
+and six selected provider acceptance cases pass after it. The owning resource
+module only wakes reopened issue scopes, never unchanged inventory or completed
+history. See the milestone audit for full commands/results and remaining producers.
+
+Fresh gate snapshot /tmp/sleep-stack-gates-configuration-drain-20261025.json has
+no failures for slices 1–12 and 14–16, plus #17505; #17490 still fails E2E shard 3
+and its aggregate. #17518/#17554 have pending review and later updated heads have
+pending checks. New #17576 security finding 4371283330 concerns repeated
+connection writes loading every live voice session in that connection. Inspect
+and address it without dropping future deadlines or configuration revocation.
+The existing #17580 cleanup/company-deletion denial finding remains open. No
+review blocker is resolved merely by pushing inherited changes. No PRs merged.
+
+Origin/master refreshed to e335265568 (task-run UI polling removal #17608).
+Full base reconciliation, remaining recurring-work slices, milestone startup
+wiring, fresh reviews, and all latest-head CI gates remain required.

doc/plans/2026-10-25-chat-run-milestone-sleep-audit.md

@@ -1072,3 +1072,58 @@ passing evidence; the full 108 voice integration cases passed at its parent.
 This establishes the changed dispatch/drain boundary, not final PR readiness or
 host sleep. The same pending predicate in three earlier independent workers is
 still a required parent repair. Remaining milestone producers/wiring are unchanged.
+
+## Resource reactivation producers (2026-10-25)
+
+The current selector admits active/waiting conversations. Resource inventory and
+provider lifecycle recovery can reopen an unavailable conversation after the
+milestone worker exhausted its earlier scan. Both paths lacked an issue wake.
+The real-owner regressions in /tmp/sleep28-resource-before.log fail after commit
+with no failed-run publication, establishing the gap independently of manual
+notification helpers.
+
+Resource reconciliation now owns one local availability transition function. It
+locks the unavailable bindings it will reopen, signals their distinct issue
+scopes before mutation, and retains the existing availability/completed-history
+rules. Both inventory and lifecycle callers use it. Unchanged inventory produces
+no milestone intent; status/health metadata is not indiscriminately promoted to
+company-wide milestone scans. No shared scheduler contract or provider protocol
+changes. The tests use the real credential lease and nested resource transaction,
+prove savepoint release does not publish, prove outer rollback leaves the worker
+quiet, and prove outer commit creates the expected publication. Completed history
+stays completed. They then verify two minutes of quiet and no intent from a
+repeated unchanged inventory.
+
+All 90 milestone lifecycle/governed/resource cases pass in
+/tmp/sleep28-resource-combined-tests.log. That command also named a nonexistent
+__tests__/chat-run-publications.test.ts path; it did not run projection units.
+The separate corrected service-path run is recorded in
+/tmp/sleep28-resource-projection-tests.log. Six existing provider acceptance cases
+pass in /tmp/sleep28-resource-acceptance.log (1,424 deselected, not counted), covering
+Slack membership/reinstall, Slack archive/unarchive, Teams/Telegram lifecycle,
+GitHub resource identity preservation, durable lifecycle retry, and canonical
+Chat SDK resource identifiers. Server typecheck passes in
+/tmp/sleep28-resource-typecheck.log. The dedicated resource database is
+paperclip_sleep28_resource_20261025_test.
+
+The earlier three configuration-owner drain repairs are now propagated. All 109
+health/Discord/receiver cases pass together at 9775b2bc4a in
+/tmp/sleep28-configuration-drain-tests.log. An earlier combined run had 108 passes
+and one schema mismatch because the parent test databases lacked the downstream
+voice cleanup column; the retained log is
+/tmp/sleep28-configuration-drain-schema-before.log. Applying the actual tip
+migrations to those disposable databases fixes that setup error.
+
+This closes resource-owner reactivation, not every configuration producer.
+GitHub-specific repository/installation restoration, other conversation rebinding,
+late authority/lineage recovery, and remaining producer dispositions still need
+review before production registration and retirement of the lifecycle scan.
+Endpoint status/health are not direct milestone selector predicates; changing
+them alone does not justify wiring a broad company wake to every health check.
+The delivery owner retains its current authority checks.
+
+Final resource checkpoint: all 20 projection units pass at the corrected path in
+/tmp/sleep28-resource-projection-tests.log, and server build passes in
+/tmp/sleep28-resource-build.log. Combined selected evidence is 116 distinct
+milestone/projection/provider cases, plus the 109 propagated configuration-owner
+cases. Full remote checks/reviews remain required for the new head.