[PR] feat(setup): propose mail backends in config and spell out next steps [magpie]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk opened a new pull request, #1636:
URL: https://github.com/apache/magpie/pull/1636

   ## Summary
   
   - `setup config` now proposes mail backends whenever a skill in scope reads or drafts mail (`security`, `release-management`). Before this, `config` never mentioned them, so a contributor configuring a mail skill had no idea what to install. For an ASF project, PonyMail and `apache-projects` are selected by default. For drafting it offers `gmail-plaintext` (the default) or the local Maildir backend for Thunderbird and other mail clients. It never offers the claude.ai Gmail connector, because that connector rewrites links into tracking redirects.
   - Each mail-backend install step (`install.md` 9c, 9d and the new 9e) now ends with a numbered *what to do next* list: run the commands, restart the agent so the MCP tools load, authenticate, verify. Before, the steps showed the commands and stopped.
   - The Maildir backend now has its own install step. Thunderbird reads a Maildir only on a *File per message (maildir)* account, and it may not notice a draft another program wrote until you run *Repair Folder*. Both facts are now in `install.md` and `tools/maildir/README.md`.
   
   ## Type of change
   
   - [x] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
   - [x] Tool / bridge contract (`tools/<system>/*.md`)
   
   ## Test plan
   
   - [x] `prek run --all-files` passes
   - [x] For skill changes: eval suite passes for the affected skill. New `setup/step-config-mail` 5/5; `setup/step-config-adversarial` 5/5 and `setup/step-config-stamp` 6/6 re-run against the edited `config.md`. Self-eval only (Claude Code, Opus 5.5).
   - [x] For skill *behaviour* changes: a new or updated eval fixture is included in this PR (`tools/skill-evals/evals/setup/step-config-mail/`, 5 cases)
   
   ## RFC-AI-0004 compliance
   
   - [x] **HITL** — `config` records choices only in the personal layer; every MCP registration is printed for the user to run, never run by the agent
   - [x] **Write-access discipline** — both drafting backends create drafts only; nothing is sent
   
   ## Linked issues
   
   None.
   
   ## Notes for reviewers (optional)
   
   - `tools/spec-loop/specs/adoption-and-setup.md` gets acceptance criterion 32 for this change. `.last-sync` is left where it was: it is 55 commits behind `main` for reasons unrelated to this PR, and bumping it here would claim those commits are synced.
   
   ---
   
   Generative AI disclosure: drafted with Claude Code (Opus 5.5) and reviewed by the author.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] feat(mail): draft to Gmail or a local Maildir, set per project; setup proposes mail backends [magpie]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #1636:
URL: https://github.com/apache/magpie/pull/1636


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org