docs: commit scopes for new integration packages

[jtruland]

Area

Docs

Problem

CONTRIBUTING.md lists cursor and antigravity as commit scopes for the existing integration packages, but there isn't a scope yet that fits a new integration. While preparing #34 (a Claude Code hooks package in packages/tiny-engineer-claude-code) I wasn't sure which scope to use, so I went with feat(packages): … for now, although packages isn't on the list either.

Proposed change

Whichever you prefer:

• Add a scope for each integration as it lands (e.g. claude-code)
• Add one general scope, such as packages or integrations, for anything under packages/
• Keep the list as it is and have new integrations omit the scope

Happy to update #34's title to match whichever you choose. Thanks!

[jamro]

Chose integrations — one scope for everything under packages/ (Cursor, Antigravity, Claude Code, later agent CLIs). Per-package scopes (cursor, antigravity, claude-code) would grow with every new agent.

CONTRIBUTING.md and the commit rule now list integrations instead of cursor / antigravity. Please retitle #34 to feat(integrations): add Claude Code hooks CLI (done on the PR).

Old feat(cursor) / feat(antigravity) commits stay as-is.