Implement Teacher Teach production experience

[mrwrite]

Summary

This PR implements Phase 3 of the EchoEd UI/UX overhaul for the Teacher Teach experience.

Changes include:

• Adds canonical Teach routes:

  • /teach
  • /teach/classes
  • /teach/classes/:id
  • /teach/curriculum
  • /teach/courses/:courseId/preview
  • /teach/assignments
  • /teach/learners/:learnerId

• Updates teacher/instructor navigation to use Teach routes while preserving legacy /home/sections
  and workspace cohort aliases.

• Reworks the teacher landing page around classroom priorities, learner progress, curriculum
  shortcuts, and supported review/discussion limitations.

• Redesigns class list and class detail with responsive layouts, roster context, assignment creation
  confirmation, progress summaries, and honest unsupported-state language.

• Adds teacher curriculum browse and preview-only course preview that does not create learner
  progress.

• Adds scoped learner detail requiring class roster context.

• Extends section models/services for roster and section summary data.

• Adds/updates teacher production docs:

  • audit
  • route migration
  • role capability map
  • assignment data contract
  • review behavior
  • privacy review
  • accessibility/responsive reviews
  • implementation notes

• Marks OpenSpec teacher tasks 6.1-6.4 complete.

No backend files, migrations, auth changes, or database schema changes were made.

Verification

• npx tsc -p tsconfig.app.json --noEmit passed
• npm run build passed
• npx ng test --watch=false --browsers=ChromeHeadless passed: 233 SUCCESS
• npx playwright test --list passed: 1 demo smoke test discovered
• openspec validate overhaul-role-based-ui-ux-experience --strict passed

Known limitation
Seeded Playwright browser execution remains blocked because local frontend :4200, backend :8000, and
PostgreSQL :5432 are not listening.

Motivation

Why is this change needed?

Type of Change

• Documentation
• Frontend
• Backend
• Tests
• Accessibility
• Demo
• Curriculum/community review
• Other

Test Plan

List the checks you ran.

• Backend tests
• Frontend build
• Frontend unit tests
• Demo smoke test
• Manual review
• Not run. Explain below.

If you could not run a check, explain why:

Screenshots

Add screenshots for visible UI changes.

Accessibility Check

Describe any accessibility impact, including keyboard, contrast, labels, readable text, and mobile layout where relevant.

Community or Curriculum Impact

Does this affect educator review, historical accuracy, source quality, learner experience, community language, or contribution flow?

Notes

Anything maintainers should know?

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
echoed	Ready	Preview, Comment	Jul 12, 2026 3:11pm