Check git commit conventions before committing

Before committing, check How do I commit to git using ORE Studio conventions?. The format requires: a [component] bracket prefix in imperative mood under 72 characters; Story-ID: and Task-ID: trailers (full UUIDs) on every commit that implements agile work; an Environment: trailer naming the worktree (ORES_CHECKOUT_LABEL from that worktree's .env); and a Co-Authored-By: trailer for any LLM-generated commit.

Why: Story-ID/Task-ID trailers were being omitted, breaking traceability between commits and agile artefacts. The Environment trailer was added after a drift investigation needed to know which worktree produced a given commit and that information wasn't recoverable from git history alone. The recipe is the authoritative reference for all four requirements.

How to apply: Every time a commit is about to be made — before constructing the commit message — open the recipe or recall the four requirements: (1) [component] Imperative summary ≤72 chars; (2) Story-ID: / Task-ID: with full UUIDs from the task and story :ID: properties when the commit is part of a story/task; (3) Environment: with the current worktree's ORES_CHECKOUT_LABEL; (4) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> at the end.