admin/40227-vm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
40227-vm/backend/docs/walkthrough-checkins.md
Dmitri d4a5378adf Refactor: migrate frontend to Vite/React, add product backend modules 
Frontend:
- Replace Next.js with Vite + React + TypeScript
- Add new component architecture (app-shell, sidebar, dashboard modules)
- Implement product modules: FRAME, safety protocols, walkthrough checkin,
  campus/staff attendance, personality quiz, sign language, classroom timer
- Add shadcn/ui component library with Tailwind CSS
- Remove legacy generated components, stores, and pages

Backend:
- Add product migrations: frame_entries, user_progress, safety_quiz_results,
  walkthrough_checkins, communication_events, personality_quiz_results,
  campus_attendance_config/summaries, staff_attendance_records, content_catalog
- Add corresponding models, services, and routes
- Implement cookie-based auth with refresh token rotation
- Add content catalog seeder with product content
- Migrate to ESLint flat config
- Switch from yarn to npm

Infrastructure:
- Update .gitignore for new tooling
- Add project documentation (CLAUDE.md, docs/)
- Remove deprecated config files and yarn.lock

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-06-09 15:18:23 +02:00

1.4 KiB
Raw Blame History

Walk-Through Check-Ins Backend

Purpose

walkthrough_checkins stores structured classroom observation records for director-level users. The backend owns tenant scope, campus scope, creator ownership, validation, and role-gated access.

API

All routes require JWT authentication.

  • GET /api/walkthrough_checkins: returns check-ins visible to the current manager.
  • GET /api/walkthrough_checkins?teacher_name=<name>: filters visible check-ins by teacher name.
  • POST /api/walkthrough_checkins: creates one check-in for the current user's organization and campus.
  • DELETE /api/walkthrough_checkins/:id: deletes one visible check-in.

Access Rules

  • Director/superintendent-capable generated roles can create, list, and delete check-ins.
  • Records are scoped to the current user's organization.
  • Campus-scoped users write records to their current campus.
  • The frontend does not send organization, campus, creator, or updater fields.

Data Contract

Required mutation fields:

  • teacher_name
  • classroom
  • director_name
  • check_in_date
  • check_in_time
  • attitude_rating
  • classroom_management_rating
  • cleanliness_rating
  • vibes_rating
  • team_dynamics_rating
  • emergency_exit_rating
  • lesson_plan_rating

Optional mutation fields:

  • category comments
  • overall_notes

The backend returns normalized DTO rows with tenant and audit fields.