Bugfix: Angular compiler TS2353 error: 'description' does not exist ...

Documentation for Sessions

🐛 Bugfix: Angular compiler TS2353 error: 'description' does not exist ...

Date: 2026-03-23
Time: 17:02:12 UTC
Session: gspace1-258.4
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Angular compiler TS2353 error: 'description' does not exist in type 'RoutineSuggestion' after plugin migration

Task: S258: Fix Angular compiler error after plugin migration

🎯 Decision Made

Chosen:

Three-part fix: (1) Revert awareness-data.service.ts imports to @libs-ai/chat-plugin-core (subagent used fragile relative path ../../../../chat-plugin-core/src/...). (2) Make RoutineSuggestion fields match the canonical stored shape (all required, since the service normalizes wire data). (3) Introduce local StoredAwarenessRoutine type for internal storage, keeping RoutineSuggestion as the public contract.

Options Considered:

  1. Make all RoutineSuggestion fields optional (wrong — loses type safety for consumers)
  2. Keep separate types for wire vs stored (chosen — clean separation)
  3. Remove RoutineSuggestion from chat-plugin-core entirely (breaks AwarenessStateProvider contract)

💭 Reasoning

Root cause chain: (A) Subagent modified awareness-data.service.ts to import RoutineSuggestion from chat-plugin-core via relative path — this worked for tsc but failed for the Angular compiler which has different module resolution. (B) The RoutineSuggestion interface had dismissed as optional in one version, required in another — structural type mismatch. (C) The service creates objects with description/profileId/confidence fields that must match the interface. Fix: ensure the interface in chat-plugin-core matches the normalized stored shape, use @libs-ai/chat-plugin-core path alias (not relative), and separate wire type from stored type.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation