iSchool Platform Release Report

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• Attendance and teaching check-in behavior became a more explicit operational workflow with clearer timing rules and submission windows.
• Performance visibility moved closer to day-to-day tutor operations rather than staying isolated in secondary reporting tools.
• Quality review and attendance logic now better reflect actual session timing and classroom behavior.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• Backend changes adjusted check-in eligibility, attendance handling, performance query behavior, and related support jobs so time-based logic is more resilient.
• Frontend work added and refined check-in history, weekly reports, performance views, and timing-sensitive tutor surfaces such as banners and countdowns.
• The overall implementation tightened the contract between backend timing rules and frontend presentation so tutors and reviewers see more trustworthy session state.

Implementation Footprint

Delivery footprint: 89 grouped commits (54 backend / 35 frontend), +21,322 / -3,641 lines of churn.

Backend emphasis: service-layer logic (83), test coverage (79), domain models (57), controllers and API endpoints (36)

Frontend emphasis: feature screens and flows (299), other touched areas (12), shared components (8), API integration (8)

Follow-Up Attention

Suggested validation and follow-up focus after release.

Validate check-in eligibility, attendance submission windows, check-in history filters, banner timing, and performance dashboards.

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• Session access became more explicitly centered on join-time behavior instead of exposing broader meeting data earlier than needed.
• External-meeting fallback is now treated as a deliberate operational path rather than an edge-case workaround.
• Recordings and join-state timing were strengthened as reliability concerns that affect the overall classroom experience.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• Backend resources and controller responses were narrowed around join-only session contracts, while provider-switching and external meeting support were expanded where operational fallback is needed.
• Recording-related models, sync logic, and fetch paths were hardened so recording availability and metadata flow more consistently through admin and meeting experiences.
• Frontend changes updated meeting-state handling, server-time-based join logic, admin actions, and recording surfaces so the UI matches the refined backend contract and runtime conditions.

Implementation Footprint

Delivery footprint: 64 grouped commits (33 backend / 31 frontend), +61,029 / -12,785 lines of churn.

Backend emphasis: test coverage (183), service-layer logic (115), controllers and API endpoints (87), domain models (66)

Frontend emphasis: feature screens and flows (550), shared components (67), other touched areas (37), API integration (29)

Follow-Up Attention

Suggested validation and follow-up focus after release.

Exercise join-only session payloads, switch-to-external flows, join-state timing, recording visibility, exports, and admin copy/join actions.

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• Support handling became a more explicit operational workflow with ownership, visibility, and resolution attribution as first-class concerns.
• Unread state and real-time updates became part of the expected support experience rather than a best-effort enhancement.
• Ticket communication moved closer to live classroom intervention instead of delayed back-office follow-up.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• Backend changes tightened support-ticket visibility logic, assignment rules, resolved-by attribution, and the broadcast paths used to keep ticket state synchronized in near real time.
• Frontend work added unread and live-update behavior, richer thread and ticket editing flows, and stronger support-topic and attachment handling for admins and tutors.
• The combined changes align the frontend ticket experience with the backend's refined ownership and visibility rules so ticket status is more trustworthy across surfaces.

Implementation Footprint

Delivery footprint: 44 grouped commits (28 backend / 16 frontend), +14,836 / -839 lines of churn.

Backend emphasis: test coverage (78), domain models (50), controllers and API endpoints (47), service-layer logic (38)

Frontend emphasis: feature screens and flows (55), WebSocket integration (4), shared components (4), API integration (1)

Follow-Up Attention

Suggested validation and follow-up focus after release.

Re-test ticket visibility rules, resolved-by attribution, admin assignment flows, unread counters, WebSocket updates, and support-topic forms.

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• Filtering, export, and outreach behavior became part of the platform's core operating workflow rather than a collection of one-off admin tools.
• Bulk communication can now target more specific organizational, student, and group segments.
• Reporting and operational follow-up rely less on spreadsheet cleanup outside the platform.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• Backend work expanded filter and export capabilities, refined targeting rules, and updated service and controller logic that powers admin reporting and outreach flows.
• Frontend work improved bulk messaging flows, reporting views, selection controls, and admin search experiences so the richer operational data can actually be used effectively.
• These changes tie segmentation and outreach closer to the same backend rules that power exports and dashboards, reducing mismatch across admin tools.

Implementation Footprint

Delivery footprint: 17 grouped commits (13 backend / 4 frontend), +11,247 / -2,565 lines of churn.

Backend emphasis: service-layer logic (19), test coverage (10), controllers and API endpoints (9), domain models (5)

Frontend emphasis: feature screens and flows (198), shared components (35), other touched areas (13), styles (4)

Follow-Up Attention

Suggested validation and follow-up focus after release.

Re-test exports, filters, newsletter targeting, bulk messaging CSV flows, outreach dashboards, and student/group lookup workflows.

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• Tutor blocks became a governed business workflow with persistent records and review states instead of an ad-hoc operational decision.
• Certificate access moved closer to policy-based eligibility by level rather than broad availability.
• Scheduling and reassignment logic now has explicit safeguards tied to approved tutor-block outcomes.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• Backend work added and evolved tutor-block domain records, review lifecycle handling, and the checks that keep blocked tutor relationships out of scheduling and reassignment flows.
• Certificate-related backend services and level configuration now honor explicit eligibility flags, so downstream certificate behavior follows the configured academic rules.
• Frontend admin work added dedicated tutor-block pages, filters, status handling, review modals, and level-form controls so the new governance model can actually be operated in production.

Implementation Footprint

Delivery footprint: 1 grouped commits (1 backend / 0 frontend), +22 / -1 lines of churn.

Backend emphasis: background jobs (1), domain models (1)

Frontend emphasis: No significant file changes were detected.

Follow-Up Attention

Suggested validation and follow-up focus after release.

Verify tutor-block creation, duplicate handling, review-state transitions, scheduling exclusion, and level-based certificate visibility/download rules.

Business / Domain Changes

Workflow, rule, and operating-model changes introduced by this workstream.

• These commits are valuable but more scattered, so they are grouped as supporting operational changes rather than a single business initiative.
• This bucket is useful for completeness, but it should be read as background release context rather than a headline release theme.

Engineering Change Summary

A more detailed implementation readout for engineering and product partners.

• The bucket includes one-off fixes, smaller dashboards, operational cleanups, and isolated implementation work that did not repeat often enough to deserve its own dedicated workstream.
• Engineering teams should use this section as a completeness pass for the release window rather than the main narrative of the release.

Implementation Footprint

Delivery footprint: 226 grouped commits (132 backend / 94 frontend), +28,517 / -7,411 lines of churn.

Backend emphasis: test coverage (97), service-layer logic (61), controllers and API endpoints (55), other touched areas (52)

Frontend emphasis: feature screens and flows (313), API integration (25), shared components (19), copy and localization (18)

Follow-Up Attention

Suggested validation and follow-up focus after release.

Spot-check any business-critical one-off fixes that do not fall under the main feature sets.