[ISSUE] Define/Document current "best" approach for updating devika

[agrajagco]

Describe your issue

Looking to discuss/propose an "Updating Devika" docs section for testers/contributors returning to projct. It might be self evident to conitributors but to me its brute force/not sure activity...

How To Reproduce

Steps to reproduce the behavior (example):

1. clone, configure
2. (work/test/play-with/submit things/answer questions)
3. Notice updating in the repo...
4. git fetch?
5. assuming that I should refresh
   pip install -r requirements.txt
6. (moment of pause; do I re run the playwright to capture any required updates?)
   playwright install --with-deps
   ...???

Expected behavior

Have at least a fundimental understanding and basic content informing users approaching projeect on how to properly "keep up with updates" in the project

Screenshots and logs

um... non-sequitor

Configuration

Any

Additional context

Thanks for the awesome project... want to keep up and contribute with testing/issues.... um not sur how to close the template out so I'll just stop typing now.