codeapp-js 1.0.1 → 1.1.0

package/AI/skills/autoreview/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: autoreview
+description: "Use when: reviewing Power Automate flows with the AutoReview connector, including metadata, JSON review output, file-based review output, diagrams, or the raw AutoReview HTTP endpoint."
+---
+
+# AutoReview Connector Guide
+
+Do not use CLI PAC commands to get connecctor models or services,
+use `codeApp/dist/connectors/autoreview.js` as the repo source of truth.
+
+
+## power.config.json
+
+Always read the current `power.config.json` before editing it.
+
+Ensure `"id": "/providers/Microsoft.PowerApps/apis/shared_autoreview"` exists.
+
+```json
+"connectionReferences": {
+  "autoreview": {
+      "id": "/providers/Microsoft.PowerApps/apis/shared_autoreview",
+      "displayName": "AutoReview",
+      "dataSources": [
+        "autoreview"
+      ],
+      "dataSets": {},
+      "authenticationType": null,
+      "sharedConnectionId": null
+    }
+}
+```
+
+Rules for editing `power.config.json`:
+
+- Preserve existing keys such as `sharedConnectionId`, `authenticationType`, and other working connection metadata.
+- If the app uses Dataverse environment variables, also load the environment-variables skill.
+
+## Core Rule
+
+Prefer the latest exported actions and avoid older superseded variants.
+
+## Action Surface
+
+- `GET_info()`
+- `POST_http(path, body)`
+- `POST_json(flowProperties, configs)`
+- `POST_file_V2(flowProperties, configs)`
+- `POST_diagram(flowProperties, configs)`
+
+## When To Use Each Action
+
+- `GET_info()` returns connector metadata, version details, and service information.
+- `POST_http(...)` is the raw escape hatch for AutoReview endpoints.
+- `POST_json(...)` returns structured JSON review output for a flow.
+- `POST_file_V2(...)` returns generated review/report files using the newer file action.
+- `POST_diagram(...)` returns a rendered flow diagram artifact.
+
+## Practical Guidance
+
+- Prefer `POST_json(...)` when the app needs machine-readable review output.
+- Prefer `POST_file_V2(...)` instead of the older file action.
+- Use `POST_diagram(...)` when the user explicitly wants a visual flow representation.
+- Only fall back to `POST_http(...)` when there is no dedicated action for the output you need.
+
+## Debugging
+
+- If review output looks incomplete, confirm the flow properties payload includes the definition, owner, environment, and flow ID fields the connector expects.
+- If you need a file artifact, use `POST_file_V2(...)`, not the legacy file action.
+- Treat `POST_http(...)` as an escape hatch, not the default integration path.

package/AI/skills/connections/SKILL.md

@@ -5,7 +5,7 @@ description: "Use when: wiring connector-backed Power Apps Code Apps, validating
 
 # Connections Guide
 
-Use this skill for the shared rules that apply across the handwritten connector helpers in `dev files/`.
+Use this skill for the shared rules that apply across the handwritten connector helpers in `dev files/connectors/`.
 
 ## Core Rules
 
@@ -13,7 +13,7 @@ All authentication is handled by the Power Apps runtime and the connector client
 
 Do:
 - Keep connector calls inside the wrapper helper for that connector.
-- Reuse the repo's helper patterns such as `unwrapResult` and the candidate data-source retry logic in `codeapp-helper.js`.
+- Reuse the repo's helper patterns such as `unwrapResult` and the candidate data-source retry logic in `codeapp.js`.
 - Treat the helper file as the repo-local source of truth for public function names, default versions, and parameter mapping.
 - Validate `power.config.json` `dataSources` names against the wrapper before changing them.
 
@@ -25,7 +25,7 @@ Don't:
 
 ## Wrapper Patterns
 
-- `codeapp-helper.js` exposes `execConnectorOpWithCandidates(...)` for wrappers that must retry multiple `dataSources` names.
+- `codeapp.js` exposes `execConnectorOpWithCandidates(...)` for wrappers that must retry multiple `dataSources` names.
 - Some wrappers use exact inline `apis` metadata (`outlook.js`, `office365users.js`, `Teams.js`, `Jira.js`, `AzureKeyvault.js`).
 - Some wrappers intentionally rely on runtime-resolved connector operations and focus on stable public helper names (`office365groups.js`).
 - Prefer the existing wrapper over rebuilding a connector client from scratch unless the wrapper is missing the operation entirely.
@@ -34,7 +34,7 @@ Don't:
 
 The raw HTTP helper signatures are not interchangeable.
 
-- Outlook, Office 365 Users, and Office 365 Groups map friendly inputs to connector fields like `Uri`, `Method`, `Body`, `ContentType`, and `CustomHeader1..5`.
+- Office 365 Outlook, Office 365 Users, and Office 365 Groups map friendly inputs to connector fields like `Uri`, `Method`, `Body`, `ContentType`, and `CustomHeader1..5`.
 - SharePoint and Teams currently pass `method`, `uri`, `headers`, and `body` directly.
 
 Check the specific wrapper before copying a raw-request pattern between connectors.

package/AI/skills/dataverse/SKILL.md

@@ -9,7 +9,7 @@ description: "Use when: building or debugging Dataverse CRUD in a Power Apps Cod
 
 ## power.config.json
 
-For the helper in `dev files/codeapp-helper.js`, Dataverse CRUD depends on `databaseReferences.default.cds.dataSources`.
+For the helper in `dev files/codeapp.js`, Dataverse CRUD depends on `databaseReferences.default.cds.dataSources`.
 
 ```json
 {
@@ -30,6 +30,8 @@ For the helper in `dev files/codeapp-helper.js`, Dataverse CRUD depends on `data
 - `entitySetName` is the plural OData collection name.
 - `logicalName` is the singular logical name.
 - Every Dataverse table used by the app must be present here.
+- Schemas are often stored in the `agent` folder, if they are not check `.power\schemas` folder. If required and missing use `pac code add-data-source -a dataverse -t <tableName>` to generate the schema in  `.power\schemas` folder.
+- if schema found copy it to `agent` folder and edit the `.power/schemas/` folder.
 - Do not add unbound actions like `WhoAmI` or `GrantAccess` to `dataSources`.
 
 The helper does not require a separate Dataverse `connectionReferences` entry for CRUD or `callUnboundAction`.
@@ -57,7 +59,7 @@ Use `registerTable(tableName, primaryKey)` only when you need to add a table at
 
 ## CRUD Surface
 
-`codeapp-helper.js` exports:
+`codeapp.js` exports:
 
 - `createItem(tableName, primaryKey, record)`
 - `getItem(tableName, primaryKey, id, select)`

package/AI/skills/frontend-design/SKILL.md

@@ -1,34 +1,46 @@
 ---
 name: frontend-design
-description: "Use when: designing or restyling pages, components, mockups, dashboards, or app UIs in this repo. Favor distinctive frontend work over generic defaults."
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
 ---
 
-# Frontend Design Guide
+# Frontend Design Skill
 
-Use this skill to keep UI work intentional, distinctive, and production-grade.
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
 
 ## Design Thinking
 
-Before coding:
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+
+- **Purpose:** What problem does this interface solve? Who uses it?
+- **Tone:** Pick an extreme: modern minimal, maximalist chaos, Microsoft's Fluent design language, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints:** Technical requirements (framework, performance, accessibility).
+- For CAP code apps, treat workspace configuration and loaded skills as the source of truth for technical constraints. If `power.config.json` or the agent prompt already fixes the stack, connector, or app name, do not ask the user to restate them.
+- **Differentiation:** What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL:** Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code in the project's required stack. Default to plain HTML/CSS/JS when the workspace instructions or agent prompt do not explicitly require a framework. Do not ask the user to choose React, Vue, or another framework unless the project requirements are genuinely ambiguous.
+
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
 
-- Understand the purpose, audience, and constraints.
-- Commit to a clear aesthetic direction instead of blending safe defaults.
-- Treat the existing workspace configuration and loaded skills as the source of truth for stack and app constraints.
-- Default to plain HTML, CSS, and JS when the repo does not require a framework.
+## Frontend Aesthetics Guidelines
 
-## Aesthetic Rules
+Focus on:
 
-- Choose fonts with character. Avoid default system-looking results.
-- Use a deliberate palette with clear hierarchy and CSS variables.
-- Build atmosphere with gradients, textures, overlays, or shape systems instead of flat backgrounds.
-- Use motion for a few strong moments rather than generic micro-animations everywhere.
-- Make layouts feel designed, not template-generated.
+- **Typography:** Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme:** Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion:** Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Only use framework-specific animation libraries when the project already uses that framework. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition:** Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details:** Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
 
-## Avoid
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
 
-- Generic AI-looking typography and spacing.
-- Purple-on-white gradient defaults.
-- Cookie-cutter cards and dashboards with no point of view.
-- Asking the user to pick a framework when the repo already implies one.
+IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
 
-Push for work that feels specific to the app instead of interchangeable.
+Remember: LLMs are capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/AI/skills/keyvault/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: keyvault
+description: "Use when: building or debugging Azure Key Vault connector flows in a Power Apps Code App, including keys, secrets, metadata, or encryptData and decryptData helpers."
+---
+
+# Azure Key Vault Connector Guide
+
+> Agent limitation: do not use CLI commands directly from chat for Key Vault connector setup. Use the built-in Auth, Sync Connections, and Deploy buttons instead.
+
+## Core Rule
+
+The wrapper in `codeApp/dist/connectors/azureKeyvault.js` is the repo-local source of truth for public helper names, supported operations, and parameter normalization.
+
+- It retries the data-source names `keyvault`, `KeyVault`, `azurekeyvault`, `azureKeyVault`, and `AzureKeyVault`.
+- It includes inline metadata for the key, secret, metadata, and encrypt/decrypt actions it supports.
+- Vault selection is handled by the Power Apps connector connection, not by passing a vault name into each helper call.
+
+## First Questions To Ask
+
+Ask only what is needed to choose the right helper and confirm the right connection:
+
+1. Does the app need keys, secrets, or both?
+2. Does it need metadata only, the secret value itself, or encryption/decryption operations?
+3. Is a specific key version or secret version required?
+4. Does `power.config.json` already contain a Key Vault connection reference?
+5. Is the existing Key Vault connection already pointing at the correct vault?
+
+## power.config.json
+
+Prefer a Key Vault connection reference whose `dataSources` array contains `keyvault`.
+
+```json
+{
+  "connectionReferences": {
+    "keyvaultConnection": {
+      "id": "/providers/Microsoft.PowerApps/apis/shared_keyvault",
+      "displayName": "Azure Key Vault",
+      "dataSources": ["keyvault"],
+      "dataSets": {}
+    }
+  }
+}
+```
+
+Rules for editing `power.config.json`:
+
+- Preserve existing keys such as `sharedConnectionId`, `authenticationType`, and working connection metadata.
+- Prefer `keyvault` as the exposed data-source name even though the wrapper retries additional casing variants.
+- The connection-reference object key can vary by environment, but the wrapper-facing data source should stay aligned.
+- No Dataverse tables are required for Key Vault-only apps.
+- Do not invent custom top-level config keys for vault auth or tokens.
+
+## Public Helper Surface
+
+The wrapper exports:
+
+- `callKeyVaultOperation(operationName, parameters)`
+- `listKeys(oOptions)`
+- `listKeyVersions(keyName)`
+- `getKeyMetadata(keyName)`
+- `getKeyVersionMetadata(keyName, keyVersion)`
+- `encryptData(keyName, inputOrOptions)`
+- `encryptDataWithVersion(keyName, keyVersion, inputOrOptions)`
+- `decryptData(keyName, inputOrOptions)`
+- `decryptDataWithVersion(keyName, keyVersion, inputOrOptions)`
+- `getSecret(secretName)`
+- `listSecrets(oOptions)`
+- `listSecretVersions(secretName)`
+- `getSecretMetadata(secretName)`
+- `getSecretVersionMetadata(secretName, secretVersion)`
+- `getSecretVersion(secretName, secretVersion)`
+
+## Supported Connector Actions
+
+The wrapper currently maps to these connector actions:
+
+- `ListKeys`
+- `ListKeyVersions`
+- `GetKeyMetadata`
+- `GetKeyVersionMetadata`
+- `EncryptData`
+- `EncryptDataWithVersion`
+- `DecryptData`
+- `DecryptDataWithVersion`
+- `GetSecret`
+- `ListSecrets`
+- `ListSecretVersions`
+- `GetSecretMetadata`
+- `GetSecretVersionMetadata`
+- `GetSecretVersion`
+
+## Important Wrapper Behavior
+
+- `encryptData(...)` and `decryptData(...)` automatically switch to the versioned connector action when `keyVersion` is supplied in the options object.
+- Encryption and decryption helpers accept either positional arguments or an options object.
+- `operationInput` is normalized from shapes like `operationInput`, `input`, or `body`.
+- For encryption, the wrapper looks for payload values such as `rawData`, `data`, `raw`, `plainText`, `plaintext`, or `value`.
+- For decryption, the wrapper looks for payload values such as `encryptedData`, `cipherText`, `ciphertext`, `data`, or `value`.
+- The default algorithm is `RSA-OAEP-256` when none is supplied.
+- Key and secret helpers accept object forms such as `{ keyName, version }` or `{ secretName, secretVersion }`.
+- The wrapper accepts `apiVersion`-shaped arguments on some secret helpers for compatibility, but the current implementation does not pass `apiVersion` through to the connector call.
+
+## Usage Rules
+
+- Use `listKeys(...)` and `listSecrets(...)` for discovery.
+- Use metadata helpers when the app only needs properties, status, or version information.
+- Use `getSecret(...)` or `getSecretVersion(...)` only when the app actually needs the secret value.
+- Prefer `encryptData(...)` and `decryptData(...)` over raw calls when the wrapper already supports the operation.
+- If the app requires an exact key version, pass `keyVersion` explicitly or call the version-specific helper.
+- Do not add manual auth headers or direct Key Vault REST calls when the connector helper already exists.
+
+## Raw Calls
+
+Use `callKeyVaultOperation(operationName, parameters)` only when a dedicated helper does not already exist.
+
+Do not invent:
+
+- connector action names
+- `operationInput` field names
+- raw Key Vault REST paths
+- manual `api-version` query handling in app code
+- manual auth headers or token acquisition
+
+## Debugging
+
+- If the failure mentions a missing connection reference, confirm `power.config.json` exposes a Key Vault connection and prefer `dataSources: ["keyvault"]`.
+- If the app hits the wrong vault, the underlying Power Apps connection is likely pointing at a different vault. The wrapper does not choose vaults per request.
+- If encryption or decryption fails with input-shape errors, verify the payload resolves to `operationInput` with `rawData` or `encryptedData` after normalization.
+- If a version-specific operation is expected but the unversioned action runs, confirm `keyVersion` was actually supplied.
+- If changing `apiVersion` appears to do nothing, that is expected with the current wrapper because it does not send `apiVersion` through to the connector.
+- If a raw call fails but a dedicated helper exists, switch back to the helper before debugging deeper connector behavior.
+
+## Summary Rules
+
+- Treat `codeApp/dist/connectors/azureKeyvault.js` as the public API contract.
+- Prefer `keyvault` as the configured data-source name.
+- Use dedicated helpers for keys, secrets, and crypto before raw operations.
+- Remember that vault selection lives in the connector connection, not in helper parameters.
+- Do not rely on `apiVersion` arguments to change connector behavior unless the wrapper is updated.

package/AI/skills/office365-groups/SKILL.md

@@ -5,57 +5,78 @@ description: "Use when: building or debugging Office 365 Groups connector flows
 
 # Office 365 Groups Connector Guide
 
-> Agent limitation: do not use CLI commands directly from chat for Office 365 Groups setup. Use the built-in Sync Connections and Deploy buttons instead.
+Do not use CLI PAC commands to get connecctor models or services,
+use `codeApp/dist/connectors/office365groups.js` as the repo source of truth.
 
-## Core Rule
+## power.config.json
 
-The wrapper in `dev files/office365groups.js` is the repo-local source of truth.
+Always read the current `power.config.json` before editing it.
 
-- It retries both `office365groups` and `Office365Groups`.
-- It keeps the public helper surface stable even though the raw connector operations are runtime-resolved.
-- Do not replace it with made-up placeholder paths copied from generic examples.
+Ensure `"id": "/providers/Microsoft.PowerApps/apis/shared_office365"` exists.
 
-## power.config.json
+```json
+"connectionReferences": {
+  "office365groups": {
+    "id": "/providers/Microsoft.PowerApps/apis/shared_office365groups",
+    "displayName": "Office 365 Groups",
+    "dataSources": [
+      "office365groups"
+    ],
+    "authenticationType": null,
+    "sharedConnectionId": null,
+    "dataSets": {}
+  }
+}
+```
+
+Rules for editing `power.config.json`:
 
-Prefer a connection reference whose `dataSources` array includes `office365groups`.
+- Preserve existing keys such as `sharedConnectionId`, `authenticationType`, and other working connection metadata.
+- If the app uses Dataverse environment variables, also load the environment-variables skill.
 
-Older apps may still use `Office365Groups`; the wrapper retries both.
+## Core Rule
 
-## Public Helper Surface
+Prefer the exported helper layer instead of wiring raw connector operations directly in app code.
 
-The wrapper exports:
+## Action Helper Surface
 
+- `callGroupsOperation(operationName, parameters)`
+- `openGroupsHttpRequest(options)`
 - `listMyGroups(options)`
 - `listOwnedGroups(options)`
 - `listGroups(options)`
 - `listGroupMembers(groupId, options)`
-- `onGroupMembershipChange(groupId, options)`
 - `addMemberToGroup(userUpn, groupId)`
 - `removeMemberFromGroup(userUpn, groupId)`
 - `createGroupEvent(groupId, options)`
 - `updateGroupEvent(eventId, options, groupId)`
 - `deleteGroupEvent(eventId, groupId)`
-- `onNewGroupEvent(groupId)`
 - `listDeletedGroups()`
 - `restoreDeletedGroup(groupId)`
 - `listDeletedGroupsByOwner(userId)`
-- `openGroupsHttpRequest(options)`
 
-## Important Wrapper Behavior
+## Latest Action Defaults
+
+- `listMyGroups({ version: 1|2|3 })` routes to `ListOwnedGroups`, `ListOwnedGroups_V2`, or `ListOwnedGroups_V3`.
+- `listGroups(...)` supports `$filter`, `$top`, `skipToken`, `nextLink`, and `skip` aliases.
+- `createGroupEvent(...)` defaults to `CreateCalendarEventV2`.
+- `deleteGroupEvent(...)` uses `CalendarDeleteItem_V2`.
+- `openGroupsHttpRequest(...)` can target `HttpRequest` or `HttpRequestV2` through `version`, `useV2`, or `operationName`.
 
-- `listMyGroups({ version: 1|2|3 })` switches between `ListOwnedGroups`, `ListOwnedGroups_V2`, and `ListOwnedGroups_V3`.
-- `listGroups(...)` supports `$filter`, `$top`, `skipToken`, `nextLink`, and compatibility aliases like `skip`.
-- Event helpers accept flexible options objects and normalize event payloads for the connector.
-- `openGroupsHttpRequest(...)` maps friendly inputs to connector fields like `Uri`, `Method`, `Body`, `ContentType`, and `CustomHeader1..5`.
-- `openGroupsHttpRequest(...)` can target `HttpRequest` or `HttpRequestV2` with `version` or `useV2`.
+## HTTP Escape Hatch
 
-## Raw Calls
+`openGroupsHttpRequest(...)` maps friendly inputs to connector fields:
 
-Use `callGroupsOperation(operationName, parameters)` only when a high-level helper does not exist.
+- `uri` -> `Uri`
+- `method` -> `Method`
+- `body` -> `Body`
+- `contentType` -> `ContentType`
+- `customHeaders[0..4]` -> `CustomHeader1..5`
 
-Do not bypass the wrapper with direct Graph calls for operations already covered by the connector.
+Use this only when no helper exists for the action you need.
 
 ## Debugging
 
-- If the failure is `Connection reference not found`, confirm the app exposes either `office365groups` or `Office365Groups` in `power.config.json`.
-- If an HTTP request fails, verify the wrapper is sending connector-style fields rather than raw fetch-style headers.
+- Keep helper names stable and widen alias support instead of adding another parallel wrapper.
+- If group pagination fails, pass `skipToken` or `nextLink`, not a raw `$skip` query.
+- If HTTP requests fail, verify you are sending connector-style fields through `openGroupsHttpRequest(...)`.

package/AI/skills/office365-outlook/SKILL.md

@@ -5,48 +5,79 @@ description: "Use when: building or debugging Outlook connector flows in a Power
 
 # Office 365 Outlook Connector Guide
 
-> Agent limitation: do not use CLI commands directly from chat for Outlook setup. Use the built-in Sync Connections and Deploy buttons instead.
+Do not use CLI PAC commands to get connecctor models or services,
+use `codeApp/dist/connectors/office365outlook.js` as the repo source of truth.
 
-## Core Rule
 
-The wrapper in `dev files/outlook.js` is the repo-local source of truth, and `dev files/outlook-helper-reference.md` documents its accepted aliases.
+## power.config.json
+
+Always read the current `power.config.json` before editing it.
+
+Ensure `"id": "/providers/Microsoft.PowerApps/apis/shared_office365"` exists.
+
+```json
+"connectionReferences": {
+  "office365outlook": {
+    "id": "/providers/Microsoft.PowerApps/apis/shared_office365",
+    "displayName": "Office 365 Outlook",
+    "dataSources": [
+      "office365"
+    ],
+    "authenticationType": null,
+    "sharedConnectionId": null,
+    "dataSets": {}
+  }
+}
+```
 
-- It retries `office365outlook`, `Office365Outlook`, and `office365`.
-- It includes inline metadata for the operations the wrapper exposes.
-- Many helpers choose the operation version automatically.
+Rules for editing `power.config.json`:
+
+- Preserve existing keys such as `sharedConnectionId`, `authenticationType`, and other working connection metadata.
+- If the app uses Dataverse environment variables, also load the environment-variables skill.
+
+## Core Rule
 
-Prefer `office365` in `power.config.json`, while keeping the wrapper's candidate names intact.
+Prefer the exported helper layer instead of hard-coding raw operation names in app code.
 
-## Public Helper Surface
+The helper layer defaults to the latest action versions where the connector exposes them.
 
-The wrapper exports helpers for:
+## Action Helper Surface
 
-- Mail: `sendEmail`, `listEmails`, `getEmail`, `forwardEmail`, `replyToEmail`, `moveEmail`, `deleteEmail`, `draftEmail`, `updateDraftEmail`, `sendDraftEmail`, `markEmailAsRead`, `updateEmailFlag`, `getEmailAttachment`, `assignOutlookCategory`, `assignOutlookCategoryBulk`
+- Mail: `sendEmail`, `listEmails`, `getEmail`, `forwardEmail`, `replyToEmail`, `moveEmail`, `deleteEmail`, `draftEmail`, `updateDraftEmail`, `sendDraftEmail`, `markEmailAsRead`, `updateEmailFlag`, `getEmailAttachment`
+- Categories: `listOutlookCategories`, `assignOutlookCategory`, `assignOutlookCategoryBulk`
 - Shared mailbox: `sendFromSharedMailbox`
-- Calendar: `createEvent`, `listEvents`, `editEvent`, `deleteEvent`, `listCalendars`, `getEvent`, `getCalendarView`, `respondToEventInvite`, `findMeetingTimes`, `listRoomLists`, `listRooms`, `listRoomsInRoomList`, `setAutomaticReplies`, `getMailTips`
+- Calendar: `createEvent`, `listEvents`, `editEvent`, `deleteEvent`, `listCalendars`, `getEvent`, `getCalendarView`, `respondToEventInvite`, `findMeetingTimes`, `setAutomaticReplies`, `getMailTips`, `listRoomLists`, `listRooms`, `listRoomsInRoomList`
 - Contacts: `listContactFolders`, `listContacts`, `getContact`, `createContact`, `updateContact`, `deleteContact`
 - Advanced: `callOutlookOperation`, `callOutlookHttpRequest`, `manageOutlookEmails`, `manageOutlookMeetings`, `manageOutlookContacts`
 
-## Important Wrapper Defaults
+## Latest Action Defaults
 
-- `sendEmail(...)` uses `SendEmailV2` unless `isHtml === false`, in which case it uses the legacy plain-text action.
-- `listEmails(...)` defaults to version 3, folder `Inbox`, and `top: 10`.
-- `replyToEmail(...)` uses `ReplyToV3` unless `isHtml === false`.
-- `getEmail(...)` defaults to the V2 action.
+- `sendEmail(...)` defaults to `SendEmailV2` and only falls back to plain-text `SendEmail` when `isHtml === false`.
+- `listEmails(...)` defaults to `GetEmailsV3`, folder `Inbox`, and `top: 10`.
+- `getEmail(...)` defaults to `GetEmailV2`.
+- `replyToEmail(...)` defaults to `ReplyToV3` and only falls back to `ReplyToV2` for plain-text replies.
+- `moveEmail(...)` uses `MoveV2`.
 - `createEvent(...)`, `listEvents(...)`, and `editEvent(...)` use the V4 calendar actions.
-- `markEmailAsRead(...)` uses the V3 action unless the caller explicitly requests the older legacy pattern.
+- `deleteEvent(...)` uses `CalendarDeleteItem_V2`.
+- `findMeetingTimes(...)` uses `FindMeetingTimes_V2`.
+- `setAutomaticReplies(...)` defaults to `SetAutomaticRepliesSetting_V2`.
+- `getMailTips(...)` defaults to `GetMailTips_V2` when a request body is supplied.
+- Contact helpers use the V2 contact actions.
 
-## Raw HTTP Calls
+## HTTP Escape Hatch
 
-`callOutlookHttpRequest(...)` expects the connector-style field mapping used by the wrapper.
+`callOutlookHttpRequest(...)` maps friendly inputs to connector fields:
 
-- Pass `uri`, `method`, `body`, `contentType`, and `customHeaders`.
-- The wrapper maps them to `Uri`, `Method`, `Body`, `ContentType`, and `CustomHeader1..5`.
+- `uri` -> `Uri`
+- `method` -> `Method`
+- `body` -> `Body`
+- `contentType` -> `ContentType`
+- `customHeaders[0..4]` -> `CustomHeader1..5`
 
-Do not reuse the SharePoint or Teams raw HTTP pattern here.
+Use this only when no helper exists for the action you need.
 
 ## Debugging
 
-- If the failure mentions `Connection reference not found`, verify `power.config.json` exposes one of the wrapper's candidate data-source names.
-- If a versioned mail or calendar call behaves unexpectedly, check the wrapper default before changing the raw operation name.
-- For alias-heavy helpers, consult `dev files/outlook-helper-reference.md` before adding new parameter mapping logic.
+- If a mail helper behaves differently than expected, check its default version before changing the raw connector action.
+- If HTTP calls fail, verify you are passing connector-style fields through `callOutlookHttpRequest(...)`, not fetch-style options.
+- Keep helper names stable and widen alias support instead of introducing another parallel wrapper.