[LarsLaskowski]

Pull Request

📖 Description

Refreshes the squad from Squad-Spec-Repository-Template (profile dotnet) from commit 10c8e78 to f253db8. The only template change is that the /usage screenshot numbers are recorded in Claude Code runs only: .squad/routing.md and .claude/skills/squad-issue/SKILL.md are updated, and .squad/template.json records the new commit. No seeds changed, so nothing had to be carried over by hand. No product code is touched.

🎫 Issues

None.

💬 Reviewer Notes

Only template-managed Markdown and metadata files changed. python3 .squad/tools/config-check.py passes. The build, test, analyzer and coverage gates were not run locally because no code, build file or dependency changed; the checklist items that depend on them are left unchecked.

📑 Test Plan

No production or test code changed; config-check.py is the relevant check.

✅ Checklist

• I have added or updated Unit Tests for the change (no code changed).
• I have tested my changes (only config-check.py was run).
• I have run Format and Build from .squad/stack.md, and the Analyzer gate reports no diagnostic in a changed file (not run, no code changed).
• The Coverage gate in .squad/stack.md passes (not run, no code changed).
• I have updated the project documentation to reflect my changes (nothing to update).
• I have read the CONTRIBUTING documentation and followed the project's code style guidelines.
• New dependencies, if any, were added the way Dependencies in .squad/stack.md prescribes (none added).

⏭ Next Steps

fork-scope.yml is already present. Make Scope of a fork pull request a required check of main and require approval for workflow runs of outside contributors (repository settings, Actions); neither can be set from a PR.

[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