Skip to content

fix(forge): stage Gmail secrets and confirm sends twice - #35

Closed
uphiago wants to merge 4 commits into
mainfrom
feat/gmail-capability
Closed

fix(forge): stage Gmail secrets and confirm sends twice#35
uphiago wants to merge 4 commits into
mainfrom
feat/gmail-capability

Conversation

@uphiago

@uphiago uphiago commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Stage Gmail runtime secrets for the Forge worker after each startup.
  • Require a two-step human confirmation before Hermes sends a direct Gmail message.
  • Record the Listmonk SMTP/template operational state.

Verification

  • pytest tests/test-worker-rpc.py tests/test-hermes-configure.py -q
  • tests/test-hermes-secret-stage.sh
  • tests/infra-regression.sh
  • Manual deployment workflow passed on the feature branch.

uphiago added 4 commits August 4, 2026 23:12
- New mail.send / mail.read capabilities in worker-rpc.py using smtplib (SMTP 587) and imaplib (IMAP 993)
- Router tools gmail_send and gmail_read routing mail.* to the Forge runtime lane
- JobRequest fields to, subject, body, mailbox, limit, query with validation
- Docker secrets gmail_user and gmail_app_password staged on the host (never in git)
- Hermes skill barbarossa-gmail documenting read/send usage
- deploy-runtime-files.sh ensures Gmail secrets exist on deploy
- Router + infra regression tests updated and passing
@uphiago

uphiago commented Aug 5, 2026

Copy link
Copy Markdown
Owner Author

Substituída pela PR #36, criada sobre a main atual para evitar o conflito com a PR #34 já mesclada.

@uphiago uphiago closed this Aug 5, 2026
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