Bilingual Maths Vocabulary Phone Quiz

ROLE: Act as a bilingual maths-language educator, terminology checker and Google Forms developer.

CONTEXT: A teacher wants students in [CLASS] to connect equivalent maths terms in [LANGUAGE 1] and [LANGUAGE 2] using an approved glossary.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [LANGUAGE 1]
- [LANGUAGE 2]
- [APPROVED BILINGUAL GLOSSARY]
- [TOPIC]
- [QUESTION COUNT]
- [SCRIPT OR SPELLING CONVENTION]

DO THIS:
1. Extract only term pairs present in the approved glossary and flag conflicts or missing equivalents for teacher review.
2. Test recognition in both language directions plus meaning-in-context, not transliteration alone.
3. Keep mathematical notation unchanged across languages and use short examples to disambiguate polysemous words.
4. Give a teacher key with a note separating vocabulary errors from maths errors and add check-this-yourself links for numerical examples.
5. Generate one complete executable FormApp script with Unicode text, quiz mode, correct choices, points, feedback and logged URLs.
6. Add a phone typography and language-direction preview checklist.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Build a bilingual vocabulary item around the expression 3*7-2*4.
Expected result or check target: The maths example evaluates to 13 in both languages, while only the approved term labels change.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=3%2A7-2%2A4
(paste-fallback: 3*7-2*4)
Encoding note: The multiplication asterisks and minus signs are URL-safe in this compact query.

OUTPUT FORMAT:
1. APPROVED TERM INVENTORY
2. BILINGUAL QUIZ REVIEW
3. VOCABULARY-VS-MATHS KEY
4. COMPLETE GOOGLE APPS SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. PHONE LANGUAGE PREVIEW

QUALITY AND TOOL GUARDRAILS:
- Use only the teacher’s approved glossary; do not invent translations or silently switch language register.
- Output one COMPLETE executable FormApp code block and print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never translate or alter mathematical symbols, values or formulas.
- Never claim a URL creates the Form; label verification links check this yourself.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.

=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
   geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
   artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
   overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
   (Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
   URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
   payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
   \→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
   leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly:  CHECK → <full raw URL>   (no markdown brackets, nothing after the URL).
6. Directly below every link, print:  (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
   rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.