Skip to content

Integrate Telegram architecture and reminder guard - #2

Draft
Bao9494 wants to merge 53 commits into
modoro-digital:mainfrom
Bao9494:telegram-reminder-toolguard-20260711
Draft

Integrate Telegram architecture and reminder guard#2
Bao9494 wants to merge 53 commits into
modoro-digital:mainfrom
Bao9494:telegram-reminder-toolguard-20260711

Conversation

@Bao9494

@Bao9494 Bao9494 commented Jul 12, 2026

Copy link
Copy Markdown

Summary

  • Integration PR for the current Telegram architecture stack from the fork branch into the upstream repo.
  • Latest two commits guard Telegram reminder/tool execution and fix reminder target/content parsing so scheduled messages keep the intended content instead of trailing filler like "nha".
  • Keeps Telegram no-mention group messages silent until policy/mention requires a response.

Important Scope Note

  • Upstream modoro-digital/MODOROClaw:main is behind the fork/local line, so this draft PR currently contains the earlier Telegram architecture commits plus the latest reminder/tool-guard commits.
  • Do not merge blindly as a tiny hotfix PR. Treat this as an integration review PR unless upstream main is first aligned with the fork main.

Verification

  • PASS: runtime Telegram Web E2E created CODEX_E2E_REMINDER_20260712_0030 with expected exec telegram msg send -1003857797941 "CODEX_E2E_REMINDER_20260712_0030", then cleaned the test cron.
  • PASS: vendor/node/node.exe scripts/smoke-test.js from electron/ -> 0 failures, 6 runtime-only warnings.
  • PASS: vendor/node/node.exe electron/scripts/check-telegram-memory-contract.js -> static layered Telegram contract passed; native DB filtering skipped in source clone because better-sqlite3 is unavailable there.
  • PASS: runtime ports are listening: 18789, 20128, 20129, 20200.
  • PASS: no leftover npm install process; worktree is clean.

Notes

  • Pushed to fork remote, not origin.
  • Source node_modules was repaired locally for smoke verification only; ignored by Git.

@Bao9494 Bao9494 changed the title Guard Telegram reminders and tool spawning Integrate Telegram architecture and reminder guard Jul 12, 2026
@Bao9494

Bao9494 commented Jul 12, 2026

Copy link
Copy Markdown
Author

Update 2026-07-12: fixed clean-vendor Telegram patching.

Commit pushed: Bao9494/MODOROClaw@60dcc1f

Verification:

  • Clean C: build worktree: C:\b\mc-tg-build-20260712
  • npm ci --no-audit --no-fund OK
  • npm run prebuild:vendor on clean vendor applied all Telegram patches: dispatch diagnostics, fast id/role/context, reminder fast-path, provider timeout, inbound history, no-mention pretyping. No anchor warnings found.
  • npm run prebuild:models OK
  • node scripts/smoke-test.js OK: 0 failures, 0 warnings
  • npm run build:win OK: LASTEXIT=0
  • Installer: C:\b\mc-tg-build-20260712\dist\9BizClaw Setup 2.4.23.exe
  • Packaged app.asar contains all 8 Telegram patch markers.

Note: the earlier Tee-Object build run returned a PowerShell NativeCommandError because stderr warnings were piped as error records; rerunning with direct redirection returned exit 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant