All commits in this repository must be in English. This document is enforced by agents via .cursor/rules/commit-conventions.mdc.

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Use lowercase. Omit scope if change spans multiple modules: feat: add municipality search.

• Imperative mood: add, fix, update (not "added", "fixes")
• Max 72 characters
• No period at the end
• No emoji

• Explain why, not what (the diff shows what)
• Wrap at 72 characters
• Reference use case: Implements UC-004 municipality search.
• Reference business rule: Enforces BR-007 minimum search length.

• Refs: UC-005 — use case reference
• Refs: BR-003 — business rule reference
• BREAKING CHANGE: — incompatible API/DB migration
• Closes #123 — issue tracker (when applicable)

feat(domain): add SurveyWeek value object with BR-001 validation

Refs: BR-001

fix(sync): preserve cache when ANP download fails

Sync failures no longer clear previously imported weeks.
Enforces BR-011.

Refs: BR-011, UC-001

docs(use-cases): document UC-003 location selection flow

Refs: UC-003

test(domain): add FuelProduct normalization tests

Refs: BR-002

Per ADR-020, use maintained dev for bounded task commits and a protected dev → main PR. A worktree isolates concurrent authorized efforts when needed. Existing task IDs remain in their commit/issue history; published fixes use new commits, never amend/force push. A current-head guarded merge follows affected tests, required Quick verification and applicable reviews, preserving commits through a merge commit. Retain and synchronize dev after integration. Historical construction branches are deleted only after verified main ancestry; no direct development push to main.

See DELIVERY_WORKFLOW for issue/milestone/wiki cadence, authorization and safe cleanup. Current workflow activation is G01-FLOW, not assumed from this prose.

Same format as commit subject. PR description must include:

Use the phase PR template for phase delivery, including task range, issue closure, tested revision, specialized/quick evidence and separate wiki/release status. The short format below remains useful for small standalone corrections; it does not replace the phase gate.

## Summary
- Bullet points of changes

## Use cases
- UC-00X (if applicable)

## Test plan
- [ ] Domain unit tests pass
- [ ] Manual verification steps

Before committing:

• Commit message is in English
• Type and scope are correct
• Domain changes have unit tests (TDD)
• No secrets, keystores, or local.properties
• No hardcoded user-visible strings (i18n keys used)
• docs/glossary.md updated if domain terms changed
• Use case doc exists if implementing new user flow

• local.properties, *.keystore, .env
• Build outputs (build/, *.apk)
• IDE-specific files (.idea/ except shared configs)
• Large downloaded ANP files in data/downloads/
• Agent temp files (agent-tools/)

When creating commits for the user:

1. Use Conventional Commits format above.
2. Commit/publish only within session-authorized phase delivery; planning-only edits do not imply publication. Reuse existing authorization instead of requesting it per microtask.
3. One atomic implementation commit per locally accepted task; later corrections are additional fix commits in the same phase branch.
4. Reference UC/BR IDs in body when relevant.