Check say e dey compatible with Foundry Local
### Review Process
- Educational content changes go dey check for accuracy and clarity
- Code samples go dey test for functionality
- Translation updates
Module08/samples/XX] Description for sample changes
```
### Code of Conduct
అన్ని సహకారదారులు [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) ను అనుసరించాలి. దయచేసి సహకరించే ముందు [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) ను సమీక్షించండి.
### Before Submitting
Foundry Local
### Proseso ng Review
- Ang mga pagbabago sa nilalaman pang-edukasyon ay sinusuri para sa katumpakan at kalinawan
- Ang mga sample ng code ay sinusuri para sa functionality
impact revenue and user trust.
Treat every change like it's going through senior codereview:
- No lazy shortcuts or placeholder code
- Handle errors and edge cases properly
- Write code
what is necessary for the requirement. Do not refactor, add comments, or "improve" unrelated code.
5. **Verify**: Bug fixes must include regression tests that fail before the fix and pass
code may rely on new columns, rows, or backfilled data being present at startup, and migration-before-rollout never needs to be flagged as a deploy risk in reviews
variables** → mention them in `AGENTS.md` under "Configuration references" if they affect agent behavior.
- **New code-generation or build steps** → add them under "Regenerating artifacts" in `AGENTS.md`.
When in doubt
record the rationale in the PR if Sonar raises a hotspot. Code change and hotspot review are separate actions.
- **PR description must call out remaining Sonar UI work
agreement before correction.
Bad:
“Yes, you’re right, but…”
Good:
“No. The issue is…”
CodeReview Rules
When reviewing or modifying code:
- Do not assume the user’s diagnosis
applies to all agents.
## Understanding the repository
Read [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) before working on or reviewingcode here. It describes what each service does, how services interact (sandbox creation, traffic routing