Find the Wrong Line Error Hunt

ROLE: Act as a maths misconception diagnostician, worked-solution auditor and Google Forms developer.

CONTEXT: A teacher wants students in [CLASS] to spot the first wrong line in plausible worked solutions on [TOPIC].

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [TOPIC]
- [ITEM COUNT]
- [COMMON STUDENT ERRORS]
- [DIFFICULTY]
- [MARKS PER ITEM]

DO THIS:
1. Write short numbered solution chains with exactly one first mathematically invalid line per item.
2. Offer line-number choices plus an option stating that no line is wrong only when deliberately requested.
3. Audit every line before and after the breakpoint and explain the smallest valid correction.
4. Add a check-this-yourself link that demonstrates the correct simplification or answer for each computational chain.
5. Generate one complete executable FormApp script with quiz mode, correct line choices, points, feedback and logged URLs.
6. Summarise what each distractor choice suggests the student misunderstood.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Create an error hunt for the false expansion (x+1)^2=x^2+1.
Expected result or check target: The audit shows the missing 2x term is the first break, because the correct difference simplifies to 0 only after including it.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=simplify%20%28x%2B1%29%5E2-%28x%5E2%2B2x%2B1%29
(paste-fallback: simplify (x+1)^2-(x^2+2x+1))
Encoding note: Spaces use %20, parentheses use %28 and %29, + uses %2B and ^ uses %5E.

OUTPUT FORMAT:
1. ERROR-HUNT REVIEW COPY
2. BREAKPOINT AND CORRECTION KEY
3. DISTRACTOR DIAGNOSIS
4. COMPLETE GOOGLE APPS SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. RE-TEACH GROUPS

QUALITY AND TOOL GUARDRAILS:
- Each worked chain must have exactly one unambiguous first wrong line, with every earlier line valid.
- Output one COMPLETE executable FormApp code block and print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never claim a URL creates the form; use allowed solver links only to check the correct mathematics.
- Do not use deliberately malformed notation that becomes unreadable on a phone.
- 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.