openspec: archive add-french-translation, sync hacs-packaging spec

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-11-07 18:43:34 +01:00
co-authored by Cursor
parent d5f32d956e
commit be00125465
6 changed files with 11 additions and 1 deletions
+11 -1
View File
@@ -51,9 +51,19 @@ The repository SHALL be mirrored to GitHub for HACS compatibility, since HACS re
- **THEN** they SHALL be pushed to both the primary Gitea repo (origin) and the GitHub mirror (github)
### Requirement: Translations
The integration SHALL provide English UI strings for all config flow steps, errors, abort reasons, options, and entity names.
The integration SHALL provide English and French UI strings for all config flow steps, errors, abort reasons, options, and entity names. Every shipped translation file SHALL have exactly the same key structure as `strings.json`.
#### Scenario: Translation files
- **WHEN** HA renders the integration UI
- **THEN** `strings.json` and `translations/en.json` SHALL provide labels for all steps, fields, errors, and entity names
- **THEN** descriptions SHALL not contain curly braces (parsed as translation placeholders) or newlines (cause MALFORMED_ARGUMENT)
#### Scenario: French UI
- **WHEN** HA renders the integration UI with its language set to French
- **THEN** `translations/fr.json` SHALL provide French labels for all steps, fields, errors, abort reasons, options, and entity names
- **THEN** each French string SHALL use the same `{placeholder}` names as its English counterpart
#### Scenario: Key parity
- **WHEN** a key is added to, renamed in, or removed from `strings.json`
- **THEN** `translations/en.json` and `translations/fr.json` SHALL be updated to the same key structure in the same change
- **THEN** the test suite SHALL fail if any of the three files has a key the others lack