Sync .kiro/ from master — v2.2.0 release batch

New specs: archer-template-library, ccp-metrics-view-restructure,
compliance-list-stale-after-sidebar-edit, compliance-metric-estimated-resolution-date,
compliance-remediation-display-fix, flexible-jira-ticket-creation,
forecast-burndown-chart, granite-loader-export, ivanti-queue-clear-completed-fix,
multi-item-jira-ticket, queue-collapsible-sections, vendor-issue-type-dropdown

New steering: archer-template-gen.md

Updated: migration-registration-check hook, remediation-plan-history spec,
gitlab-workflow, tech, versioning steering files

.kiro/steering/gitlab-workflow.md

@@ -28,6 +28,14 @@ When working from a GitLab issue, reference the issue number in:
 
 - Prefer closing issues via commit message keywords (`Closes`, `Fixes`, `Resolves`) so GitLab auto-closes them when the pipeline succeeds on the default branch.
 - If a commit was pushed without the keyword, close the issue via the API after confirming the deploy succeeded.
+- **Always post a brief summary comment** on the issue when closing it. One or two sentences describing what was done is enough — the goal is that anyone reading the issue later understands the resolution without digging through commits. Post the comment via the GitLab API:
+  ```bash
+  curl --silent --request POST \
+    --header "PRIVATE-TOKEN: $GITLAB_PAT" \
+    --header "Content-Type: application/json" \
+    --data '{"body": "Fixed in <commit>. <1-2 sentence summary of what changed>."}' \
+    "http://steam-gitlab.charterlab.com/api/v4/projects/13/issues/<N>/notes"
+  ```
 
 ## Pipeline Notifications