Add pizza yes-no wiring and Pegasus parser guardrails

OpenJibo/docs/development-plan.md

@@ -6,7 +6,7 @@ This document is the current working plan for the OpenJibo hosted cloud.
 
 The production lane is the `.NET` cloud in `src/Jibo.Cloud/dotnet`. The Node server remains the protocol oracle, capture harness, and fast reverse-engineering lab, but it is no longer the long-term hosted architecture.
 
-Day-to-day feature sequencing lives in [feature-backlog.md](feature-backlog.md). Live closeout checks live in [regression-test-plan.md](regression-test-plan.md). The `1.0.19` release shape is detailed in [release-1.0.19-plan.md](release-1.0.19-plan.md), while this file keeps the broader evidence and architecture context.
+Day-to-day feature sequencing lives in [feature-backlog.md](feature-backlog.md). Live closeout checks live in [regression-test-plan.md](regression-test-plan.md). The `1.0.19` release shape is detailed in [release-1.0.19-plan.md](release-1.0.19-plan.md), and the legacy-to-current architecture map is tracked in [system-diagram-alignment.md](system-diagram-alignment.md), while this file keeps the broader evidence and architecture context.
 
 ## Current Release Snapshot
 

OpenJibo/docs/feature-backlog.md

@@ -460,6 +460,27 @@ Current release theme:
   - what upload metadata must survive for gallery refresh
   - how to map this cleanly to Blob Storage
 
+### Next Up (`2026-05-06`): Dialog Parsing Expansion And Ambiguity Guardrails
+
+- Status: `ready`
+- Tags: `protocol`, `content`, `stt`, `docs`
+- Why now:
+  - this is the next queued `1.0.19` implementation slice after weather provider bring-up
+  - recent live runs showed phrases where trigger detection can interrupt full-utterance understanding
+  - phrase import work from Pegasus has already started for chitchat and should now expand to broader parsing boundaries
+- Scope:
+  - expand Pegasus-backed phrase coverage for question/command/assertion patterns
+  - add ambiguity guardrails for overlapping intents (date vs birthday, generic chat vs memory set/lookup, weather variants)
+  - preserve command-vs-question personality behavior and stock skill launch compatibility
+  - add focused tests for new phrase families and negative boundary cases
+- Exit criteria:
+  - ambiguous phrase handling is improved without regressions in existing `1.0.19` features
+  - phrase imports are documented and traceable to Pegasus parser sources
+  - test suite stays green and includes targeted parser-guardrail coverage
+- Tracking:
+  - [release-1.0.19-plan.md](release-1.0.19-plan.md)
+  - [system-diagram-alignment.md](system-diagram-alignment.md)
+
 ## Discovery Queue
 
 ### 12. Weather As Cloud Report Plus Local Presentation
@@ -661,7 +682,7 @@ For `1.0.19`:
 2. Expand memory-backed personal facts with tenant-scoped storage (beyond the first birthday/preferences foundation) - implemented
 3. Proactivity selector baseline with source-backed first offers - implemented
 4. Weather report-skill launch compatibility - implemented
-5. Dialog parsing expansion and ambiguity guardrails
+5. Dialog parsing expansion and ambiguity guardrails - queued next as of `2026-05-06`
 6. Holidays and seasonal personality behavior built on the new memory/proactivity foundation
 7. Durable memory persistence path (multi-tenant backing store)
 8. Update, backup, and restore proof

OpenJibo/docs/release-1.0.19-plan.md

@@ -105,9 +105,34 @@ The fifth delivered slice adds provider-backed weather content while preserving
 - simple location extraction is supported for phrasing like `what's the weather in Chicago tomorrow`
 - provider config supports appsettings and `OPENWEATHER_API_KEY` environment fallback for deployment
 
+## System Diagram Alignment Snapshot (`2026-05-06`)
+
+Legacy architecture (`system_diagram.png`) has been mapped to current OpenJibo cloud services so release execution stays anchored to:
+
+- where we were (Pegasus/Jibo cloud design intent)
+- where we are (current hosted `.NET` modular monolith)
+- where we are headed (durable memory, proactivity catalogs, parser depth, provider aggregation)
+
+Reference:
+
+- [system-diagram-alignment.md](system-diagram-alignment.md)
+
+## Next Queued Task (`2026-05-06`)
+
+Queued next `1.0.19` implementation task:
+
+- dialog parsing expansion and ambiguity guardrails
+
+Execution focus:
+
+- import additional Pegasus parser phrases/entities into intent handling where safe
+- reduce trigger-only captures that drop the rest of the utterance
+- preserve command-vs-question personality split and local skill payload compatibility
+- add focused tests for new phrase families and ambiguity boundaries
+
 ## Next Slices
 
-1. Dialog parsing expansion (more phrase variants, ambiguity handling, and transcript-to-intent guardrails)
+1. Dialog parsing expansion (queued next as of `2026-05-06`; more phrase variants, ambiguity handling, and transcript-to-intent guardrails)
 2. Holidays and seasonal personality slice beyond pizza day (time-scoped content backed by memory/proactivity path)
 3. Durable memory persistence path (swap in provider-backed multi-tenant storage while preserving behavior contracts)
 4. Update/backup/restore end-to-end proof (operator-run and documented)

OpenJibo/docs/system-diagram-alignment.md

@@ -0,0 +1,104 @@
+# System Diagram Alignment
+
+## Purpose
+
+This document maps the legacy Pegasus/Jibo cloud `system_diagram.png` architecture to the current OpenJibo `1.0.19` cloud.
+
+Use it to keep release planning grounded in three views:
+
+- where we were (legacy design intent)
+- where we are (current hosted `.NET` implementation)
+- where we are headed (next architecture slices)
+
+As-of date: `2026-05-06`
+
+## Diagram Inputs
+
+- Legacy system architecture: `C:\Projects\jibo\pegasus\resources\system_diagram.png`
+- Legacy generic skill scaffold: `C:\Projects\jibo\pegasus\packages\template-skill\docs\TemplateSkill.png`
+
+## Template Skill Verdict
+
+The template-skill diagram is a generic scaffold, not a production behavior contract.
+
+Evidence:
+
+- `C:\Projects\jibo\pegasus\packages\template-skill\src\TemplateSkill.ts` is a starter graph (`Intent Split` -> `Do MIM` -> `Complete` -> `Done`).
+- `C:\Projects\jibo\pegasus\packages\template-skill\src\nodes\MemoSplitNode.ts` uses placeholder memo validation (`SomeThing`).
+
+Conclusion: do not treat template-skill flow as a port target. Treat it as a shape reference only.
+
+## System Diagram Mapping
+
+| Legacy block | OpenJibo `1.0.19` equivalent | Current gap / opportunity |
+| --- | --- | --- |
+| `Auth` | [JiboCloudProtocolService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboCloudProtocolService.cs) (`CreateHubToken`, `CreateAccessToken`, account handlers) | move from in-memory/session stubs to durable tenant/account identity services |
+| `Loop` | [JiboCloudProtocolService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboCloudProtocolService.cs) (`HandleLoop`) + [InMemoryCloudStateStore.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Infrastructure/Persistence/InMemoryCloudStateStore.cs) | richer loop/member lifecycle and onboarding flows |
+| `Hub` | [JiboWebSocketService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboWebSocketService.cs) + [WebSocketTurnFinalizationService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/WebSocketTurnFinalizationService.cs) | split hub responsibilities into clearer protocol, routing, and orchestration boundaries |
+| `ASR Handler` | STT strategy selection in [WebSocketTurnFinalizationService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/WebSocketTurnFinalizationService.cs) + DI in [ServiceCollectionExtensions.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Infrastructure/DependencyInjection/ServiceCollectionExtensions.cs) | short-turn reliability, managed STT comparison, and better low-signal/noise handling |
+| `Parser / Robust Parser` | rule-based intent resolution in [JiboInteractionService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboInteractionService.cs) + focused state machines (personal report/chitchat) | deeper phrase import from Pegasus intents/entities plus ambiguity guardrails |
+| `Skill Router` | [JiboInteractionService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboInteractionService.cs) decision switch and local skill payload shaping | external skill routing config and safer declarative intent mapping |
+| `Proactivity Selector` | weighted candidate selection in [JiboInteractionService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/JiboInteractionService.cs) + pending-offer session state in [WebSocketTurnFinalizationService.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Application/Services/WebSocketTurnFinalizationService.cs) | externalized proactivity catalog, cooldown policy, and broader category coverage |
+| `Skill Registry` | implicit in current code/routing | formal registry abstraction for local/cloud capabilities and manifest metadata |
+| `History` | tenant-scoped memory store in [InMemoryPersonalMemoryStore.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Infrastructure/Persistence/InMemoryPersonalMemoryStore.cs) | durable multi-tenant persistence and history timeline/query support |
+| `Lasso` provider aggregation | partial provider integration via weather provider wiring in [ServiceCollectionExtensions.cs](../src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Infrastructure/DependencyInjection/ServiceCollectionExtensions.cs) | full aggregation service for weather/news/calendar/knowledge inputs |
+| `Proactivity Catalog` | in-code candidate lists/weights | explicit catalog service with tuned weights and operator controls |
+| `Audio Logs` | file telemetry sinks in infrastructure telemetry | hosted indexed capture/retention for multi-operator analysis |
+
+## Where We Were
+
+Legacy cloud design was service-oriented around:
+
+- hub orchestration
+- parser robustness
+- skill routing
+- proactivity selection
+- history/memory and provider aggregation
+
+It emphasized a personality-rich surface while still being operationally observable.
+
+## Where We Are
+
+OpenJibo `1.0.19` is a functional hosted `.NET` modular monolith with:
+
+- protocol compatibility paths for HTTP and websocket robot flows
+- deterministic intent routing plus state-machine slices
+- tenant-scoped memory foundation
+- first proactivity baseline
+- first external weather provider integration
+
+This is the right shape for rapid parity plus safe incremental growth.
+
+## Where We Are Headed
+
+Near-term architecture evolution should preserve current shipping velocity:
+
+1. Expand parser coverage and ambiguity guardrails from Pegasus phrase corpora.
+2. Externalize proactivity policy and category catalogs.
+3. Move memory from in-memory to durable multi-tenant backing stores.
+4. Add stronger observability around STT, parser decisions, and follow-up turn state.
+5. Build a focused aggregation layer (Lasso-like) for multi-provider content.
+
+## Charm Preservation Rules
+
+To keep Jibo's charm while modernizing the platform:
+
+- keep MIM/ESML and expressive animation hooks as first-class outputs
+- keep deterministic command-vs-question behavior for personality reliability
+- layer richer provider data behind stable personality and gesture patterns
+- prefer small source-backed slices over broad rewrites
+
+## Queued Next `1.0.19` Task
+
+The next queued implementation task is:
+
+- `Dialog parsing expansion and ambiguity guardrails`
+
+Tracking anchors:
+
+- [release-1.0.19-plan.md](release-1.0.19-plan.md)
+- [feature-backlog.md](feature-backlog.md)
+
+Primary objective:
+
+- import Pegasus parser intent phrases/entities to improve intent confidence while preserving command-vs-question personality behavior.