[LarsLaskowski]

Pull Request

📖 Description

Refreshes the squad from Squad-Spec-Repository-Template (commit 94a7016 → 10c8e78), profile dotnet. The squad-issue skill now records the session's /usage output in its wrap-up, and .squad/routing.md carries the matching one-line change. .squad/template.json records the new commit. No seeded files changed upstream, so nothing was carried over by hand, and no code, dependency or workflow changed.

🎫 Issues

None.

💬 Reviewer Notes

Only template-managed docs changed (3 files). config-check.py passes. No product code is touched, so the build, test and coverage gates were not re-run. The fork-scope.yml workflow is already present; Scope of a fork pull request should be a required check of main, and approval for workflow runs of outside contributors should be required (repository settings, Actions); neither can be set from a PR.

📑 Test Plan

python3 .squad/tools/config-check.py → PASS (7 agents, 5 skills).

✅ Checklist

• I have added or updated Unit Tests for the change. (no code change)
• I have tested my changes.
• I have run Format and Build (no code change).
• The Coverage gate passes (no code change).
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation.
• No new dependencies.

⏭ Next Steps

None.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud