Shipping update - 2026-02-15

Highlights

• Improved AI chat navigation clarity in last9/last9 by replacing generic deep-link text with context-aware destination labels, so users can tell where a result link will take them before clicking.
• Strengthened chat request assembly in last9/last9 to consistently include the latest user message plus client timestamp/timezone metadata, backed by targeted tests.
• Simplified AI tool-description architecture in last9/ai by removing client-side enrichment and relying on server-provided metadata, reducing duplication and drift risk.
• Clarified time-parameter defaults in last9/last9-mcp-server documentation so consumers can reason about behavior when start/end ranges are omitted.

User outcomes

• Users get clearer, more predictable AI-chat result navigation with destination-specific link labels instead of generic wording.
• Chat interactions are more dependable because request payload construction now preserves current user intent and time context.
• Teams integrating MCP capabilities can implement faster with fewer misunderstandings about default lookback windows and optional time inputs.
• Platform behavior is easier to trust during troubleshooting because time semantics are more explicit and consistently handled.

Technical wins

• Implemented fallback-safe deep-link labeling that prioritizes extracted source context, then tool-mapped destinations, then a generic default to maintain compatibility.
• Introduced a dedicated chat stream request-body builder and expanded test coverage around message assembly and client-time metadata.
• Removed redundant client-side prompt/tool-description loading paths and associated local markdown artifacts, consolidating responsibility in the MCP server.
• Standardized documentation language around default temporal windows across multiple tool areas, reducing cross-surface inconsistency.

Notes

• Sensitive/internal details have been redacted.
• Evidence basis: last9/ai#99, last9/last9-mcp-server#74, last9/last9#10579, last9/last9#10568.