Jul 17 - Fill the gaps between Single-tenant mode and Multi-tenant mode - MT7

app/api/__init__.py

@@ -50,7 +50,7 @@ def register_api(app):
     from app.api.comments import bp as comments_bp
     api_bp.register_blueprint(comments_bp)
 
-    # MT-5: Planned inspection assignments (plan-mode schedules)
+    # phase43: Planned inspection assignments (plan-mode schedules)
     from app.api.scheduled import bp as scheduled_bp
     api_bp.register_blueprint(scheduled_bp)
 

app/api/scheduled.py

@@ -1,7 +1,7 @@
 """
 app/api/scheduled.py
 --------------------
-Mobile API endpoint for planned inspection assignments (MT-5, phase43).
+Mobile API endpoint for planned inspection assignments (phase43).
 
 GET /api/v1/scheduled-inspections
     Returns ACTIVE, PLAN-MODE schedules the caller is responsible for.
@@ -17,7 +17,7 @@ Why plan-mode only
 `mode='auto'` schedules materialise themselves into a real Inspection at
 next_run_at, which the iPad already fetches via /api/v1/inspections. Returning
 them here too would show the same work twice, and "Start" is meaningless for a
-schedule that starts itself. This mirrors the web dashboard panel (MT-4).
+schedule that starts itself. This mirrors the web dashboard panel (phase43).
 
 A plan-mode schedule is a PLAN, not an inspection — see
 app/models/inspection_schedule.py for the full lifecycle.