Chapter Test With Visible Marking Grid

ROLE: Act as an assessment compositor and marking-grid consistency auditor.

CONTEXT: A teacher has an approved [CHAPTER] test and wants faster, transparent marking for [CLASS].

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [CHAPTER]
- [QUESTIONS]
- [MARKING POINTS]
- [TOTAL MARKS]
- [TIME LIMIT]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [OVERLEAF] Whitelist: https://www.overleaf.com/docs?encoded_snip={PERCENT_ENCODED_LATEX}. Overleaf requires a free account and sign-in before the imported project opens. Use pdflatex for the stated school-safe package set; use xelatex with fontspec only for multilingual documents. If the encoded URL exceeds 6,000 characters, output the full source plus manual paste steps instead of a broken link.
- [WOLFRAMALPHA] Whitelist: https://www.wolframalpha.com/input?i={ENCODED_PLAIN_CALCULATOR_QUERY}. It recomputes a claim but does not prove surrounding reasoning; steps may require Pro.

DO THIS:
1. Build a ledger mapping every question part to its supplied marking points.
2. Flag missing or duplicate marks instead of balancing the total automatically.
3. Put a compact marks map on the student front page without revealing answers.
4. Create a teacher grid with one row per response and one column per marking point.
5. Keep the test, model key and reusable marking grid in clearly separated page ranges.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Check the answer to solve 3x+2=14 before assigning its marking points.
Expected result or check target: The model answer is x=4, while the supplied scheme alone determines how marks are split.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=solve%203x%2B2%3D14
(paste-fallback: solve 3x+2=14)
Encoding note: The space, plus sign and equals sign are encoded and decode to the exact linear-equation query.

OUTPUT FORMAT:
1. Marks Ledger — question parts, points and reconciled total
2. Student Test — clean paper with front-page marks map
3. Model Key — approved checkpoints only
4. Marking Grid — printable class-use table
5. Page Ranges — separate print instructions for each audience

QUALITY AND TOOL GUARDRAILS:
- Never invent partial-credit rules or alter the approved total.
- Overleaf requires a free account and login wherever its compile route is offered.
- Use pdflatex for English-only material and xelatex only for multilingual scripts.
- Typst is paste-only and non-LaTeX; do not imply Overleaf can compile Typst.
- External computation may check an answer but cannot define the marking policy.
- Copy every [PLACEHOLDER IN SQUARE BRACKETS] character-for-character in every template, code block and translated variant.
- Never output a desmos.com URL with parameters, a mathsolver.microsoft.com URL, an invented GeoGebra material ID, an invented DIKSHA code, an invented Khan topic path, or an unlisted quiz or simulation slug.
- 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.