Adding mastg, maswe and mobileapp api v2.0

[sydseter]

Description

Adding endpoints for fetching the maswe, mastg, cre, and general mobileapp edition mapping.

AI Tool Disclosure

• My contribution does not include any AI-generated content
• My contribution includes AI-generated content, as disclosed below:
  • AI Tools: GitHub CoPilot
  • LLMs and versions: GPT-5.6 Luna, Thinking level: High, Context size: 200K
  • Prompts: similar to cornucopia.owasp.org\src\routes\api\asvs\[edition]\[version] and cornucopia.owasp.org\src\routes\api\capec\[edition]\[version] create server.ts controllers for exposing the mobileapp-mastgt-2.0.yaml and the mobileapp-maswe-2.0.yaml mapping. Add relevant swagger documentation and add the endpoints to svelte.config.js , headers-stage.js and headers.js with the headers needed for exposing the application/json api through cloudflare workers. Also make sure the test coverage is 95% and that you follow the linting rules of the cornucopia.owasp.org project. Ensure the api has the same structure as the other api's expect for the necessary changes due to the fact that these expose the maswe and mastg mapping.

Affirmation

• My code follows the CONTRIBUTING.md guidelines

[qltysh]

All good ✅

[Copilot]

🔵 Needs a closer look

Broad API and deployment changes plus inconsistent OpenAPI examples warrant final human review.

Review details

Suppressed comments (2)

cornucopia.owasp.org/static/api/openapi.yaml:571

• The example is now identified as version 2.0, but its data/M01 payload does not match this endpoint: CreController.getCreMapping returns a standards array, and Mobile App 2.0 card IDs begin with values such as PC2. Please replace the example body with an actual 2.0 response so the newly documented endpoint is usable by consumers.

                      version: "2.0"

cornucopia.owasp.org/static/api/openapi.yaml:390

• This labels the example as a 2.0 response, but the PC3 payload below is still the 1.1 data (PLATFORM-3 and TEST-0008/TEST-0037/TEST-0057). The 2.0 mapping instead uses numeric MASTG IDs and MASWE fields, so clients copying this example receive a contradictory contract. Either update the payload from mobileapp-mappings-2.0.yaml or keep this example identified as 1.1.

                      version: "2.0"

• Files reviewed: 15/15 changed files
• Comments generated: 0 new
• Review effort level: Balanced