Add OWASP AISVS 1.0 mapping across all three source lists

[ottosulin]

Summary

Adds OWASP AISVS 1.0 as a framework mapping across all three source lists. AISVS is a technical verification standard of 191 testable requirements, so it complements the governance frameworks.

298 mappings covering 41 of 41 entries, using 165 of 191 requirements. Every requirement against AISVS 1.0/en.

Changes

• llm-top10/LLM_AISVS.md, agentic-top10/Agentic_AISVS.md, dsgai-2026/DSGAI_AISVS.md
• data/frameworks/owasp-aisvs.json (191 controls, one per requirement)
• three entries in FRAMEWORK_FILES in scripts/generate.js, plus regenerated data/entries/*.json and data/backlinks.json
• README badge 67 to 70

Few notes

• Tier is derived from the AISVS level (L1 Foundational, L2 Hardening, L3 Advanced). Levels vary per requirement while parseQuickRef() assigns one tier per entry, so the quick-reference tier is each entry's modal level and the exact level is stated in every row's notes.
• 26 requirements are intentionally unmapped, clustering in AI hardware security (C4.2), edge and on-device AI (C4.3) and alignment training (C11.1). Nothing in the entry lists covers those, and forcing them onto adjacent entries would degrade those entries for every framework already attached. Candidates for new entries rather than mappings, opinions welcome.

DSGAI mapping

All of DSGAI01 to DSGAI21, in dsgai-2026/DSGAI_AISVS.md. LLM01 to LLM10 and ASI01 to ASI10 are also covered.

Checklist

• Data is anonymized (no PII, credentials, or org names)
• Entries reference at least one DSGAI ID where applicable
• Validation scripts pass: scripts/validate.js (no AISVS errors) and scripts/ingest-framework.mjs --validate (191 controls, passed).
• One entry per file for dataset contributions - not a dataset contribution; one mapping file per source list, per shared/TEMPLATE.md