docs: "exec" tool disabling

[MaksimSkorobogatov]

📝 Description

🗣️ Type of Change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 📖 Documentation update
• ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

• 🤖 Fully AI-generated (100% AI, 0% Human)
• 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
• 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

Fixes #1621

☑️ Checklist

• My code/docs follow the style of this project.
• I have performed a self-review of my own changes.
• I have updated the documentation accordingly.

[CLAassistant]

All committers have signed the CLA.

[yinwm]

Review Summary

Thanks for documenting the exec tool disabling feature! The content is clear and helpful. However, I found some issues that need to be fixed before merging.

---

❌ Critical Issue: Missing Closing Backticks

In README.pt-br.md (line 705) and README.vi.md (line 677), the Fork bomb line is missing a closing backtick:

- * Fork bomb `:(){ :|:& };:
+ * Fork bomb `:(){ :|:& };:`

This will break the markdown rendering and cause the subsequent content to be rendered as inline code.

Files affected:

• README.pt-br.md:705
• README.vi.md:677

---

💡 Minor Suggestion

In README.md:857, the backticks around exec were removed (the exec tool instead of the \exec` tool`). This seems inconsistent with other references to the tool name in the same document. Consider keeping the backticks for consistency, or if this was intentional, maybe apply the same change across all language versions.

---

Summary

Please fix the missing backticks in the Portuguese and Vietnamese READMEs, then this PR should be good to merge! 🚀

[MaksimSkorobogatov]

@yinwm Thank you for your review!
I fixed the critical issue and applied you minor suggestion by adding the backticks (in body, ignoring titles for consistency with othre titles) in commit cf9304e

[yinwm]

plz fix conflicts, @MaksimSkorobogatov thanks

[yinwm]

@MaksimSkorobogatov plz sign CLA

[MaksimSkorobogatov]

@yinwm, i resolved conflicts, added documentation to more languages and merged last changes from main.

cla sining doesn't work :(

i tried it yesterday and today, it shows me
but nothing changes

[yinwm]

@MaksimSkorobogatov you may check your email address, the one you commit should be in your github email list

[MaksimSkorobogatov]

@yinwm, it worked!
I had to disable the private email setting

[yinwm]

LGTM

[yinwm]

@MaksimSkorobogatov thanks for the pr

[Orgmar]

@MaksimSkorobogatov Thanks for documenting the exec tool disabling! Having clear docs on how to control tool access is important for users managing security boundaries. Nice that it closes out #1621 too.

We have a PicoClaw Dev Group on Discord where contributors connect and collaborate. If you'd like to join, send an email to support@sipeed.com with subject [Join PicoClaw Dev Group] MaksimSkorobogatov and we'll send you the invite link!