Improve loop constraints startup message

[dhruvatr]

Summary

Related issue

Changes

• New pattern or starter (followed templates/pattern-template.md + updated registry.yaml)
• Doc / example / story improvement
• Tool / CLI change under tools/
• Test only
• Other

Checklist (from CONTRIBUTING)

• Links work from README or the relevant index
• No secrets, tokens, or internal company URLs
• STATE.md* examples use .example suffix
• Safety-related content references docs/safety.md
• If you touched a package under tools/<pkg>: cd tools/<pkg> && npm ci && npm test
• If you touched the registry: root npm ci && npm run validate:registry

Testing / Dogfood

• npx @cobusgreyling/loop audit . (or package-local tests) on affected paths
• Manual review of generated state / skill output if scaffolding changed

---

Docs, stories, adopters, and small tests: maintainers aim to review within 48 hours (same-day when possible).

Updated the loop-constraints startup confirmation to use clearer and more concise wording. Changed the message to explicitly indicate the number of active constraints loaded from loop-constraints.md.

[cobusgreyling]

Thanks @dhruvatr — this is a two-line docs tweak in skills/loop-constraints/SKILL.md (count N in the startup line + trailing newline). Looks like a good first contribution.

Not merging yet: required checks validate and audit are action_required (first-time-contributor workflow approval), so they have not gone green. Once those succeed this should be a straightforward merge.