Anonymous Chapter Feedback Pulse

ROLE: Act as a student-voice facilitator, privacy-aware survey designer and Google Forms script developer.

CONTEXT: A teacher wants an anonymous phone pulse after [CHAPTER] for [CLASS] to learn what felt clear, rushed or unsupported.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [CHAPTER]
- [FEEDBACK FOCUS]
- [RESPONSE WINDOW]
- [SCHOOL ACCOUNT CONSTRAINTS]
- [NEXT LESSON DATE]

DO THIS:
1. Write a short mix of confidence scale, pace choice, most-useful method, remaining doubt and one open suggestion.
2. Avoid names, roll numbers, email questions and free-text prompts that unnecessarily invite sensitive personal information.
3. Generate one complete executable FormApp script with quiz mode off, email collection off, neutral wording, a closing message and logged URLs.
4. State that Workspace or domain settings may still require sign-in and must be checked manually after creation.
5. Give exact private-window and phone tests for anonymity before sharing.
6. Provide a coding frame and three response thresholds that lead to specific re-teach actions.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Build a chapter pulse after students solve equations such as 5x-8=17.
Expected result or check target: The mathematical example has x=5, while the pulse asks anonymously whether inverse operations felt clear and what needs re-teaching.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=solve%205x-8%3D17
(paste-fallback: solve 5x-8=17)
Encoding note: The space is %20 and = is %3D.

OUTPUT FORMAT:
1. ANONYMOUS PULSE DESIGN
2. COMPLETE NON-QUIZ FORMAPP SCRIPT
3. RUN IT — script.google.com → New project → paste → Run → View → Logs
4. MANUAL ANONYMITY SETTINGS CHECK
5. PRIVATE-WINDOW PHONE TEST
6. RESPONSE CODING FRAME
7. YOU SAID, I WILL FOLLOW-UP

QUALITY AND TOOL GUARDRAILS:
- Output one COMPLETE executable FormApp code block with quiz mode off and email collection off.
- After the code, print exactly: script.google.com → New project → paste → Run → View → Logs.
- Do not promise perfect anonymity from code alone; tell the teacher to check Workspace sign-in and email settings manually.
- Never claim a URL creates the Form and never collect unnecessary personal or sensitive data.
- 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.