# 3. AI Study Plan Generation — Test Cases

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: ai_study_plan_generation.md — every feature, sub-feature, and rule covered

## Test Execution Policy

- Zero tolerance: any deviation from the documented behavior is a defect.
- Every failed test is logged with a Bug ID, the feature, the sub-feature, the expected vs actual result, and the severity; 100% of bugs are fixed before the group passes.
- 100% pass rate is required for the group to be marked complete.

## Coverage Matrix

| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 3.1 Plan Creation Rules | Plan inputs (exam date, current level, gaps) | TC-SA-TE-20-001 |
| 3.1 Plan Creation Rules | Coverage rule (all mapped topics before exam date) | TC-SA-TE-20-002 |
| 3.1 Plan Creation Rules | Gap-first rule (weakest topics scheduled first) | TC-SA-TE-20-003 |
| 3.1 Plan Creation Rules | Plan horizon (full exam period, rolling weekly) | TC-SA-TE-20-004 |
| 3.1 Plan Creation Rules | Rule: cannot cover all topics → flagged overloaded | TC-SA-TE-20-005 |
| 3.1 Plan Creation Rules | Rule: no gap data → coverage-based plan | TC-SA-TE-20-006 |
| 3.1 Plan Creation Rules | Rule: rolling weekly regenerates next week each cycle | TC-SA-TE-20-007 |
| 3.1 Plan Creation Rules | Rule: disabled exam type → no plan generated | TC-SA-TE-20-008 |
| 3.1 Plan Creation Rules | Audit logging of plan creation rules | TC-SA-TE-20-009 |
| 3.2 Task Breakdown Templates | Task types (learn, practice, revise, mock test) | TC-SA-TE-21-001 |
| 3.2 Task Breakdown Templates | Task duration defaults (per task type, per grade band) | TC-SA-TE-21-002 |
| 3.2 Task Breakdown Templates | Task ordering rules (learn → practice → revise) | TC-SA-TE-21-003 |
| 3.2 Task Breakdown Templates | Task granularity (per topic, per sub-topic) | TC-SA-TE-21-004 |
| 3.2 Task Breakdown Templates | Rule: no duration default → global default | TC-SA-TE-21-005 |
| 3.2 Task Breakdown Templates | Rule: ordering violation not generated | TC-SA-TE-21-006 |
| 3.2 Task Breakdown Templates | Rule: per sub-topic capped per day | TC-SA-TE-21-007 |
| 3.2 Task Breakdown Templates | Rule: template change applies to new plans only | TC-SA-TE-21-008 |
| 3.2 Task Breakdown Templates | Audit logging of task breakdown templates | TC-SA-TE-21-009 |
| 3.3 Revision Cycle Configuration | Revision intervals (aligned with SRS intervals) | TC-SA-TE-22-001 |
| 3.3 Revision Cycle Configuration | Revision task types (flashcards, quick quiz, summary review) | TC-SA-TE-22-002 |
| 3.3 Revision Cycle Configuration | Revision frequency per topic importance | TC-SA-TE-22-003 |
| 3.3 Revision Cycle Configuration | Final revision window (intensive before exam) | TC-SA-TE-22-004 |
| 3.3 Revision Cycle Configuration | Rule: interval below SRS minimum clamped | TC-SA-TE-22-005 |
| 3.3 Revision Cycle Configuration | Rule: high importance → more revision cycles | TC-SA-TE-22-006 |
| 3.3 Revision Cycle Configuration | Rule: final window overlapping exam truncated | TC-SA-TE-22-007 |
| 3.3 Revision Cycle Configuration | Rule: revision for unlearned topic not scheduled | TC-SA-TE-22-008 |
| 3.3 Revision Cycle Configuration | Audit logging of revision cycle configuration | TC-SA-TE-22-009 |
| 3.4 Milestone Celebration Triggers | Milestone types (topic, phase, mock test, streak) | TC-SA-TE-23-001 |
| 3.4 Milestone Celebration Triggers | Celebration types (badge, confetti, message, reward) | TC-SA-TE-23-002 |
| 3.4 Milestone Celebration Triggers | Milestone thresholds (25/50/75/100% coverage) | TC-SA-TE-23-003 |
| 3.4 Milestone Celebration Triggers | Milestone notification (to student, to parent) | TC-SA-TE-23-004 |
| 3.4 Milestone Celebration Triggers | Rule: milestone fires once per student per plan | TC-SA-TE-23-005 |
| 3.4 Milestone Celebration Triggers | Rule: 100% threshold fires only on full completion | TC-SA-TE-23-006 |
| 3.4 Milestone Celebration Triggers | Rule: reward requires configured reward else message | TC-SA-TE-23-007 |
| 3.4 Milestone Celebration Triggers | Rule: parent notification respects preferences | TC-SA-TE-23-008 |
| 3.4 Milestone Celebration Triggers | Audit logging of milestone celebration triggers | TC-SA-TE-23-009 |
| 3.5 Plan Adherence Tracking | Adherence metrics (on-time completion, slippage days) | TC-SA-TE-24-001 |
| 3.5 Plan Adherence Tracking | Adherence thresholds (on-track, at-risk, off-track) | TC-SA-TE-24-002 |
| 3.5 Plan Adherence Tracking | Slippage detection (tasks pushed beyond planned date) | TC-SA-TE-24-003 |
| 3.5 Plan Adherence Tracking | Adherence alerts (to student, parent, mentor) | TC-SA-TE-24-004 |
| 3.5 Plan Adherence Tracking | Rule: late task counts as slipped | TC-SA-TE-24-005 |
| 3.5 Plan Adherence Tracking | Rule: at-risk threshold → alert not off-track | TC-SA-TE-24-006 |
| 3.5 Plan Adherence Tracking | Rule: alert at most once per threshold crossing per day | TC-SA-TE-24-007 |
| 3.5 Plan Adherence Tracking | Rule: no tasks yet → "not started" not off-track | TC-SA-TE-24-008 |
| 3.5 Plan Adherence Tracking | Audit logging of plan adherence tracking | TC-SA-TE-24-009 |

## 3.1 Plan Creation Rules

### TC-SA-TE-20-001 — Plan inputs (exam date, current level, gaps)
**Type:** Positive
**Covers:** 3.1 → Plan inputs
**Preconditions:** A Super Admin account is active; the Target Exam feature is enabled.
**Steps:**
1. As a Super Admin, open Target Exam Management → AI Study Plan → Creation Rules.
2. Set the plan inputs (exam date, current level, gaps).
3. Verify a generated plan uses the configured inputs.
**Expected Result:** Plan inputs — delivered exactly as documented.
**Priority:** Critical

### TC-SA-TE-20-002 — Coverage rule (all mapped topics before exam date)
**Type:** Positive
**Covers:** 3.1 → Coverage rule
**Preconditions:** Plan inputs are configured.
**Steps:**
1. Enable the coverage rule.
2. Generate a plan and verify all mapped topics are scheduled before the exam date.
**Expected Result:** Coverage rule — delivered exactly as documented.
**Priority:** Critical

### TC-SA-TE-20-003 — Gap-first rule (weakest topics scheduled first)
**Type:** Positive
**Covers:** 3.1 → Gap-first rule
**Preconditions:** A student has identified gaps.
**Steps:**
1. Enable the gap-first rule.
2. Generate a plan and verify the weakest topics are scheduled first.
**Expected Result:** Gap-first rule — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-20-004 — Plan horizon (full exam period, rolling weekly)
**Type:** Positive
**Covers:** 3.1 → Plan horizon
**Preconditions:** Plan inputs are configured.
**Steps:**
1. Set the plan horizon to full exam period and verify the plan spans the period.
2. Set the plan horizon to rolling weekly and verify the plan covers the current week.
**Expected Result:** Plan horizon — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-20-005 — Rule: cannot cover all topics → flagged overloaded
**Type:** Edge
**Covers:** 3.1 → Rule: overloaded
**Preconditions:** The mapped topics cannot all be covered before the exam date.
**Steps:**
1. Generate a plan.
2. Verify the plan is flagged as overloaded.
**Expected Result:** A plan that cannot cover all topics before the exam date is flagged (overloaded) — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-20-006 — Rule: no gap data → coverage-based plan
**Type:** Edge
**Covers:** 3.1 → Rule: no gap data
**Preconditions:** A student has no gap data.
**Steps:**
1. Generate a plan.
2. Verify the plan is coverage-based with no gap-first ordering.
**Expected Result:** A student with no gap data gets a coverage-based plan (no gap-first ordering) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-20-007 — Rule: rolling weekly regenerates next week each cycle
**Type:** Positive
**Covers:** 3.1 → Rule: rolling weekly
**Preconditions:** The plan horizon is rolling weekly.
**Steps:**
1. Advance to the next weekly cycle.
2. Verify the next week's plan is regenerated.
**Expected Result:** A plan horizon of rolling weekly regenerates the next week each cycle — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-20-008 — Rule: disabled exam type → no plan generated
**Type:** Negative
**Covers:** 3.1 → Rule: disabled exam type
**Preconditions:** The exam type is disabled.
**Steps:**
1. Attempt to generate a plan for the disabled exam type.
2. Verify no plan is generated.
**Expected Result:** A plan for a disabled exam type is not generated — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-20-009 — Audit logging of plan creation rules
**Type:** Positive
**Covers:** 3.1 → Audit logging
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Change a plan creation rule.
2. Verify the change is recorded in the audit log with actor, timestamp, and before/after values.
**Expected Result:** Audit logging of plan creation rules — delivered exactly as documented.
**Priority:** Medium

## 3.2 Task Breakdown Templates

### TC-SA-TE-21-001 — Task types (learn, practice, revise, mock test)
**Type:** Positive
**Covers:** 3.2 → Task types
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Open AI Study Plan → Task Breakdown.
2. Define the task types (learn, practice, revise, mock test).
3. Verify generated plans use the defined task types.
**Expected Result:** Task types — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-21-002 — Task duration defaults (per task type, per grade band)
**Type:** Positive
**Covers:** 3.2 → Task duration defaults
**Preconditions:** Task types are defined.
**Steps:**
1. Set the task duration defaults per task type and grade band.
2. Verify generated tasks use the configured durations.
**Expected Result:** Task duration defaults — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-21-003 — Task ordering rules (learn → practice → revise)
**Type:** Positive
**Covers:** 3.2 → Task ordering rules
**Preconditions:** Task types are defined.
**Steps:**
1. Set the task ordering rules.
2. Verify generated tasks follow the ordering.
**Expected Result:** Task ordering rules — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-21-004 — Task granularity (per topic, per sub-topic)
**Type:** Positive
**Covers:** 3.2 → Task granularity
**Preconditions:** Task types are defined.
**Steps:**
1. Set the task granularity to per topic and verify task count.
2. Set the task granularity to per sub-topic and verify task count.
**Expected Result:** Task granularity — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-21-005 — Rule: no duration default → global default
**Type:** Edge
**Covers:** 3.2 → Rule: global default
**Preconditions:** A task type has no duration default set.
**Steps:**
1. Generate a plan containing that task type.
2. Verify the task uses the global default duration.
**Expected Result:** A task with no duration default uses the global default — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-21-006 — Rule: ordering violation not generated
**Type:** Negative
**Covers:** 3.2 → Rule: ordering violation
**Preconditions:** Task ordering rules are set.
**Steps:**
1. Generate a plan.
2. Verify no task ordering violation (practice before learn) is generated.
**Expected Result:** A task ordering violation (practice before learn) is not generated — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-21-007 — Rule: per sub-topic capped per day
**Type:** Edge
**Covers:** 3.2 → Rule: per day cap
**Preconditions:** The task granularity is per sub-topic.
**Steps:**
1. Generate a plan for a topic with many sub-topics.
2. Verify the tasks per day are capped.
**Expected Result:** A granularity of per sub-topic produces more tasks (capped per day) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-21-008 — Rule: template change applies to new plans only
**Type:** Edge
**Covers:** 3.2 → Rule: new plans only
**Preconditions:** An existing plan has been generated.
**Steps:**
1. Change a task breakdown template.
2. Verify the existing plan is unchanged and newly generated plans use the new template.
**Expected Result:** A task template change applies to newly generated plans only — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-21-009 — Audit logging of task breakdown templates
**Type:** Positive
**Covers:** 3.2 → Audit logging
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Change a task breakdown template.
2. Verify the change is recorded in the audit log with actor, timestamp, and before/after values.
**Expected Result:** Audit logging of task breakdown templates — delivered exactly as documented.
**Priority:** Medium

## 3.3 Revision Cycle Configuration

### TC-SA-TE-22-001 — Revision intervals (aligned with SRS intervals)
**Type:** Positive
**Covers:** 3.3 → Revision intervals
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Open AI Study Plan → Revision Cycles.
2. Set the revision intervals aligned with SRS intervals.
3. Verify generated revision tasks use the configured intervals.
**Expected Result:** Revision intervals — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-22-002 — Revision task types (flashcards, quick quiz, summary review)
**Type:** Positive
**Covers:** 3.3 → Revision task types
**Preconditions:** Revision intervals are set.
**Steps:**
1. Choose the revision task types.
2. Verify generated revision tasks use the chosen types.
**Expected Result:** Revision task types — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-003 — Revision frequency per topic importance
**Type:** Positive
**Covers:** 3.3 → Revision frequency
**Preconditions:** Revision task types are chosen.
**Steps:**
1. Set the revision frequency per topic importance level.
2. Verify higher-importance topics get more revision cycles.
**Expected Result:** Revision frequency per topic importance — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-004 — Final revision window (intensive before exam)
**Type:** Positive
**Covers:** 3.3 → Final revision window
**Preconditions:** Revision cycles are configured.
**Steps:**
1. Define the final revision window.
2. Verify intensive revision is scheduled before the exam.
**Expected Result:** Final revision window — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-005 — Rule: interval below SRS minimum clamped
**Type:** Edge
**Covers:** 3.3 → Rule: clamped
**Preconditions:** The SRS minimum interval is known.
**Steps:**
1. Set a revision interval shorter than the SRS minimum.
2. Verify the interval is clamped to the SRS minimum.
**Expected Result:** A revision interval shorter than the SRS minimum is clamped to the SRS minimum — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-006 — Rule: high importance → more revision cycles
**Type:** Positive
**Covers:** 3.3 → Rule: importance
**Preconditions:** Topics have importance levels.
**Steps:**
1. Generate a plan.
2. Verify a high-importance topic gets more revision cycles than a low-importance topic.
**Expected Result:** A high-importance topic gets more revision cycles than a low-importance topic — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-007 — Rule: final window overlapping exam truncated
**Type:** Edge
**Covers:** 3.3 → Rule: truncated
**Preconditions:** The final revision window overlaps the exam date.
**Steps:**
1. Generate a plan.
2. Verify the final revision window is truncated to end before the exam.
**Expected Result:** A final revision window overlapping the exam date is truncated to end before the exam — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-22-008 — Rule: revision for unlearned topic not scheduled
**Type:** Negative
**Covers:** 3.3 → Rule: unlearned topic
**Preconditions:** A topic has not yet been learned.
**Steps:**
1. Generate a plan.
2. Verify no revision task is scheduled for the unlearned topic.
**Expected Result:** A revision task for a topic not yet learned is not scheduled — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-22-009 — Audit logging of revision cycle configuration
**Type:** Positive
**Covers:** 3.3 → Audit logging
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Change a revision cycle setting.
2. Verify the change is recorded in the audit log with actor, timestamp, and before/after values.
**Expected Result:** Audit logging of revision cycle configuration — delivered exactly as documented.
**Priority:** Medium

## 3.4 Milestone Celebration Triggers

### TC-SA-TE-23-001 — Milestone types (topic, phase, mock test, streak)
**Type:** Positive
**Covers:** 3.4 → Milestone types
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Open AI Study Plan → Milestones.
2. Define the milestone types.
3. Verify milestones of the defined types are tracked.
**Expected Result:** Milestone types — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-002 — Celebration types (badge, confetti, message, reward)
**Type:** Positive
**Covers:** 3.4 → Celebration types
**Preconditions:** Milestone types are defined.
**Steps:**
1. Choose the celebration types.
2. Trigger a milestone and verify the chosen celebration fires.
**Expected Result:** Celebration types — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-003 — Milestone thresholds (25/50/75/100% coverage)
**Type:** Positive
**Covers:** 3.4 → Milestone thresholds
**Preconditions:** Milestone types are defined.
**Steps:**
1. Set the milestone thresholds.
2. Verify milestones fire at the configured thresholds.
**Expected Result:** Milestone thresholds — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-004 — Milestone notification (to student, to parent)
**Type:** Positive
**Covers:** 3.4 → Milestone notification
**Preconditions:** Milestones are configured.
**Steps:**
1. Set the milestone notifications to student and parent.
2. Trigger a milestone and verify the notifications are sent.
**Expected Result:** Milestone notification — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-005 — Rule: milestone fires once per student per plan
**Type:** Edge
**Covers:** 3.4 → Rule: once only
**Preconditions:** A milestone has already fired for a student's plan.
**Steps:**
1. Re-trigger the same milestone condition.
2. Verify the celebration does not fire again.
**Expected Result:** A milestone fires only once per student per plan (no re-celebration) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-006 — Rule: 100% threshold fires only on full completion
**Type:** Edge
**Covers:** 3.4 → Rule: 100%
**Preconditions:** A milestone threshold of 100% is configured.
**Steps:**
1. Reach 99% coverage and verify the milestone does not fire.
2. Reach 100% coverage and verify the milestone fires.
**Expected Result:** A milestone threshold of 100% fires only on full completion — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-007 — Rule: reward requires configured reward else message
**Type:** Edge
**Covers:** 3.4 → Rule: reward fallback
**Preconditions:** A celebration type of reward is selected with no reward configured.
**Steps:**
1. Trigger the milestone.
2. Verify a message is sent instead of a reward.
**Expected Result:** A celebration type of reward requires a reward to be configured (else message only) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-008 — Rule: parent notification respects preferences
**Type:** Edge
**Covers:** 3.4 → Rule: preferences
**Preconditions:** A parent has notifications for milestones disabled.
**Steps:**
1. Trigger a milestone with a parent notification.
2. Verify the parent is not notified.
**Expected Result:** A parent notification for a milestone respects the parent's notification preferences — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-23-009 — Audit logging of milestone celebration triggers
**Type:** Positive
**Covers:** 3.4 → Audit logging
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Change a milestone celebration trigger.
2. Verify the change is recorded in the audit log with actor, timestamp, and before/after values.
**Expected Result:** Audit logging of milestone celebration triggers — delivered exactly as documented.
**Priority:** Medium

## 3.5 Plan Adherence Tracking

### TC-SA-TE-24-001 — Adherence metrics (on-time completion, slippage days)
**Type:** Positive
**Covers:** 3.5 → Adherence metrics
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Open AI Study Plan → Adherence.
2. Set the adherence metrics.
3. Verify adherence is computed using the configured metrics.
**Expected Result:** Adherence metrics — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-24-002 — Adherence thresholds (on-track, at-risk, off-track)
**Type:** Positive
**Covers:** 3.5 → Adherence thresholds
**Preconditions:** Adherence metrics are set.
**Steps:**
1. Set the adherence thresholds.
2. Verify students are classified on-track, at-risk, or off-track.
**Expected Result:** Adherence thresholds — delivered exactly as documented.
**Priority:** High

### TC-SA-TE-24-003 — Slippage detection (tasks pushed beyond planned date)
**Type:** Positive
**Covers:** 3.5 → Slippage detection
**Preconditions:** Adherence thresholds are set.
**Steps:**
1. Configure the slippage detection.
2. Verify tasks pushed beyond the planned date are detected as slipped.
**Expected Result:** Slippage detection — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-004 — Adherence alerts (to student, parent, mentor)
**Type:** Positive
**Covers:** 3.5 → Adherence alerts
**Preconditions:** Adherence thresholds are set.
**Steps:**
1. Set the adherence alerts to student, parent, and mentor.
2. Trigger an at-risk condition and verify the alerts are sent.
**Expected Result:** Adherence alerts — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-005 — Rule: late task counts as slipped
**Type:** Edge
**Covers:** 3.5 → Rule: late task
**Preconditions:** A task is completed after its planned date.
**Steps:**
1. Review the student's adherence.
2. Verify the late task counts as slipped (not on-time).
**Expected Result:** A task completed late counts as slipped (not on-time) for adherence — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-006 — Rule: at-risk threshold → alert not off-track
**Type:** Edge
**Covers:** 3.5 → Rule: at-risk
**Preconditions:** A student is at the at-risk threshold.
**Steps:**
1. Review the student's adherence status.
2. Verify the student is at-risk (not off-track) and an alert is sent.
**Expected Result:** A student at the at-risk threshold gets an alert (not off-track yet) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-007 — Rule: alert at most once per threshold crossing per day
**Type:** Edge
**Covers:** 3.5 → Rule: once per day
**Preconditions:** A student crosses a threshold multiple times in a day.
**Steps:**
1. Trigger the threshold crossing repeatedly.
2. Verify the alert fires at most once per threshold crossing per day.
**Expected Result:** An adherence alert fires at most once per threshold crossing per day — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-008 — Rule: no tasks yet → "not started" not off-track
**Type:** Edge
**Covers:** 3.5 → Rule: not started
**Preconditions:** A plan was just generated with no completed tasks.
**Steps:**
1. Review the student's adherence status.
2. Verify the status shows "not started" (not off-track).
**Expected Result:** A plan with no tasks yet (just generated) shows "not started" (not off-track) — delivered exactly as documented.
**Priority:** Medium

### TC-SA-TE-24-009 — Audit logging of plan adherence tracking
**Type:** Positive
**Covers:** 3.5 → Audit logging
**Preconditions:** A Super Admin account is active.
**Steps:**
1. Change a plan adherence setting.
2. Verify the change is recorded in the audit log with actor, timestamp, and before/after values.
**Expected Result:** Audit logging of plan adherence tracking — delivered exactly as documented.
**Priority:** Medium