Misconception Poll With Teaching Notes

ROLE: Act as a formative-assessment specialist, misconception analyst and Google Forms poll developer.

CONTEXT: A teacher needs a rapid concept check for [CLASS] on [CONCEPT], with useful action attached to every response pattern.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [CONCEPT]
- [QUESTION COUNT, DEFAULT 4]
- [KNOWN MISCONCEPTIONS]
- [LESSON OBJECTIVE]
- [POLL TIME]

DO THIS:
1. Write one-concept multiple-choice questions whose incorrect options each embody a named misconception.
2. Give a teacher-only mapping from every option to the likely reasoning behind it.
3. Add one quick re-teach move and one follow-up question for each misconception.
4. Verify every computational key with a check-this-yourself link and separate mathematical correctness from diagnostic interpretation.
5. Generate one complete executable FormApp script with quiz mode, correct choices, points, feedback and logged URLs.
6. Finish with a response-split decision table for what to teach next.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Poll Class 7 students on solving 3x+4=19.
Expected result or check target: The verified solution is x=5; options 23/3, 15 and 5/3 are each tied to a different inverse-operation mistake.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=solve%203x%2B4%3D19
(paste-fallback: solve 3x+4=19)
Encoding note: The space is %20, + is %2B and = is %3D.

OUTPUT FORMAT:
1. CONCEPT POLL REVIEW
2. OPTION-TO-MISCONCEPTION MAP
3. TEACH-NEXT NOTES
4. COMPLETE GOOGLE APPS SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. RESPONSE-SPLIT DECISION TABLE

QUALITY AND TOOL GUARDRAILS:
- Output one COMPLETE executable FormApp code block; no TODOs or manual question-entry gaps.
- After the code, print exactly: script.google.com → New project → paste → Run → View → Logs.
- Every distractor must correspond to a stated misconception rather than being random filler.
- Label solver links check this yourself and keep student-facing feedback respectful.
- Never claim a URL can create the Form; the complete Apps Script is the only creation route.
- 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.