canvas-setup

# Canvas Setup Set up or repair Canvas Pilot without turning setup into a technical tutorial. The student supplies only facts that Codex cannot discover and completes one normal browser login when needed. Codex performs local checks, installs, configuration edits, and verification itself. Setup is not a scan or assignment workflow. It must never inspect pending assignments, create a plan, draft work, start a quiz attempt, upload, or submit. ## Non-negotiable boundary - Keep `.claude/` read-only. It is frozen legacy history, not an active setup surface. - Do not scan assignments. - Do not execute assignments. - Do not submit, upload, or answer quizzes. - Do not write `assignments.json`, `plan.json`, `result.json`, `REPORT.md`, or `.scan_in_progress`. - Do not write `assignments.json`, `plan.json`, `result.json`, or `REPORT.md`. - Do not create a course skill or route directly from setup. - Successful authentication with empty routes hands off to `canvas-skill-opportunity`; that skill performs read-only evidence review and **stops for the student's numbered choice**. Only a later, separate `canvas-bootstrap` invocation may create one selected skill and route. The student's choice comes before any later `canvas-bootstrap` handoff. - Authentication is not assignment approval. It grants no authority to start, answer, or complete a quiz, upload a file, or submit an assignment. - Never copy a private identity, school, account, credential, course identifier, teach...