Update fork with upstream changes

Author: Abhijeet2409

.codacy.yml

@@ -0,0 +1,9 @@
+---
+engines:
+  bandit:
+    enabled: true
+    arguments:
+      - "-s"
+      - "B101"
+    exclude_paths:
+      - tests/**

.coderabbit.yaml

@@ -36,7 +36,7 @@ body:
       label: 🆕🐥 Newcomer Friendly
       description: Who is this issue for?
       value: |
-        This **[Good First Issue](https://github.com/hiero-ledger/hiero-sdk-python/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22%20no%3Aassignee)** is a guided, well-scoped task intended for new contributors to the Hiero Python SDK.
+        This **[Good First Issue](https://github.com/hiero-ledger/hiero-sdk-python/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22%20no%3Aassignee)** is a guided, well-scoped task intended for new human contributors to the Hiero Python SDK.
 
         #### What you’ll do
         - ✅ understand how the repository is structured
@@ -269,7 +269,7 @@ body:
 
         - [ ] **Connect** origin with upstream: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/03_staying_in_sync.md)
 
-        - [ ] **Install Packages** and protobufs: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) (or [Windows Setup Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/setup_windows.md) for Windows users)
+        - [ ] **Install Packages** and protobufs: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) (or [Windows Setup Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/setup_windows.md) for Windows users)
 
         - [ ] **Sync Main** pull any recent upstream changes: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/rebasing.md)
 
@@ -284,7 +284,7 @@ body:
       description: Provide a contribution workflow suitable for new contributors.
       value: |
         #### ✅ Get ready
-        - [ ] **Claim the issue:**  comment `/assign`: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/04_assigning_issues.md)
+        - [ ] **Claim the issue:**  comment `/assign`: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/04_assigning_issues.md). Pull requests created without being assigned will be automatically closed.
 
         - [ ] **Double check the Issue and AI plan:** carefully re-read the issue description and the CodeRabbit AI plan
 
@@ -310,7 +310,7 @@ body:
 
         - [ ] **Complete the PR description:**  briefly describe your changes, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/11_submit_pull_request.md)
 
-        - [ ] **Link the Issue:**  link the issue the PR solves in the PR description, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/how_to_link_issues.md)
+        - [ ] **Link the Issue:**  link the issue the PR solves in the PR description, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/how_to_link_issues.md). Pull requests created without a linked issue will be automatically closed.
 
         - [ ] **Submit the pull request:**  click `**Create pull request**` 🎉
 
@@ -394,12 +394,7 @@ body:
       label: 🤖 AI usage guidelines
       description: Guidance on using AI tools responsibly for this issue.
       value: |
-        You’re welcome to use AI tools while working on this issue.
-
-        Many contributors do — especially for:
-        - understanding unfamiliar code
-        - drafting small refactors
-        - sanity-checking approaches
+        Humans are welcome to use AI tools while working on this issue but we do not accept AI bot-authored PRs.
 
         **Use AI responsibly:**
         - review suggestions carefully

.github/ISSUE_TEMPLATE/01_good_first_issue_candidate.yml

@@ -20,7 +20,7 @@ body:
       label: 🆕🐥 Newcomer Friendly
       description: Who is this issue for?
       value: |
-        This **[Good First Issue](https://github.com/hiero-ledger/hiero-sdk-python/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22%20no%3Aassignee)** is a guided, well-scoped task intended for new contributors to the Hiero Python SDK.
+        This **[Good First Issue](https://github.com/hiero-ledger/hiero-sdk-python/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22%20no%3Aassignee)** is a guided, well-scoped task intended for new human contributors to the Hiero Python SDK.
 
         #### What you’ll do
         - ✅ understand how the repository is structured
@@ -253,7 +253,7 @@ body:
 
         - [ ] **Connect** origin with upstream: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/03_staying_in_sync.md)
 
-        - [ ] **Install Packages** and protobufs: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) (or [Windows Setup Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/setup_windows.md) for Windows users)
+        - [ ] **Install Packages** and protobufs: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) (or [Windows Setup Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/setup_windows.md) for Windows users)
 
         - [ ] **Sync Main** pull any recent upstream changes: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/rebasing.md)
 
@@ -268,7 +268,7 @@ body:
       description: Provide a contribution workflow suitable for new contributors.
       value: |
         #### ✅ Get ready
-        - [ ] **Claim the issue:**  comment `/assign`: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/04_assigning_issues.md)
+        - [ ] **Claim the issue:**  comment `/assign`: [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/04_assigning_issues.md). Pull requests created without being assigned will be automatically closed.
 
         - [ ] **Double check the Issue and AI plan:** carefully re-read the issue description and the CodeRabbit AI plan
 
@@ -294,7 +294,7 @@ body:
 
         - [ ] **Complete the PR description:**  briefly describe your changes, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/11_submit_pull_request.md)
 
-        - [ ] **Link the Issue:**  link the issue the PR solves in the PR description, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/how_to_link_issues.md)
+        - [ ] **Link the Issue:**  link the issue the PR solves in the PR description, [Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/how_to_link_issues.md). Pull requests created without a linked issue will be automatically closed.
 
         - [ ] **Submit the pull request:**  click `**Create pull request**` 🎉
 
@@ -378,12 +378,7 @@ body:
       label: 🤖 AI usage guidelines
       description: Guidance on using AI tools responsibly for this issue.
       value: |
-        You’re welcome to use AI tools while working on this issue.
-
-        Many contributors do — especially for:
-        - understanding unfamiliar code
-        - drafting small refactors
-        - sanity-checking approaches
+        Humans are welcome to use AI tools while working on this issue but we do not accept AI bot-authored PRs.
 
         **Use AI responsibly:**
         - review suggestions carefully

.github/ISSUE_TEMPLATE/02_good_first_issue.yml

@@ -35,8 +35,26 @@ issue_has_gfi() {
   [[ "$has" == "true" ]]
 }
 
+# Count open assignments for a user
+# For triage users (mentors), excludes issues with 'mentor-duty' label
+# This allows mentors to be assigned to mentorship issues without consuming their assignment limit
 assignments_count() {
-  gh issue list --repo "${REPO}" --assignee "${ASSIGNEE}" --state open --limit 100 --json number --jq 'length'
+  local permission="${1:-none}"
+  
+  if [[ "$permission" == "triage" ]]; then
+    echo "Triage user detected — excluding mentor-duty issues from count." >&2
+    # For triage users, exclude issues with 'mentor-duty' label
+     gh api "repos/${REPO}/issues?per_page=100&page=1" \
+       -f assignee="${ASSIGNEE}" \
+       -f state=open \
+       --jq '.[] 
+            | select(.pull_request == null)
+            | select(any(.labels[]; .name == "mentor-duty") | not)
+            | .number' | grep -c . || echo 0
+  else
+    # For non-triage users, count all open assignments
+    gh issue list --repo "${REPO}" --assignee "${ASSIGNEE}" --state open --limit 100 --json number --jq 'length'
+  fi
 }
 
 remove_assignee() {
@@ -118,7 +136,7 @@ if is_spam_user; then
   echo "User is in spam list.  Applying restricted assignment rules."
 fi
 
-COUNT="$(assignments_count)"
+COUNT="$(assignments_count "$PERMISSION")"
 
 # Apply assignment rules
 if [[ "$SPAM" == "true" ]]; then