chore: clarify commit message style rules in .rules

Separate the body-style, footer-tokens, and Assisted-by rules into
distinct bullets so each constraint is unambiguous.

Assisted-by: Zed (Claude Sonnet 4.6)

Author: jdc-pub

.rules

@@ -19,10 +19,11 @@
 ## Git
 
 - When appropriate, always commit; never push unless asked to directly.
-- When committing, use Conventional Commit style with paragraph styling for the commit message body; use `Assisted-by: $Tool ($Model $Version)` as the final commit message footer where Company can be empty if it's the same as tool.
-  - For example, using Zed's Claude Sonnet 4.6 model should produce: `Assisted-by: Zed (Claude Sonnet 4.6)`.
+- When committing, use Conventional Commit style. The body must be prose paragraphs — never bullet lists.
+- Every trackable change (anything that belongs in a changelog) must appear as either the commit header or a Conventional Commit footer token, e.g. `feat: add Foo`, `deprecates: Bar`.
+  This applies even when the information duplicates the body.
+- The final footer must always be `Assisted-by: $Tool ($Model $Version)` — for example: `Assisted-by: Zed (Claude Sonnet 4.6)`.
 - Prioritize multiple commits when warranted.
-- The project uses conventional commits to track changes, so summarize all changes as either commit headers or footers using Conventional Commit syntax; every change that should be tracked in a changelog should be either a commit header or footer, even if that duplicates information in a commit message.
 - The only commit scopes that should be used are those listed in `.config/committed.toml`; this project does not use scopes for code contributions that are user-facing.
 - Expect `prek` (not `pre-commit`) to have installed git hooks; if no hooks run on commit, try running the install command: `prek install -c .config/pre-commit.yaml`.
 - You may make commits; use `fixup!` and `wip:` as appropriate, but do not `fixup!` commits that are already pushed to a remote.