GurukulGalaxy Architecture Review, Pending Work & Server Health Analysis

Act as a senior software architect, DevOps engineer, Laravel/PHP reviewer, and product delivery manager.

I am working on GurukulGalaxy project.

I will provide you:
1. Architecture files / flow documents
2. Feature planning documents
3. Pending task notes
4. Server health command outputs
5. Disk/storage command outputs
6. Application/service status outputs

Your task is to carefully read and analyze all provided files and outputs.

Important Rules:
- Do not assume anything that is not present in the provided files or command outputs.
- If something is missing, clearly say "Not found in provided data".
- First understand the architecture, then identify pending work.
- Explain everything in simple words.
- Give clear status: Completed, Pending, In Progress, Blocked, Need Verification.
- Tell how each pending feature/module works based on the architecture.
- Also analyze server health, storage status, performance risk, and urgent issues.

Project Name:
GurukulGalaxy

Main Areas to Analyze:
1. Overall project architecture
2. User flow and modules
3. Feed feature
4. Chat / connect feature
5. Teacher, student, institute flow
6. Course / mock test / learning flow
7. Admin panel or dashboard flow
8. API/backend services
9. Database or storage dependency
10. Pending development work
11. Pending testing work
12. Pending code fixing work
13. Pending deployment or server work
14. Server health
15. Disk/storage usage
16. RAM, CPU, MySQL, Redis, Apache, Keycloak, queue, scheduler, logs

Output Format:

1. Executive Summary
Give a short summary of current project status.

2. Architecture Understanding
Explain:
- What the system is
- Main modules
- How users interact with the platform
- How data flows between frontend, backend, database, auth, and other services

3. Module-wise Status Table
Create a table like this:

| Module / Feature | Purpose | Current Status | Pending Work | Risk | Priority |
|------------------|---------|----------------|--------------|------|----------|

4. Pending Work List
Separate pending work into:

A. Development Pending
B. Testing Pending
C. UI/UX Pending
D. Backend/API Pending
E. Database Pending
F. Server/Deployment Pending
G. Security Pending
H. Documentation Pending

For every pending item, mention:
- What is pending
- Why it is pending
- How it should work
- What needs to be done next
- Priority: High / Medium / Low

5. How It Works
Explain important flows step by step:

Example:
- User registration flow
- Login/authentication flow
- Feed post creation flow
- Chat/connect flow
- Teacher/institute discovery flow
- Mock test or course flow

Use this format:

Flow Name:
Step 1:
Step 2:
Step 3:
Expected Result:
Possible Issue:

6. Testing Status
Analyze what needs testing:

| Test Area | What to Test | Current Status | Missing Test | Priority |
|----------|--------------|----------------|--------------|----------|

Include:
- Functional testing
- UI testing
- API testing
- Security testing
- Performance testing
- Role-based testing
- Mobile responsive testing

7. Server Health Status
Analyze server outputs and explain:

| Component | Status | Observation | Risk | Recommended Action |
|----------|--------|-------------|------|--------------------|

Check:
- CPU usage
- RAM usage
- Disk usage
- Swap status
- Apache status
- MySQL status
- Redis status
- Keycloak status
- Queue status
- Scheduler status
- SSL status
- Logs size
- Storage growth risk

8. Storage Status
Explain:
- Total disk size
- Used storage
- Available storage
- Biggest folders
- Log file size
- Laravel storage size
- Database size
- Backup size
- Whether cleanup is required
- Whether alert system is required

9. Risk Analysis
Create table:

| Risk | Impact | Severity | Fix Required |
|------|--------|----------|--------------|

Include risks related to:
- Security
- Storage
- Server performance
- Incomplete features
- Broken user flow
- Untested code
- Deployment issues

10. Recommended Next Action Plan
Create a clear action plan:

Today:
Next 24 Hours:
Next 48 Hours:
This Week:

11. Final Status
Give final project status in this format:

Overall Project Status:
Server Health Status:
Storage Status:
Testing Status:
Deployment Readiness:
Production Risk Level:
Top 5 Urgent Actions:

12. GitHub Issue Format
At the end, create a GitHub issue-ready summary with:

Title:
Description:
Current Status:
Pending Tasks:
Server Health:
Storage Status:
Risks:
Acceptance Criteria:
Priority:
Labels:

Now wait for my architecture files and command outputs, then analyze them properly.