Split Scrum Wiki into separate daily entries

docs/Scrum_Artifacts.md

@@ -0,0 +1,6 @@
+# 26.04.30 ARTIFACT
+
+## Artifacts Used
+- **Taiga Platform:** Used for managing the Product Backlog, Sprint Backlog, and Kanban board.
+- **GitHub:** Used for version control, code review, and CI/CD pipelines.
+- **Documentation:** The `docs/` folder maintains the Ground Truth architectural state.

docs/Scrum_Daily.md

@@ -0,0 +1,10 @@
+# 26.04.30 DAILY
+
+## Daily Scrum (Stand-up)
+**Frequency:** Daily (15 minutes time-boxed).
+**Participants:** Development Team, Scrum Master.
+**Objective:** 
+To synchronize activities and create a plan for the next 24 hours. Each member answers three questions:
+1. *What did I do yesterday that helped the Development Team meet the Sprint Goal?*
+2. *What will I do today to help the Development Team meet the Sprint Goal?*
+3. *Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?*

docs/Scrum_Plan.md

@@ -0,0 +1,11 @@
+# 26.04.30 PLAN
+
+## Sprint Planning
+**Frequency:** Start of every Sprint (Weekly).
+**Participants:** Product Owner (Customer), Scrum Master, Development Team.
+**Objective:** 
+- Define the Sprint Goal.
+- Review and prioritize the Product Backlog in Taiga.
+- Estimate User Stories (using story points or hours).
+- Select User Stories to form the Sprint Backlog.
+- Break down selected User Stories into actionable Technical Tasks.

docs/Scrum_Retro.md

@@ -0,0 +1,10 @@
+# 26.04.30 RETROSPECTIVE
+
+## Sprint Retrospective
+**Frequency:** End of every Sprint, immediately following the Sprint Review.
+**Participants:** Scrum Team.
+**Objective:** 
+To identify areas of improvement for the upcoming Sprint.
+- **What went well?** (e.g., "Dockerizing Zabbix reduced deployment time.")
+- **What didn't go well?** (e.g., "SQL schema initialization was brittle.")
+- **Actionable improvements:** (e.g., "Implement `SET GLOBAL log_bin_trust_function_creators = 1` permanently.")

docs/Scrum_Review.md

@@ -0,0 +1,10 @@
+# 26.04.30 REVIEW
+
+## Sprint Review
+**Frequency:** End of every Sprint.
+**Participants:** Scrum Team, Stakeholders (Customer).
+**Objective:** 
+- Inspect the Increment (the completed work).
+- Demonstrate new features (e.g., Zabbix Integration, Medical AI Chat).
+- Adapt the Product Backlog if needed.
+- Gather feedback from the stakeholders to ensure the project remains aligned with their needs.

taiga_wiki_push.py

@@ -24,9 +24,12 @@ def push_wiki(slug, md_path):
         payload = {'project': proj_id, 'slug': slug, 'content': content}
         r = requests.post(f'{base_url}/wiki', json=payload, headers=headers, verify=False)
         print(f'Created {slug}: {r.status_code}')
+        if r.status_code != 201:
+            print(r.text)
 
 # In Taiga, the home page of the wiki is usually 'home'
-push_wiki('home', 'docs/Scrum_Wiki.md')
-push_wiki('backup-procedure', 'docs/Backup_Procedure.md')
-push_wiki('wsl-deployment', 'docs/WSL_Deployment.md')
-push_wiki('test-cases-sprint8', 'docs/Test_Cases_Sprint8.md')
+push_wiki('26-04-30-plan', 'docs/Scrum_Plan.md')
+push_wiki('26-04-30-daily', 'docs/Scrum_Daily.md')
+push_wiki('26-04-30-review', 'docs/Scrum_Review.md')
+push_wiki('26-04-30-retrospective', 'docs/Scrum_Retro.md')
+push_wiki('26-04-30-artifact', 'docs/Scrum_Artifacts.md')