Skip to content

fix(i18n): restore voice settings strings on the memory stack - #348

Draft
daveh-beep wants to merge 1 commit into
clay/memory-reviewfrom
dave/voice-i18n-restore
Draft

daveh-beep wants to merge 1 commit into
clay/memory-reviewfrom
dave/voice-i18n-restore

Conversation

@daveh-beep

Copy link
Copy Markdown
Contributor

Draft — implementation paused pending the remaining-work plan

This is a separate repair branch targeting #289, not main. No review is requested yet. It does not rewrite the memory stack branches.

Scope

Restore the English and Spanish voice settings blocks from the stack's common base, ce48ca5. Commit 5b894c9 removed 63 existing leaf keys and changed 9 existing values in each locale; it also added voice.interruptionDescription, which this patch preserves. The net loss was 62 leaf keys. Everything outside the voice blocks is unchanged.

This corrects the earlier diagnosis in #347: the 14 voice test failures are present in its stack base, but are not pre-existing failures on main. Updating test expectations would conceal the catalog regression.

Validation already completed

  • 447 voice-conversation tests passed across 32 files on this branch.
  • just check passed.
  • Full integrated-stack CI has not been rerun with this repair.

Integration plan

Keep this PR in draft. After the stack owner chooses how to incorporate the repair, propagate it through #290 and #347 and rerun the complete validation gate. No unrelated lockfile change is included.

…ranch

The memory review commit 5b894c9 overwrote the voice block in en and es settings.json with a divergent variant. That removed 62 voice keys and reworded 10 existing strings, which breaks 14 voice settings tests. Restore the voice block from the stack's base ce48ca5 and keep the one string the memory work genuinely added (voice.interruptionDescription). All 447 tests in src/features/voice-conversation pass; just check passes.

Signed-off-by: David Hamilton <daveh@squareup.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant