Incorporate API spec v65 changes; release 1.0.3

.claude/skills/caredaily/SKILL.md

@@ -117,8 +117,8 @@ Import from `caredaily.apis` (or the subpackage):
   CloudConnectivity, CloudsIntegration, DeviceFiles, DeviceMeasurements,
   Devices, DeviceTypesAndParameters, EnergyManagement, Locations, PaidServices,
   ProfessionalMonitoring, RAG, Rules, SystemAndUserProperties, UserAccounts,
-  UserCommunication, Weather, Websocket
-- **`admin_api`** (`caredaily.apis.admin`): Billing, Challenges, AdminDevices,
+  UserCommunication, Websocket
+- **`admin_api`** (`caredaily.apis.admin`): Billing, AdminDevices,
   Firmware, Groups, AdminLocations, Narratives, Organizations, Reports, System,
   AdminTags, UserGroups, Users
 - **`bot_api`** (`caredaily.apis.bot`): Analytic, BotDeveloper, BotStore,

CHANGELOG.md

@@ -5,6 +5,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.0.3] - 2026-10-05
+
+### Added
+- Locations: `get_escalations`, `create_escalation`, and `update_escalation`
+  for the new `/cloud/json/escalations` endpoints
+- Locations: `escalation_id` filter on `get_narratives`; narratives can carry an
+  `escalationId` in `put_narrative`
+
+### Changed
+- API specs (cloud, admin, bots) updated to server API v65
+- DeviceTypesAndParameters: `add_default_rule` now requires `location_id`
+  (breaking)
+
+### Removed
+- Weather API class (all `/cloud/json/weather/...` endpoints removed from the spec)
+- Admin Challenges API class (`/admin/json/organizations/{organizationId}/challenges...`)
+- Bot Analytic: `get_challenge_participants` (`/analytic/admin/challenges/{challengeId}/participants`)
+- UserAccounts: `put_user_code`, `get_user_codes`, `delete_user_code` (`/cloud/json/userCodes`)
+- DeviceTypesAndParameters: `simple` and `organization_id` on `get_device_types`
+- PaidServices: `get_card` on `get_location_service_plans`
+
 ## [1.0.2] - 2026-09-11
 
 ### Added

CLAUDE.md

@@ -70,7 +70,7 @@ auth = cd.app_api(Authentication)   # also: cd.admin_api(...), cd.bot_api(...)
 Each factory (`app_api`, `admin_api`, `bot_api`) is an explicit if-chain over known classes and returns `None` for unknown types. **When adding a new API class**, you must (1) create it under the right `apis/` subpackage, (2) export it from `apis/__init__.py`, and (3) add it to the matching factory chain in `caredaily.py`.
 
 API subpackages:
-- `apis/app/` — user-facing APIs (Authentication, Locations, Devices, DeviceMeasurements, Rules, Weather, RAG, Websocket, ...)
+- `apis/app/` — user-facing APIs (Authentication, Locations, Devices, DeviceMeasurements, Rules, RAG, Websocket, ...)
 - `apis/admin/` — administrative APIs (System, Organizations, Users, Billing, Firmware, Reports, ...)
 - `apis/bot/` — bot developer APIs (BotDeveloper, BotStore, DeveloperTeams, Analytic, Execution)
 

docs/CARE_DAILY_APIS.md

@@ -37,15 +37,13 @@ Application-level APIs for standard user operations:
 - **SystemAndUserProperties** - System and user property management
 - **UserAccounts** - User account management
 - **UserCommunication** - User messaging and communication
-- **Weather** - Weather data integration
 - **Websocket** - WebSocket connections and real-time updates
 
 ### Administrative APIs (`admin/`)
 
 Administrative APIs requiring admin privileges:
 
 - **Billing** - Billing and subscription management
-- **Challenges** - Challenge management
 - **Devices** (AdminDevices) - Administrative device management
 - **Firmware** - Firmware management and updates
 - **Groups** - Organization group management