more version 18 test fixes

OpenJibo/docs/feature-backlog.md

@@ -43,6 +43,7 @@ Current release theme:
 - `jibo test 23` validated basic news, proved one alarm set/fire path at `7:43 AM`, exposed comma-separated/short alarm follow-up parsing risk, showed stock alarm replacement yes/no rules that needed cloud handling, and showed photo gallery still failing when `shared/yes_no` ASR came back empty
 - `jibo test 24` showed alarm replacement yes/no working, but exposed empty `clock/alarm_set_value` and `gallery/gallery_preview` turns falling into generic `I heard you` fallback speech; it also showed `CLIENT_NLU cancel` inside `clock/alarm_set_value` re-asking for an alarm value instead of closing the prompt
 - `jibo test 25` proved a broader regression path but exposed repeated backup-in-progress/update-menu blockage, timer/alarm stale state and delete/menu disagreement, gallery `shared/yes_no` hangs under `@be/gallery`, punctuated `Never mind.` falling through to chat, volume homophone parsing (`Set Volume 2-6.`), and settings volume-control cleanup falling into `I heard you`
+- `jibo test 26` live-proved punctuated stop, volume homophone parsing, gallery launch/yes/create/save, and good morning; it still exposed robot-local backup warnings, long blue-ring buffering without a fresh `LISTEN`, alarm replacement drifting into the value/manual screen, and alarm delete phrases/mishears falling to chat
 
 ## Immediate `1.0.18` Queue
 
@@ -101,10 +102,12 @@ Current release theme:
 - Latest evidence:
   - `jibo test 22` did not show `Backup_*` HTTP traffic during the backup complaint
   - `jibo test 25` again showed backup-in-progress/update-menu blockage without `Backup_*` HTTP traffic; observed cloud traffic was log upload, ASR binary upload, and update check traffic
+  - `jibo test 26` again had the robot announce backup-in-progress from `@be/surprises-ota`, with no `Backup_*` HTTP target in the capture
   - stock `@be/surprises-ota` drives the backup notification from robot-local `jibo.scheduler.backupStatus`
   - original `surprises-ota` tests make backup and OTA notifications contextual-priority prompts, with repeat suppression through last-notification timestamps
   - a spoken `take a backup` command currently routes as generic chat and is not the same as proving the local backup scheduler path
-  - `jibo test 23` and `jibo test 25` showed backup-in-progress sluggishness and update-menu blockage while backups were active; explicit backup voice launch remains unwired
+  - `jibo test 23`, `jibo test 25`, and `jibo test 26` showed backup-in-progress sluggishness or warnings while backups were active; explicit backup voice launch remains unwired
+  - Test 26 suggests this should be investigated beside robot-local scheduler status and log/upload load rather than only hosted backup APIs
 - Exit criteria:
   - spoken `yes` and `no` work on update, backup, share/offer, and gallery/create prompts
   - empty or missed short replies retry locally instead of relaunching Nimbus or generic chat
@@ -129,6 +132,8 @@ Current release theme:
   - empty `gallery/gallery_preview` turns complete locally as no-input instead of relaunching Nimbus fallback speech
   - passive gallery/create/settings context no longer reopens stale cloud turns
   - active local prompts under gallery/settings contexts are preserved so real short replies are not suppressed as passive context
+  - context-only or post-skill binary audio tails are ignored until a fresh `LISTEN`, preventing no-`LISTEN` blue-ring buffering loops
+  - blank-audio hotphrase turns clear pending listen state and install a short late-audio ignore window
   - `shared/yes_no` no-input fallback and repeated create keeper cleanup were added after `jibo test 22`
 - Latest evidence:
   - gallery opened and handed into create, but repeated `create/is_it_a_keeper` prompts could leave the blue ring/listening state
@@ -140,6 +145,8 @@ Current release theme:
   - `jibo test 24` showed photo/gallery blue-ring cleanup improved and create keeper completion working, but empty `gallery/gallery_preview` produced `I heard you`; current source now keeps that as local no-input
   - `jibo test 25` showed gallery launching from the observed phrase `open the photogal`, but active `shared/yes_no` prompts under `@be/gallery` could hang; current source now recognizes the alias and preserves active gallery prompts even while ignoring passive gallery tails
   - `jibo test 25` showed timer/alarm still needs live follow-up for stale timer state, alarm replacement/PM ambiguity, and voice delete versus robot menu agreement
+  - `jibo test 26` showed gallery success through empty-gallery yes, create, keep, save, and reopen, but also showed a post-gallery blue-ring/fallback tail now addressed by the no-`LISTEN` binary guard
+  - `jibo test 26` showed alarm replacement still drifting into value/manual-screen behavior and alarm delete phrases/mishears falling to chat; current source now maps `delete the alarm`, `delete along`, and `delete the along` to local clock delete without keeping follow-up open
   - original clock tests confirm cancel inside the alarm value prompt must close without scheduling, existing-alarm `keep` must preserve KB/scheduler state, and existing-alarm `delete` or `cancel` must clear it
   - original gallery tests confirm empty-gallery `yes` redirects to `@be/create`, empty-gallery `no` exits, media-load failure exits, and delete confirmation only deletes on a positive `yes`
 - Exit criteria:
@@ -166,10 +173,12 @@ Current release theme:
   - stop/cancel matching now normalizes stock ASR punctuation, so `Never mind.` is still a stop command
   - absolute volume parsing now treats the observed homophone shape `Set Volume 2-6.` as level `6`
   - passive settings context and `settings/volume_control` no-input cleanup now avoid post-panel `I heard you` fallback speech
+  - local clock delete/cancel commands now settle without a generic follow-up mic
 - Evidence:
   - Pegasus `globals/global_commands_launch.rule` defines `stop`, `volumeUp`, `volumeDown`, and `volumeToValue`
   - stock Jibo `VolumePlugin` subscribes to global volume events and uses the same intent/entity names
   - stock `@be/settings` exposes `volumeQuery` and opens the volume panel
+  - `jibo test 26` live-proved punctuated `Never mind.` and the `Set Volume 2-6.` homophone path
 - Exit criteria:
   - live stop settles the robot without a generic chat reply
   - live volume up/down audibly changes volume or logs a local volume event
@@ -225,7 +234,7 @@ Current release theme:
 - Follow-up:
   - live regression remains in the immediate queue
   - add fixture coverage for original clock-test branches that are not yet mirrored in `.NET`: no-alarm query `yes`/`no`, existing-alarm `keep` versus `delete`, and cross-domain `OtherSet` behavior
-  - Test 25 still requires a focused live check for timer stale state and alarm voice delete versus menu state
+  - Test 26 still requires a focused live check for alarm replacement, voice delete versus menu state, and whether the no-`LISTEN` guard removes the long blue-ring loop
 
 ### Photo / Gallery / Create Family
 
@@ -352,6 +361,7 @@ Current release theme:
   - original OTA surprise tests treat backup/download status as robot-local scheduler state, not as a direct cloud backup command path
   - no-op update fabrication has been removed from `.NET`
   - Test 25 still showed repeated backup-in-progress/update-menu blockage without `Backup_*` HTTP traffic
+  - Test 26 repeated the backup-in-progress warning from robot-local `@be/surprises-ota` without `Backup_*` HTTP traffic
 - Exit criteria:
   - no phantom "always has updates" behavior
   - one controlled update can be staged and delivered
@@ -369,6 +379,7 @@ Current release theme:
   - `jibo test 23` did not show the same decode failure pattern, but gallery yes/no turns still produced empty ASR
   - `jibo test 24` still had collapsed or empty transcripts in alarm/gallery paths, including `Sudden alarm.`, `I'm setting alarm for seven.`, empty clock value input, and empty gallery preview input
   - `jibo test 25` still had short-answer failures, but several were cloud turn-state issues now patched rather than pure STT failures
+  - `jibo test 26` had long no-`LISTEN` binary buffering and alarm-delete mishears now patched; remaining short-answer failures still need STT/noise work
   - current source now skips local whisper when buffered audio does not contain an Opus identification header
   - yes/no and alarm flows are especially sensitive to short or collapsed transcripts
 - Implementation notes: