Changelog

ParseActionBlocks now falls back to ExtractBareIntentJson when no

[ACTION] wrapper tags are found, recovering intent JSON that the AI

emits without the required tags. The fallback only triggers when the

primary parser found nothing, preventing double-extraction.

ActionFormatHeader now explicitly warns against JSON document objects

in content/description text slots.

Visibility changes: ParseActionBlocks, ExtractBareIntentJson,

ParsedAction, and FlattenSlotValue are now internal (testable via

InternalsVisibleTo).

6 new xUnit tests cover bare JSON recovery, surrounding prose

stripping, non-intent JSON rejection, multiple intents, and

malformed JSON handling.

When the user asks a question while viewing an entity, the RAG query is

now augmented with semantic keywords extracted from the entity's JSON

(job_title, company_name, department, tags, contexts, etc.). This causes

the embedding search to surface semantically related items across plugins

without any changes to the RAG service or Rust embedding layer.

The intent prompt had no examples or guidance for calendar.list_events,

so the LLM didn't know how to resolve colloquial time expressions like

"this week" or "coming up this month" into proper date ranges.

• Add date range resolution section to Large tier with two categories:

strict period queries ("this week" = Mon–Sun) and forward-looking

queries ("coming up" = NOW + 30 day lookahead, no period clipping)

• Forward-looking language ("coming up", "upcoming", "do I have any")

starts from NOW and uses 30-day window — doesn't clip to month/week

boundaries so results naturally span across periods

• Add calendar.list_events examples to all 3 tiers showing "what's on

my calendar this week" and "any lunches coming up this month" (with

search_query slot and 30-day end_date)

• Include current time (HH:mm) in date context line so the LLM can set

start_date to NOW for forward-looking queries

• Add helper methods: ThisWeekStart, ThisWeekEnd, ThisMonthStart,

ThisMonthEnd, NowTimestamp, Lookahead30

The intent prompt had no examples or guidance for calendar.list_events,

so the LLM didn't know how to resolve colloquial time expressions like

"this week" or "coming up this month" into proper date ranges.

• Add date range resolution section to Large tier with concrete examples:

"this week" → Monday–Sunday, "this month" → 1st–last day, "coming up"

→ start from NOW (current time) to exclude past events

• Add calendar.list_events examples to all 3 tiers (Small, Medium, Large)

showing "what's on my calendar this week" and "any lunches coming up

this month" (with search_query slot)

• Include current time (HH:mm) in date context line so the LLM can set

start_date to NOW for forward-looking queries

• Add helper methods: ThisWeekStart, ThisWeekEnd, ThisMonthStart,

ThisMonthEnd, NowTimestamp for generating example date boundaries