docs: refresh OWASP ASI06 and ASI09 mapping

[Kerberosmansour (kerberosmansour)]

Summary

• refresh the OWASP Agentic Top 10 mapping for ASI06 with the implemented MemoryGuard controls and their opt-in integration boundary
• refresh ASI09 with the action-bound approval protocol and available backends
• state the remaining universal UI/integration gaps without overstating coverage
• update implementation evidence while retaining the existing partial-coverage ratings

Root cause

The mapping lagged behind current implementation evidence and described the ASI06 and ASI09 gaps too broadly. This update distinguishes capabilities that exist from integrations that remain application responsibilities.

Validation

• python scripts/docs/check_links.py — 0 new broken links
• python scripts/docs/check_frontmatter.py — passed with one unrelated pre-existing warning
• changed-line spelling and whitespace checks passed

Closes #3672

Tracking

• Primary issue: [Docs]: refresh OWASP ASI06 and ASI09 compliance mappings #3672; the closure directive above remains authoritative.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[github-actions]

PR Review Summary

Check	Status	Details
🔍 Code Review	⚠️ Missing	No current-run comment
🛡️ Security Scan	⚠️ Missing	No current-run comment
🔄 Breaking Changes	⚠️ Missing	No current-run comment
📝 Docs Sync	⚠️ Missing	No current-run comment
🧪 Test Coverage	⚠️ Missing	No current-run comment

Verdict: ⚠️ AI review incomplete; ready for human review

AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims.

[github-actions]

🟡 Contributor Check: MEDIUM

Check	Result
Profile	MEDIUM
Credential	MEDIUM
Overall	MEDIUM

Automated check by AGT Contributor Check.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Imran Siddique (imran-siddique)]

Checked the ASI06 claims against the module rather than reading the prose, because a compliance mapping is a claim about the code and the failure mode is that it drifts ahead of it.

Everything asserted is backed. agent-governance-python/agent-os/src/agent_os/memory_guard.py defines MemoryGuard.validate_write, which calls _check_injection_patterns, _check_code_injection and _check_unicode_manipulation; MemoryEntry.compute_hash is SHA-256 over the UTF-8 content; verify_integrity exists for the post-read check; and _audit_log with AuditRecord backs the write audit trail. The AlertType members line up with the categories the doc names.

Two things make this the right kind of mapping update, and they are worth saying because the opposite is so easy to write.

The ratings stay ⚠️ Partial. New evidence arrived and the score did not move, which is the discipline that makes the rest of the table trustworthy. A refresh that adds implementation detail and quietly upgrades a rating teaches readers to discount every row.

The Known Gap got more specific rather than softer. "No dedicated memory-sandbox or context-integrity module" became a statement that MemoryGuard is opt-in, that applications and framework adapters must place it on their actual read/write path, and that AGT cannot guarantee coverage for an external memory provider that has not integrated it. That is a harder thing to write about your own project than the sentence it replaces, and it is the sentence an assessor actually needs: the control exists, and whether it is on the path is the integrator's problem.

ASI09 follows the same pattern, keeping Partial while naming require_approval as a suspended fail-closed decision bound to the action digest, and calling out the absent universal UI integration rather than implying approval backends close the gap.

I verified ASI06 against the code and read ASI09 without checking each backend claim, so treat my confidence as high on the first and reasonable on the second.

The Validate docs frontmatter red earlier today was the stale-branch artifact from before #3619 merged, and it is green now.

No approve bit on this repo, so a comment, but I would merge it.