Five-Minute Exit Ticket Form Builder

ROLE: Act as a mathematics exit-ticket designer and careful Google Apps Script developer.

CONTEXT: A teacher needs a fast, low-stakes check for [CLASS] on [TOPIC] at the end of [LESSON OR PERIOD].

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [TOPIC]
- [LESSON OBJECTIVE]
- [QUESTION COUNT, DEFAULT 5]
- [MARKS PER QUESTION]

DO THIS:
1. Write a review copy with concise multiple-choice questions, four plausible options, the answer and a one-line teaching explanation.
2. Cover only the stated lesson objective and mix recall, interpretation and one application item.
3. Attach a check-this-yourself verification link to every computational answer before writing the script.
4. Generate one complete executable FormApp script that creates the form, switches quiz mode on, marks correct choices and assigns points.
5. Make every question required, add a useful confirmation message and log both edit and respondent URLs.
6. Print the exact run path after the code and add a two-line teacher check before sharing.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Create a four-question Class 10 exit ticket on quadratic factorisation.
Expected result or check target: The worked check factors x^2-5x+6 as (x-2)(x-3), so its roots are 2 and 3.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=solve%20x%5E2-5x%2B6%3D0
(paste-fallback: solve x^2-5x+6=0)
Encoding note: The space is %20, ^ is %5E, + is %2B and = is %3D.

OUTPUT FORMAT:
1. EXIT TICKET REVIEW COPY
2. ANSWER AND LINK CHECK TABLE
3. COMPLETE GOOGLE APPS SCRIPT
4. RUN IT — script.google.com → New project → paste → Run → View → Logs
5. TEST BEFORE SHARING

QUALITY AND TOOL GUARDRAILS:
- Output one COMPLETE executable Google Apps Script code block using FormApp; do not use TODOs, ellipses, pseudocode or manual question-entry steps.
- After the code, print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never claim that a URL can create a Google Form; the script is the creation route.
- Use plain ASCII maths in form text and 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.