Add server-logic, cloud-flow, integrate-backend skills and plugin version check - #57

Based on testing feedback, update the integrate-serverlogic skill:

- Server logic files now live in .powerpages-site/server-logic/<name>/
  with two files: <name>.js (code) and <name>.serverlogic.yml (metadata)
- .powerpages-site folder is now a mandatory prerequisite (not optional)
- YAML metadata includes id (UUID), web roles, display name, description
  with alphabetically sorted fields to match PAC CLI conventions
- Phase 5 now reads web roles from .powerpages-site/web-roles/ to
  populate adx_serverlogic_adx_webrole array
- Explore agent updated to search .powerpages-site/server-logic/ and
  read web role files
- Validation script updated to check new file locations, YAML structure,
  UUID validity, and non-empty web role array
- Removed redundant deployment check in Phase 6 (already enforced in
  Phase 1.5)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Server.Connector.Dataverse respects table permissions — without them,
the connector silently returns 0 records. Added Phase 6 (conditional)
that:

- Parses the server logic .js to detect which Dataverse tables are
  accessed and what CRUD operations are performed
- Launches the table-permissions-architect agent to create table
  permission YAML files in .powerpages-site/table-permissions/
- Only runs when Server.Connector.Dataverse is used; skipped for
  HttpClient-only server logics

Also updated:
- Phase 4 plan table: shows table permissions needed upfront
- Phase 10.2 summary: includes table permissions row
- Phase 10.4 post-deploy: specific guidance about table permissions
- Stop hook: verifies table permissions were configured
- Key decision points and progress tracking table

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…kill

Two gaps mitigated vs integrate-webapi skill:

1. Web role creation (Phase 5.2): If no web roles exist, the skill
   now creates default roles (Authenticated Users, Anonymous Users,
   Administrators) using create-web-role.js before writing the
   server logic YAML. Previously only read existing roles.

2. Permission source choice (Phase 6.2): Added Path A (user-provided
   permissions diagram) alongside existing Path B (let architect
   analyze). Path A parses user diagrams and creates permissions
   via deterministic scripts, matching how integrate-webapi handles
   this. Path B now explicitly instructs the architect agent to
   create missing web roles if needed.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- 🔧 Changed command references from `/power-pages:create-site` to `/create-site`.
- 🔧 Updated prompt messages to reflect new command structure.
- 🔧 Adjusted deployment instructions for consistency.

-Priyanshu

Add explicit user confirmation before running /test-site after deployment,
include tracking file commit guidance, and bump power-pages plugin version.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- ✏️ Update SKILL.md to clarify async function usage with Dataverse.
- ✅ Add validation tests for server logic functions, including checks for async/await usage and error handling.
- 📝 Implement detailed error messages for validation failures.

-Priyanshu

- Rename skills/integrate-serverlogic/ to skills/add-server-logic/
- Update skill name in SKILL.md frontmatter
- Update all path references in SKILL.md, frontend-integration-reference.md
- Update skill key and validator path in powerpages-hook-utils.js
- Update skill name in render-serverlogic-plan.js
- Update tracking reference (skill name, PascalCase, setting name)
- Update skill name in test files

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…support

New add-cloud-flow skill that connects Power Automate flows to Power Pages
sites. Key behaviors beyond basic flow registration:
- Analyzes user intent to suggest the most relevant flows instead of a flat list
- Supports re-integrating already-registered flows into additional pages
  without re-creating metadata (integration-only path skips Phases 4-6)
- Guides users to Power Automate when no flows with a PowerPages trigger exist

Also adds hook registration, skill tracking, cloudflow plan renderer,
render-template dataObject support, and hook debug logging.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Standalone script that compares local plugin.json version against
origin/main and prints update commands (marketplace + plugin) if
a newer version is available.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Each skill now runs check-version.js before starting and shows an
update notice if the remote has a newer plugin version. Added the
convention to AGENTS.md and cleaned up hooks.json format.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

GitHub Actions workflow using the GitHub App to auto-add the
version check line to any SKILL.md missing it on PRs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

store-keyvault-secret.js: Write the secret to a temp file (mode 0600)
and pass --file to az CLI instead of --value, so the secret never
appears in az process arguments. Support reading the secret from
stdin (preferred) alongside the existing --secretValue flag.

ensure-skill-version-check.yml: Guard the auto-fix-and-push path
behind github.event.pull_request.head.repo.fork == false. Fork PRs
run the script in --check mode for a clear failure message without
requiring repository secrets or write access.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Fetch existing Custom APIs and Custom Process Actions from the user's
Dataverse environment so server logic can wrap them via InvokeCustomApi
instead of building equivalent logic from scratch.

- New script: list-custom-actions.js queries both customapis and
  workflows (category=3) tables with auth/retry support
- SKILL.md Phase 2.1.2: discover actions, present to user, map to
  server logic items
- SKILL.md Phase 5.3: code templates for unbound actions, entity-bound
  actions, and unbound functions
- HTML plan: purple "Custom Action" badge and detail box on cards that
  wrap an existing action
- Plan data format: optional customAction field on SERVER_LOGICS_DATA
- integrate-backend: Phase 1.3 discovers actions during site scan,
  factors them into approach recommendation and skill routing
- Decision framework: expanded Custom API entry and intent mapping

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Mermaid v11 prefixes node IDs with the SVG element ID (e.g.
"erSvg1-entity-CONTACT-0"), so the anchored regex ^entity-
never matched. Remove the ^ anchor, use .outer-path selector
for the header group, and color divider strokes to match status.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>