added in documentation

[ConnorWhite9]

IMPORTANT:

• PR must be opened from your personal branch → dev
• You must tag @Team-Deepiri/support-team
• You must update Plaky to "Needs QA"
• Never move a task to "Done" (Done = production release only)

---

Description

Briefly explain what this PR does and why.

Include:

• Related Issue number
• Plaky feature name
• Component, feature, or system affected
• Purpose of change (feature, bug fix, improvement, refactor, security, etc.)

---

Changes

List the most important updates in this PR:

Be specific. Include:

• New or updated functions, services, components, or scripts
• Refactoring or structural improvements
• Dependency or configuration changes
• Any significant implementation details

---

Related

• Issue:
• Plaky:
• Related PRs (optional):

---

Testing

Explain how you verified your changes and how to test your feature:

Additional testing details:

---

Important Notes (Optional)

• Known limitations:
• Blockers:
• CI/CD issues unrelated to this PR:
• Dependencies required for testing:

---

Workflow Checklist (Required)

• Branch is up to date with dev
• PR is from your branch → dev (no longer directly into main)
• PR title follows convention (feat:, fix:, refactor:, etc.)
• Plaky feature/bug name included above
• Tagged @Team-Deepiri/support-team
• Plaky task moved to "Needs QA"

---

Review Requests

@Team-Deepiri/support-team