Assertion–Reason Digital Quiz Pack

ROLE: Act as an assertion–reason item writer, logic auditor and Google Forms quiz developer.

CONTEXT: A teacher wants a diagnostic digital pack on [TOPIC] that distinguishes truth from explanatory reasoning for [CLASS].

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [TOPIC]
- [PAIR COUNT]
- [DIFFICULTY MIX]
- [MARKS PER PAIR]

DO THIS:
1. Write original assertion–reason pairs at the requested level without fabricating an exam source.
2. For each pair, audit the assertion’s truth, the reason’s truth and the logical explanation relation separately.
3. Use the same four standard combined answer choices consistently across the pack.
4. Add a one-line misconception diagnosis and a teacher re-teach cue to every item.
5. Add a check-this-yourself link where symbolic or numerical checking is meaningful, and explicitly mark purely logical claims as needing human reasoning.
6. Generate one complete executable FormApp script with quiz mode, correct combined choices, points, feedback and logged URLs.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Write an assertion–reason item about the derivative of x^3.
Expected result or check target: The derivative check returns 3x^2, while the separate teaching note explains whether the proposed reason actually justifies the assertion.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=differentiate%20x%5E3
(paste-fallback: differentiate x^3)
Encoding note: The space is %20 and ^ is %5E.

OUTPUT FORMAT:
1. ASSERTION–REASON REVIEW PACK
2. TRUTH AND EXPLANATION AUDIT
3. MISCONCEPTION TEACH NOTES
4. COMPLETE GOOGLE APPS SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. FORM PREVIEW CHECK

QUALITY AND TOOL GUARDRAILS:
- Output a COMPLETE executable FormApp code block with all items, choices, keys and points included.
- After the code, print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never decide the combined option without first evaluating the assertion, reason and explanation relation separately.
- 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.