Skip to content

Harden Loopndroll v1 hooks and notifications#6

Open
TheAngryPit wants to merge 1 commit intolnikell:mainfrom
TheAngryPit:main
Open

Harden Loopndroll v1 hooks and notifications#6
TheAngryPit wants to merge 1 commit intolnikell:mainfrom
TheAngryPit:main

Conversation

@TheAngryPit
Copy link
Copy Markdown

@TheAngryPit TheAngryPit commented Apr 30, 2026

Summary

  • adds a safer v1 hook-driven flow with explicit running/paused/stopped hook lifecycle handling
  • adds Telegram setup/onboarding, DM-only safety, Keychain-backed Telegram/Slack secrets, and migration/redaction support
  • improves thread naming/refresh/orphan cleanup and Telegram status/reply semantics
  • removes unproven passive wake-up behavior from v1 while keeping hook-backed remote control reliable

Safety / behavior

  • v1 remains hook-backed; it does not claim passive app-server wake-up support
  • secrets are stored through Keychain refs where available and plaintext values are redacted from managed logs/state during migration
  • hook removal distinguishes soft pause, file removal, and live runtime unload state
  • Telegram queued/reply/status state is scoped to the active destination

Proof

  • corepack pnpm run check
  • bun test
  • corepack pnpm run build
  • internal fork PR CodeQL checks passed

@TheAngryPit
Harden Loopndroll v1 hooks and notifications
3177011 
Adds a safer v1 hook-driven Loopndroll flow with Telegram onboarding, Keychain-backed secrets, hook lifecycle controls, thread naming cleanup, and scoped Telegram status handling.

Local proof before merge:
- corepack pnpm run check
- bun test
- corepack pnpm run build

Remote CodeQL checks passed on the PR branch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@TheAngryPit