Save2Save — Project Status Report

Generated on: 2026-03-13 22:35  |  Source: Confluence SRS (v5, 2026-02-22) + Jira (SAVE, cached 2026-03-13 12:00 — Atlassian MCP unavailable this session) + Git (live 2026-03-13)

Executive Summary

46% of SRS requirements are released to production (35/76), with 43% in testing on develop (33/76). Develop branch 340 commits ahead of main (unchanged). Git state stable — no new commits on develop, sprint-8, or sprint-9 since last report. Sprint-8 still 7 commits ahead of develop; Sprint-9 still 10 commits ahead. Active feature branch feat/check-in-button-visual-states now has 1 commit implementing 4-state check-in button with missed banner removal. Latest dev tag: v0.1.0-dev.20260312. Note: Jira ticket statuses carried forward from 2026-03-13 12:00 — Atlassian MCP server was unavailable this session.
46%
Released
43%
In Testing
4%
In Progress
5%
In Development
76
SRS Requirements
0
Open Bugs (all addressed)
46% Done
43%
4%
5%
Done (Released) In Testing In Progress In Development Selected for Dev

SRS Feature Coverage

Module 1: User Accounts & Identity Management 8/9
#SRS RequirementJiraSprintStatus
1.1User Registration with Email VerificationSAVE-15Sprint-1Done (Released)
1.2Mobile Number Registration & VerificationSAVE-16Sprint-2Done (Released)
1.3User Registration DataSAVE-17Sprint-1Done (Released)
1.4Secure User LoginSAVE-18Sprint-1Done (Released)
1.5Password ResetSAVE-19Sprint-1Done (Released)
1.6User Session ManagementSAVE-20Sprint-1Done (Released)
1.7User Account SettingsSAVE-21Sprint-2Done (Released)
1.8User Personal Data ManagementSAVE-22Sprint-2Done (Released)
1.9User Profile Picture (Optional)SAVE-115Sprint-8In Testing (on develop)
Module 2: Localization & Accessibility 0/3 (in testing)
#SRS RequirementJiraSprintStatus
2.1Multi-Language SupportSAVE-23Sprint-5In Testing
2.2RTL / LTR Layout SupportSAVE-24Sprint-5In Testing
2.3Language PersistenceSAVE-25Sprint-5In Testing
Module 3: Safety Check-In System 6/13
#SRS RequirementJiraSprintStatus
3.1Check-In Schedule ConfigurationSAVE-26Sprint-3Done (Released)
3.2Allowed Check-In Response WindowSAVE-27Sprint-3Done (Released)
3.3One-Tap Check-In ConfirmationSAVE-28Sprint-3Done (Released)
3.4Missed Check-In DetectionSAVE-29Sprint-3Done (Released)
3.5Escalation Timing ConfigurationSAVE-30Sprint-6In Testing
3.6Escalation Rule DefinitionSAVE-30, SAVE-39Sprint-6In Testing
3.7Default Check-In & Escalation SettingsSAVE-276Sprint-8In Progress
3.8Push Notification ReminderSAVE-31Sprint-3Done (Released)
3.9SMS Escalation & FallbackSAVE-32Sprint-6In Testing
3.10Application Non-Response HandlingSAVE-33Sprint-6In Testing
3.11Location Capture at Check-InSAVE-34Sprint-6In Testing
3.12Check-In Status Visibility (Dashboard)SAVE-35Sprint-3Done (Released)
3.13Battery Optimization & Background ExecutionSAVE-279, SAVE-359Sprint-9In Progress
Module 4: Trusted Contacts & Access Control 7/9
#SRS RequirementJiraSprintStatus
4.1Trusted Contact TypesSAVE-36Sprint-2Done (Released)
4.2Trusted Contact Data RequirementsSAVE-37Sprint-2Done (Released)
4.3Notification Contacts ConfigurationSAVE-38Sprint-2Done (Released)
4.4Escalation Order & TimingSAVE-39Sprint-6In Testing
4.5Access Contacts ConfigurationSAVE-40Sprint-2Done (Released)
4.6Trigger-Based Access ConditionsSAVE-41Sprint-3Done (Released)
4.7Asset-Level Access ControlSAVE-42Sprint-6In Testing
4.8Access Scope LimitationSAVE-43Sprint-2Done (Released)
4.9Contact ManagementSAVE-44Sprint-2Done (Released)
Module 5: Reminder & Notification Management 0/4 (in testing)
#SRS RequirementJiraSprintStatus
5.1Custom Task RemindersSAVE-45Sprint-7In Testing
5.2Medication RemindersSAVE-46Sprint-7In Testing
5.3Doctor Appointment RemindersSAVE-47Sprint-7In Testing
5.4Daily Reminder SummarySAVE-48Sprint-7In Testing
Module 6: Information Vault 4/10
#SRS RequirementJiraSprintStatus
6.1Vault TypesSAVE-49Sprint-3Done (Released)
6.2User-Defined CategoriesSAVE-50Sprint-7In Testing
6.3Category Fields StructureSAVE-51Sprint-7In Testing
6.4Attachments ManagementSAVE-52Sprint-7In Testing
6.5Asset Category TemplatesSAVE-53Sprint-8In Testing (on develop)
6.6Custom Fields per EntrySAVE-54Sprint-7In Testing
6.7Vault Entry LifecycleSAVE-55Sprint-3Done (Released)
6.8Incapability Definition & ConfirmationSAVE-117Sprint-9In Development (BE done, FE pending)
6.9Trigger-Based Access ControlSAVE-56Sprint-4Done (Released)
6.10Trigger-Based Vault ReleaseSAVE-57Sprint-4Done (Released)
Module 7: Trusted Account Perspective 0/8 (5 in testing)
#SRS RequirementJiraSprintStatus
7.1Trusted Account OverviewSAVE-123Sprint-8In Testing (on develop)
7.2Trusted User Safety Status VisibilitySAVE-162, SAVE-124Sprint-2 + Sprint-9In Development (BE done, FE pending)
7.3Trusted User Status ClassificationSAVE-125Sprint-9In Development (BE done, FE pending)
7.4Trusted Account Navigation to Status DetailsSAVE-126Sprint-9In Development (BE done, FE pending)
7.5Trusted Account Notification ContextSAVE-127Sprint-8In Testing (on develop)
7.6Trusted Account Visibility LimitationsSAVE-128Sprint-8In Testing (on develop)
7.7Multiple Trusted User HandlingSAVE-129Sprint-8In Testing (on develop)
7.8Trusted Relationship Removal HandlingSAVE-130Sprint-8In Testing (on develop)
Module 8: Subscription & Payments 6/8
#SRS RequirementJiraSprintStatus
8.1Subscription ModelSAVE-58Sprint-4Done (Released)
8.2Payment Method (IAP + PayPal)SAVE-59, SAVE-229Sprint-4Done (Released)
8.3Free vs. Premium Feature SeparationSAVE-60Sprint-4Done (Released)
8.4Premium Feature ScopeSAVE-61Sprint-8In Testing (on develop) — re-advanced to Developed
8.5Subscription ActivationSAVE-62Sprint-4Done (Released)
8.6Subscription DeactivationSAVE-63Sprint-4Done (Released)
8.7Subscription Status VisibilitySAVE-64Sprint-4Done (Released)
8.8Premium Feature Flexibility (NF)SAVE-65Sprint-8In Testing (on develop) — re-advanced to Developed
Module 9: Public Website & Onboarding 3/4
#SRS RequirementJiraSprintStatus
9.1Public Landing PageSAVE-66Sprint-8Done (Released)
9.2Feature Explanation ContentSAVE-67Sprint-8Done (Released)
9.3Call-to-Action ElementsSAVE-68Sprint-8Done (Released)
9.4Optional Explainer VideoSAVE-69Sprint-8In Testing (on develop)
Module 10: Navigation & Standard Screens 1/4
#SRS RequirementJiraSprintStatus
10.1Home DashboardSAVE-70Sprint-2Done (Released)
10.2Support / Contact ScreenSAVE-71Sprint-8In Testing (on develop)
10.3Privacy Policy ScreenSAVE-72Sprint-5In Testing
10.4Terms & Conditions ScreenSAVE-73Sprint-5In Testing
Module 11: Compliance & Constraints 0/4
#SRS RequirementJiraSprintStatus
11.1GDPR-Compliant DesignSAVE-74Sprint-5In Testing
11.2No Continuous Location TrackingSAVE-75Sprint-8In Testing (on develop)
11.3Cookie Usage & Consent ManagementSAVE-277Sprint-8Selected for Development
11.4Scope Change ControlSAVE-76Sprint-8In Progress

Coverage Summary

MetricCount%
Total SRS Requirements76
With Jira tickets76100%
Done (Released)3546%
In Testing (on develop)3343%
In Progress (Sprint-8/9)34%
In Development (Sprint-9, BE done)45%
Selected for Development11%

Sprint Progress

Sprint 9 In Development — sprint-9 branch, partially merged

Branch: sprint-9 (10 commits ahead of develop)
Jira: 83 items — 1 Done (SAVE-120), 27 Developed (up from 18, +9), 2 In Progress, 42 Selected for Development (down from 46), 11 Backlog (down from 16)
Key delivery: Incapability settings, vault release confirmation, trusted user status classification, battery optimization, production deployment, app store submissions, tier restructuring
Progress: +9 tickets moved to Developed — production infrastructure (SAVE-334/335/338/339), vault entry type validation (SAVE-390), debt direction schema (SAVE-394), category-vault-type association (SAVE-397), attachment endpoint verification (SAVE-400), and asset template alignment (SAVE-402). Backlog and Selected items progressed into Developed.
KeyTypeSummaryStatus
SAVE-117StoryIncapability Definition & Confirmation ProcessSelected for Dev
SAVE-124StoryTrusted User Safety Status VisibilitySelected for Dev
SAVE-125StoryTrusted User Status ClassificationSelected for Dev
SAVE-126StoryTrusted Account Navigation to Status DetailsSelected for Dev
SAVE-278StoryEscalation Rule DefinitionIn Progress
SAVE-279StoryBattery Optimization & Background Execution HandlingIn Progress
SAVE-286StoryCloudflare Workers Production DeploymentSelected for Dev
SAVE-289StoryGoogle Play Store SubmissionSelected for Dev
SAVE-293StoryApple App Store SubmissionSelected for Dev
SAVE-370StorySubscription Tier Restructuring: 3-Tier ModelSelected for Dev
SAVE-371StoryLocation Sharing in Emergency NotificationsSelected for Dev
SAVE-372StoryEmail Fallback Escalation When Phone UnreachableSelected for Dev
SAVE-373StoryGate Medication & Doctor Reminders to EliteSelected for Dev
SAVE-375StoryGate File Uploads & Attachments to EliteSelected for Dev
SAVE-388StoryVault Entry Type SelectionBacklog
SAVE-391StoryDebt Direction Schema EnforcementBacklog
SAVE-392StoryCategory-to-Vault-Type AssociationBacklog
SAVE-396StoryWire Attachment Manager to Backend Upload APIBacklog
SAVE-399StoryAsset Template Selection Flow in Vault FormBacklog
SAVE-305Sub-task[BE] API - Vault Release Confirmation Schema & EndpointsDeveloped
SAVE-309Sub-task[BE] API - Safety Status Data in Principals ResponseDeveloped
SAVE-314Sub-task[BE] API - Status Classification LogicDeveloped
SAVE-318Sub-task[BE] API - Vault Release Confirmation Cron & Timeout LogicDeveloped
SAVE-321Sub-task[BE] API - Principal Status Enrichment & Escalation StateDeveloped
SAVE-325Sub-task[BE] API - Status Classification Edge Case HandlingDeveloped
SAVE-327Sub-task[BE] API - Escalation Rule DefinitionDeveloped
SAVE-330Sub-task[BE] API - Principal Check-In History EndpointDeveloped
SAVE-331Sub-task[BE] API - High-Priority Push Delivery & Retry LogicDeveloped
SAVE-352Sub-task[BE] API - Incapability Settings Schema & EndpointsDeveloped
SAVE-356Sub-task[BE] API - Multi-Layer Notification Orchestration & Delivery TrackingDeveloped
SAVE-374Sub-task[BE] API - Rename enterprise → elite (DB Migration + Code)Developed
SAVE-376Sub-task[BE] API - Update Tier Limits & Feature Gates ConfigurationDeveloped
SAVE-377Sub-task[BE] API - Add Check-In History Retention EnforcementDeveloped
SAVE-380Sub-task[BE] API - Include Location in Escalation Notification PayloadDeveloped
SAVE-382Sub-task[BE] API - Email Escalation Service & Delivery LogicDeveloped
SAVE-384Sub-task[BE] API - Gate Medical Reminders to EliteDeveloped
SAVE-386Sub-task[BE] API - Gate File Uploads to EliteDeveloped
SAVE-334Sub-task[BE] Infrastructure - Production Environment & Domain SetupDeveloped (NEW)
SAVE-338Sub-task[BE] Infrastructure - Production Monitoring & AlertingDeveloped (NEW)
SAVE-390Sub-task[BE] API - Validate Vault Entry Type on CreationDeveloped (NEW)
SAVE-394Sub-task[BE] API - Add debt_direction Column to vault_entriesDeveloped (NEW)
SAVE-397Sub-task[BE] API - Add vault_type Column to vault_categoriesDeveloped (NEW)
SAVE-400Sub-task[BE] API - Verify Attachment Endpoints ReadinessDeveloped (NEW)
SAVE-402Sub-task[BE] API - Align Asset Templates with SRS (Add Estate)Developed (NEW)

Sprint 8 In Testing — Partially diverged from develop

Branch: sprint-8 now 7 commits ahead of develop (was fully merged) — new work: subscription tier ‘elite’ update, PR #69 review fixes, vault category seeding, attachment hardening
Jira (cached 2026-03-10): 53 items — 4 Done, 3 In Progress, 43 Developed, 3 Selected for Development
Progress: SAVE-61 and SAVE-65 re-advanced to Developed (were regressed to Selected for Dev — now re-advanced after backend tier work completed in Sprint-9). New sprint-8 commits add subscription tier restructuring groundwork.
KeyTypeSummaryStatus
SAVE-66StoryPublic Landing PageDone
SAVE-67StoryFeature Explanation ContentDone
SAVE-68StoryCall-to-Action ElementsDone
SAVE-303TaskUpdate SRS Section 8 — Add IAPDone
SAVE-53StoryAsset Category TemplatesDeveloped
SAVE-69StoryOptional Explainer VideoDeveloped
SAVE-71StorySupport / Contact ScreenDeveloped
SAVE-75StoryNo Continuous Location TrackingDeveloped
SAVE-115StoryUser Profile PictureDeveloped
SAVE-119TaskDefault Check-In & Escalation SettingsDeveloped
SAVE-123StoryTrusted Account OverviewDeveloped
SAVE-127StoryTrusted Account Notification ContextDeveloped
SAVE-128StoryTrusted Account Visibility LimitationsDeveloped
SAVE-129StoryMultiple Trusted User HandlingDeveloped
SAVE-130StoryTrusted Relationship Removal HandlingDeveloped
SAVE-315Sub-task[FE] UI - Default Settings Info BannerDeveloped
SAVE-322Sub-task[FE] UI - Trigger Rules Screen ImplementationDeveloped
SAVE-326Sub-task[FE] UI - Cookie Consent Banner (Demo Web App)Developed
SAVE-76StoryScope Change ControlIn Progress
SAVE-100Story[TL] Weekly Sprint & Delivery Process DefinitionIn Progress
SAVE-276StoryDefault Check-In & Escalation SettingsIn Progress
SAVE-61StoryPremium Feature ScopeDeveloped (re-advanced from Selected)
SAVE-65StoryPremium Feature Flexibility (NF)Developed (re-advanced from Selected)
SAVE-277StoryCookie Usage & Consent ManagementSelected for Dev
SAVE-317Sub-task[CONSOLIDATED] Cookie Audit ChecklistSelected for Dev
SAVE-324Sub-task[CONSOLIDATED] Privacy Policy ChecklistSelected for Dev

Sprint 7 In Testing — Merged to develop

Branch: sprint-7 fully merged into develop (0 commits ahead)
Jira: 28 items — 26 Developed (down from 27), 2 Done (up from 1)
Key delivery: Reminders system (medication, doctor, custom tasks, daily summary), vault categories & custom fields, attachments, custom auth system replacing Supabase
Progress: SAVE-367 (toast/reminders bug) moved from Developed → Done
KeyTypeSummaryStatus
SAVE-358TaskRemove Supabase — Replace with Custom AuthDeveloped
SAVE-45StoryCustom Task RemindersDeveloped
SAVE-46StoryMedication RemindersDeveloped
SAVE-47StoryDoctor Appointment RemindersDeveloped
SAVE-48StoryDaily Reminder SummaryDeveloped
SAVE-50StoryUser-Defined CategoriesDeveloped
SAVE-51StoryCategory Fields StructureDeveloped
SAVE-52StoryAttachments ManagementDeveloped
SAVE-54StoryCustom Fields per EntryDeveloped
SAVE-367BugToast not shown after reminder toggle or delete (useToast instances)Done (was Developed)
SAVE-368BugDashboard ScrollView truncates last 3 children on webDone
SAVE-369BugPremium banner visible for premium users on Reminders (stale tier)Developed

Sprint 6 In Testing — Merged to develop

Branch: sprint-6 fully merged into develop (0 commits ahead)
Jira: 20 items — 19 Developed, 1 Done (was 1 Backlog)
Key delivery: Escalation timing & ordering, SMS escalation, app non-response handling, location capture at check-in, asset-level access control
Progress: SAVE-365 moved from Backlog → Done — JWT collision bug resolved
KeyTypeSummaryStatus
SAVE-30StoryEscalation Timing ConfigurationDeveloped
SAVE-32StorySMS Escalation & FallbackDeveloped
SAVE-33StoryApplication Non-Response HandlingDeveloped
SAVE-34StoryLocation Capture at Check-InDeveloped
SAVE-39StoryEscalation Order & TimingDeveloped
SAVE-42StoryAsset-Level Access ControlDeveloped
SAVE-118TaskEscalation Rule DefinitionDeveloped
SAVE-365BugLogin returns 500 on concurrent same-user logins (JWT collision)Done (was Backlog)

Sprint 5 In Testing — all bugs resolved

Jira: 26 items — 18 Done (up from 17), 8 Developed (down from 9)
Key delivery: i18n (Arabic, English, German), RTL layout, language persistence, privacy/terms screens, GDPR data export & deletion
Progress: 1 sub-task moved from Developed → Done since last report. All 6 bugs remain resolved.
KeyTypeSummaryStatus
SAVE-23StoryMulti-Language SupportDeveloped
SAVE-24StoryRTL / LTR Layout SupportDeveloped
SAVE-25StoryLanguage PersistenceDeveloped
SAVE-72StoryPrivacy Policy ScreenDeveloped
SAVE-73StoryTerms & Conditions ScreenDeveloped
SAVE-74StoryGDPR-Compliant DesignDeveloped
SAVE-344BugVault: Toast notifications invisible while add/edit modal open (items.tsx)Done
SAVE-345BugVault: Toast notifications invisible while modal is openDone
SAVE-346Bugrouter.back() traps users on deep-linked screensDone (was Developed — resolved after multiple cycles)
SAVE-349BugLanguage selection swapped after sign-inDone
SAVE-357Bugonboarding_completed causes cold-start redirectDone
SAVE-363BugPassword reset fails with JWT_SECRET mismatch on env changeDone (was Backlog — resolved after 4 report cycles)

Sprints 1–4 Released

Branch: All merged to main

Epic Progress

EpicStoriesDoneIn TestingIn ProgressIn Dev / SelectedCompletion
User Accounts & Identity9810089%
Localization & Accessibility303000% (in testing)
Safety Check-In System13652046%
Trusted Contacts & Access Control9720078%
Reminder & Notification Mgmt404000% (in testing)
Information Vault104501 dev40%
Trusted Account Perspective80503 dev0% (5 in testing)
Subscription & Payments8620075%
Public Website & Onboarding4310075%
Navigation & Standard Screens4130025%
Compliance & Constraints40211 sel0%

Branch Status

Production

main Last commit: 05bb018 — docs: rewrite CLAUDE.md and README.md with current project state  |  Contains Sprints 1–4  |  Tag: v0.1.0-dev.20260312205441 Released

Testing / QA

develop 340 commits ahead of main (694 files, +87.0k/-23.2k lines)  |  Contains Sprint 5 + 6 + 7 + 8 + legacy overview simplification  |  Recent: Vault migration fix (f588d5c), EAS project ID update, MyCareSafe→CareSafe rename, conditional googleServicesFile, new logo assets In Testing

In Development

sprint-6 0 commits ahead of develop  |  Fully merged Merged
sprint-7 0 commits ahead of develop  |  Fully merged Merged
sprint-8 7 commits ahead of develop  |  Diverged (was fully merged)  |  Subscription tier ‘elite’ update, PR #69 review fixes, vault category seeding, attachment hardening Diverged
sprint-9 10 commits ahead of develop  |  Partially merged (27/83 Developed)  |  Incapability settings, vault release confirmation, principal status, trusted user classification, app store prep, tier restructuring BE In Development

Active Feature Branches

feat/check-in-button-visual-states Active — 1 commit: 4-state check-in button + missed banner removal (2b19227) Active
remotes/origin/landingpage-optimizations Remote-only branch (not local) Remote

Open Bugs

KeyPrioritySummarySprintStatus
SAVE-369LowPremium banner still visible for premium users on Reminders screen — stale tier from /api/featuresSprint-7Fix on develop (pending Jira update)

SAVE-369 fix landed on develop — multiple commits address the stale tier issue: features query invalidation on payment success (b68167d), reasonable staleTime restore (a769bc5), and always-refetch on mount/focus (2daa141). Jira status confirmed still "Developed" (Low priority — pending QA verification to move to Done).

All 6 previously open bugs now resolved:

Risks & Gaps

Bug Trend — All Bugs Addressed
All open bugs now have fixes on develop, including SAVE-369 (Low priority, premium banner stale). Zero unaddressed bugs across the project. The Critical SAVE-346 and High SAVE-363 that had been stalled for multiple report cycles were resolved last period and remain Done.
Sprint-8 Branch Divergence
Sprint-8 still 7 commits ahead of develop (unchanged since last report). Key work includes subscription tier ‘elite’ update, vault category seeding, and attachment hardening. This work still needs to be merged back into develop for testing.
SAVE-61/SAVE-65 Regression Resolved
Premium Feature Scope (SAVE-61) and Premium Feature Flexibility (SAVE-65) remain at Developed status after the Sprint-9 backend tier restructuring work completed.
Sprint-9 Backend Momentum
27 BE sub-tasks now Developed (up from 18, +9 since last report) — production infrastructure, vault schema enhancements (entry types, debt direction, category-vault-type association), attachment readiness, and asset template alignment all completed on backend. However, all FE sub-tasks remain in Selected for Development — frontend work has not started for any Sprint-9 feature. Sprint-9 still has 42 items in Selected for Dev (down from 46) and 11 in Backlog (down from 16), with only 2 In Progress (SAVE-278, SAVE-279).
Sprint-9 Scope
Sprint-9 at 83 tickets — the largest sprint by far, with 55 items not yet started or in early progress (42 Selected + 11 Backlog + 2 In Progress).
Sprint-8 → Develop Merge Needed
Sprint-8 has 7 commits that need merging into develop (subscription tier changes, test fixes).
Sprint-9 Merge Path
Sprint-9 is 10 commits ahead of develop. Full merge to develop is the next milestone before sprint-9 features can enter testing.
Selected for Development (Not Yet Started)
1 SRS requirement still in Selected for Dev: SAVE-277 (Cookie Usage & Consent Management)
PM/TL Coordination Tasks
7 PM/TL coordination tasks across Sprints 1–2 and Sprint-8 remain “In Progress” (SAVE-77, SAVE-79, SAVE-80, SAVE-81, SAVE-82, SAVE-83, SAVE-100). These are process tasks, not code blockers.

Summary Metrics

76
SRS Requirements
35
Done (Released)
33
In Testing
3
In Progress
4
In Development
1
Selected for Dev
MetricValue
Requirements with Jira tickets76 (100%)
Requirements Done (Released)35 (46%)
Requirements In Testing33 (43%)
Requirements In Progress3 (4%)
Requirements In Development (sprint-9)4 (5%)
Requirements Selected for Dev (not started)1 (1%)
Jira Tickets per Sprint
Sprint-120 (17 Done, 3 In Progress)
Sprint-254 (51 Done, 3 In Progress)
Sprint-333 (all Done)
Sprint-431 (all Done)
Sprint-526 (18 Done, 8 Developed)
Sprint-620 (19 Developed, 1 Done)
Sprint-728 (26 Developed, 2 Done)
Sprint-853 (4 Done, 3 In Progress, 43 Developed, 3 Selected for Dev)
Sprint-983 (1 Done, 27 Developed, 2 In Progress, 42 Selected for Dev, 11 Backlog)
Open Bugs1 (Sprint-7: 1 Low — fix on develop, pending QA)
Active SprintSprint-9
Sprints Released (main)1–4
Sprints In Testing (develop)5–8
Sprints In Progress (sprint branch)9
Develop ahead of main340 commits (694 files, +87.0k/-23.2k lines)
Sprint-7 ahead of develop0 commits (fully merged)
Sprint-8 ahead of develop7 commits (diverged from develop)
Sprint-9 ahead of develop10 commits
Latest tagv0.1.0-dev.20260312205441 (no stable release)

Generated with /project-status  |  Save2Save  |  2026-03-13 22:35