feat: emergency checklist — allow Remote Coordinators to mark tasks complete; admin checklist/subtask management & reporting

[kathirpsmy]

Emergency checklist — Remote Coordinator task completion, admin checklist/subtask management, and reporting

This pull request introduces the Emergency Checklist feature improvements and admin management tools. It enables SIMS Remote Coordinators (RCs) to mark tasks and subtasks as completed for their assignments, tracks who completed items and when, improves subtask ordering and error handling, and adds admin UI/endpoints to manage checklists, subtasks and report options. It also enhances reporting by adding detailed emergency task statistics and subtask completion data.

Highlights

• Allow Remote Coordinators to mark tasks and subtasks completed for assignments.
• Track completion metadata (completed_by user and completion timestamp) for tasks/subtasks where applicable.
• Add admin features to create, update, reorder and delete checklists and subtasks (with permission safeguards preventing deletion when assigned to emergencies).
• Add permission checks so only authorized users can edit subtasks and see completion metadata.
• Improve checklist update logic to retain existing tasks/subtasks reliably and parse updates robustly.
• Add task reports and a new report tab showing detailed emergency task statistics and per-subtask completion info.
• Fixes and polishing: subtask date variable fix in templates, ordering improvements, and improved error handling/messages.

Why this change

Remote Coordinators need to record when they complete tasks against assignments. Admins needed better tools to manage and maintain checklists and subtasks and prevent accidental data loss. The new reporting makes it easy to audit task completion across emergencies.

Files and areas changed (high level)

• Checklist management views / endpoints (admin)
• Emergency checklist update paths (assignment/task tracking)
• Subtask model fields and handling (completed metadata and ordering)
• Task reporting code and templates
• DB migrations (Alembic / Flask-Migrate) — new migration scripts added

Commit list from this branch (chronological newest -> oldest)

• 5d27460a | feat: improve task and subtask handling in emergency checklist updates with robust parsing and retention logic
• f645cf72 | feat: enhance task report with detailed emergency task statistics and subtask completion information
• 521d68c2 | feat: add prevention for deleting checklists and subtasks assigned to emergencies
• 89293ee5 | feat: add user permission checks for subtask editing and display completed by information
• 565beb3f | feat: enhance subtask management with improved ordering and error handling
• be2e55b7 | feat: add task completion tracking and user assignment
• 3a0568f1 | feat: improve emergency checklist update logic with better task and subtask handling
• cedc5552 | refactor: admin_manage_checklist for improved readability and functionality
• 49efcacc | feat: add new checklist management features including task status updates and task report tab
• 23d4081c | fix: correct subtask completion date variable in emergency template
• 47db2376 | feat: enhance checklist management with sub-task functionality and UI improvements
• 38ba81dc | Add sub-task management functionality to checklist system
• fa0fba5a | feat: initial checklist changes

Database migration notes

This branch contains Flask-Migrate (Alembic) migration scripts. Before you deploy or run the app locally after pulling this branch, apply the migrations to update your database schema.

Recommended local dev steps (PowerShell)

1. Ensure your Python environment is active and dependencies are installed. From the repository root (where flask_app/requirements.txt lives):

# create & activate a virtualenv (if you don't already have one)
python -m venv .venv
. .venv\Scripts\Activate.ps1

# install requirements
pip install -r flask_app/requirements.txt

2. Set Flask environment variables for the session and run the DB upgrade:

$env:FLASK_APP = 'flask_app/run.py'
$env:FLASK_ENV = 'development'

# run the migration upgrade
flask db upgrade

3. Start the app (optional):

# run the dev server
flask run --host 0.0.0.0 --port 5010

Notes and safety tips

• Backup your database before running migrations on staging/production.
• Inspect the migration files under flask_app/migrations/versions/ to see the exact schema changes.
• If you're using a different Flask entrypoint, set FLASK_APP accordingly (e.g. SIMS_Portal:create_app() if applicable).

Docker / container instructions

If you run the app inside Docker (docker-compose), after building/updating the image you can run the upgrade inside the running container:

# build and run (from repository root or where docker-compose.yml exists)
docker compose up --build -d

# find the running container name (example: sims-docker-vscode)
docker ps

# run the migration inside the container (adjust container name)
docker exec -it <container-name> bash
flask db upgrade
exit

If your container doesn't have the Flask CLI available, run the upgrade using the python entrypoint and Flask-Migrate scripts (for example python -m flask db upgrade inside the container).

Testing and validation

• After running flask db upgrade, run a quick smoke test: create a test assignment and mark a subtask complete via the UI or API. Confirm the completed_by and completion timestamp fields are present and saved.
• Manually review the admin checklist pages: create/edit/reorder/delete checklist & subtasks. Confirm deletion prevention triggers when a checklist/subtask is assigned to an emergency.

resolves #127