@salesforce/afv-skills 1.55.0 → 1.56.0

package/skills/dx-org-manage/examples/snapshots/success_output.json

@@ -1,15 +0,0 @@
-{
-  "status": 0,
-  "result": {
-    "Id": "0Oo5g00000001ABCAA",
-    "Status": "Pending",
-    "SourceOrg": "00D5g00000001XyEAI",
-    "SnapshotName": "MySnapshot",
-    "Description": "Baseline configuration with Package v1.2.0",
-    "Content": "metadatadata",
-    "CreatedDate": "2026-06-04T20:00:00.000+0000",
-    "CreatedBy": "0055g00000001UserEAA",
-    "LastModifiedDate": "2026-06-04T20:00:00.000+0000",
-    "LastModifiedBy": "0055g00000001UserEAA"
-  }
-}

package/skills/dx-org-manage/references/cli_flags.md

@@ -1,67 +0,0 @@
-# CLI Flags Reference
-
-Complete reference for `sf org create snapshot` command flags.
-
-## Required Flags
-
-| Flag | Alias | Description | Example |
-|------|-------|-------------|---------|
-| `--source-org` | `-o` | ID or authenticated username/alias of scratch org to snapshot | `--source-org my-scratch` |
-| `--name` | `-n` | Unique name for the snapshot | `--name MySnapshot` |
-| `--target-dev-hub` | `-v` | Dev Hub org username or alias (required unless default is set) | `--target-dev-hub DevHub` |
-
-## Optional Flags
-
-| Flag | Alias | Description | Example |
-|------|-------|-------------|---------|
-| `--description` | `-d` | Description of snapshot contents | `--description "Package v1.2.0"` |
-| `--api-version` | | Override the API version used for API requests | `--api-version 66.0` |
-
-## Global Flags
-
-| Flag | Description |
-|------|-------------|
-| `--json` | Format output as JSON (ALWAYS use this) |
-
-## Usage Patterns
-
-### Basic Snapshot Creation
-
-```bash
-sf org create snapshot --source-org my-scratch --name MySnapshot --json
-```
-
-### With Description
-
-```bash
-sf org create snapshot \
-  --source-org my-scratch \
-  --name MySnapshot \
-  --description "Baseline with Package v1.2.0" \
-  --json
-```
-
-### Using Org ID Instead of Alias
-
-```bash
-sf org create snapshot \
-  --source-org 00D5g00000001XyEAI \
-  --name MySnapshot \
-  --json
-```
-
-### Specify Dev Hub Explicitly
-
-```bash
-sf org create snapshot \
-  --source-org my-scratch \
-  --name MySnapshot \
-  --target-dev-hub MyDevHub \
-  --json
-```
-
-## Important Notes
-
-- **Source org auto-resolution**: Accepts org ID (starts with 00D) or username/alias — aliases are automatically resolved to org IDs
-- **Description best practice**: Include version control reference (git tag, commit SHA) to track snapshot contents
-- **Asynchronous creation**: Snapshot creation happens asynchronously — use `sf org get snapshot` to check status

package/skills/dx-org-manage/references/creating-snapshot.md

@@ -1,103 +0,0 @@
-# Creating Snapshots
-
-Creates a point-in-time snapshot of a scratch org using `sf org create snapshot`. Snapshots preserve scratch org state and configuration for reuse in scratch org definition files.
-
----
-
-## Required Inputs
-
-Infer from the user's request:
-
-- **Source org**: Scratch org ID (starts with 00D) or username/alias to snapshot
-- **Snapshot name**: Unique name for the snapshot (required)
-- **Dev Hub**: Dev Hub org alias/username (uses default if not specified)
-- **Description** (optional): Document snapshot contents, version control reference
-
----
-
-## Workflow
-
-1. **Gather inputs** — get source org, snapshot name, and optional description
-2. **Build command** — construct `sf org create snapshot` with appropriate flags
-3. **Execute via Bash tool** — run command with `--json` flag
-4. **Return result** — report snapshot ID and status
-
-### Command Patterns
-
-| User intent | Execute via Bash tool |
-|-------------|---------|
-| Create snapshot with name only | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --json` |
-| Create snapshot with description | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --description "<desc>" --json` |
-| Specify Dev Hub explicitly | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --target-dev-hub <devHubAlias> --json` |
-
----
-
-## Rules / Constraints
-
-| Constraint | Rationale |
-|-----------|-----------|
-| Always use `--json` flag | Provides structured output for reliable parsing and error handling |
-| Snapshot names must be unique in the Dev Hub | Duplicate names cause creation to fail |
-| Source org must be a scratch org | Snapshots only work with scratch orgs, not sandboxes or production orgs |
-| Source org accepts ID or username/alias | Command auto-resolves aliases to org IDs; org IDs start with 00D |
-| Include description for tracking | Best practice: reference version control tag or commit ID in description |
-
----
-
-## Troubleshooting
-
-| Issue | Resolution |
-|-------|------------|
-| Error creating snapshot | Surface the CLI's own error unchanged; the message states what to do next |
-| `@salesforce/plugin-signups does not exist in the registry` | Snapshot commands live in the `signups` plugin, which ships bundled with a normal `sf` install. This error means the CLI environment is incomplete (slim image) or the plugin registry is unreachable (offline). Because the registry is unavailable, `sf plugins install` cannot succeed — do NOT attempt it (it will fail and loop). Surface the error and advise the user to repair their environment from a connected machine: reinstall or update the Salesforce CLI (for example with `sf update`, or a fresh global CLI install through their normal package manager) so the bundled `signups` plugin is present, or run in an image that already includes it. Never run any install/repair from inside the skill. |
-| "No org found for <alias>" error | Source org alias doesn't exist or isn't authenticated — verify with `sf org list` |
-| Snapshot name already exists | Use a different unique name — snapshot names must be unique per Dev Hub |
-| "An error while created the org snapshot" | Generic error — check that source org is a scratch org and still active |
-| Long-running snapshot creation | Use `sf org get snapshot --snapshot <name>` to check status — snapshot creation is asynchronous |
-
----
-
-## Output Expectations
-
-The command returns JSON output with the created snapshot details.
-
-See `examples/snapshots/success_output.json` and `examples/snapshots/error_output.json` for complete response structures.
-
-Example success response:
-```json
-{
-  "result": {
-    "SnapshotId": "0Ym...",
-    "SnapshotName": "MySnapshot",
-    "Status": "Active",
-    "SourceOrg": "00D..."
-  }
-}
-```
-
----
-
-## Using Snapshots
-
-After creating a snapshot, use it to create scratch orgs by:
-
-1. **In scratch org definition file:**
-   ```json
-   {
-     "snapshot": "MySnapshot"
-   }
-   ```
-
-2. **Or via command flag:**
-   ```bash
-   sf org create scratch --snapshot MySnapshot --target-dev-hub <alias> --alias <name> --json
-   ```
-
-See `snapshot_usage.md` for detailed examples.
-
----
-
-## Additional Resources
-
-- See `cli_flags.md` for detailed explanation of all available flags
-- See `snapshot_usage.md` for how to use snapshots in scratch org creation

package/skills/dx-org-manage/references/snapshot_usage.md

@@ -1,74 +0,0 @@
-# Using Snapshots in Scratch Org Definition Files
-
-After creating a snapshot, reference it in scratch org definition files to create new scratch orgs from the saved state.
-
-## Scratch Org Definition File Format
-
-Use the `snapshot` field instead of `edition` in your `project-scratch-def.json`:
-
-```json
-{
-  "orgName": "My Company",
-  "snapshot": "MySnapshot",
-  "features": ["EnableSetPasswordInApi"],
-  "settings": {
-    "lightningExperienceSettings": {
-      "enableS1DesktopEnabled": true
-    }
-  }
-}
-```
-
-## Key Differences from Edition-Based Definitions
-
-| Field | Edition-based | Snapshot-based |
-|-------|--------------|----------------|
-| Primary field | `"edition": "Developer"` | `"snapshot": "MySnapshot"` |
-| Contents | Empty org with edition defaults | Pre-configured org state from snapshot |
-
-## Creating a Scratch Org from Snapshot
-
-```bash
-sf org create scratch --definition-file config/project-scratch-def.json --alias from-snapshot
-```
-
-The scratch org will be created with all the metadata, data, and configuration from the snapshot.
-
-## Common Use Cases
-
-### 1. Package Development
-
-```json
-{
-  "orgName": "Package Dev Org",
-  "snapshot": "Dependencies_v1.2.0",
-  "description": "Org with all dependencies installed"
-}
-```
-
-### 2. Testing Baseline
-
-```json
-{
-  "orgName": "Test Baseline",
-  "snapshot": "TestData_Populated",
-  "description": "Org with sample data for testing"
-}
-```
-
-### 3. CI/CD Pipeline
-
-```json
-{
-  "orgName": "CI Scratch Org",
-  "snapshot": "Nightly_Build_Baseline",
-  "description": "Latest nightly build dependencies"
-}
-```
-
-## Workflow Summary
-
-1. **Create snapshot**: `sf org create snapshot --source-org <scratch> --name MySnapshot`
-2. **Check status**: `sf org get snapshot --snapshot MySnapshot`
-3. **Reference in definition file**: `"snapshot": "MySnapshot"`
-4. **Create new scratch org**: `sf org create scratch --definition-file config/project-scratch-def.json`

package/skills/experience-accessibility-validate/scripts/contrast-ratio.py

@@ -1,153 +0,0 @@
-#!/usr/bin/env python3
-"""WCAG 2.2 SC 1.4.3 / 1.4.11 contrast-ratio calculator.
-
-Computes the exact WCAG contrast ratio between a foreground and a background
-color so the accessibility reviewer never has to approximate relative luminance
-by hand (which is unreliable and has produced inconsistent findings). The
-reviewer resolves the two colors from the component's HTML/CSS, then invokes
-this script; the printed verdict is authoritative.
-
-Usage:
-  contrast-ratio.py FOREGROUND BACKGROUND [--large] [--json]
-
-Arguments:
-  FOREGROUND   Text color. Accepts #RGB, #RRGGBB, rgb(r,g,b) or rgba(r,g,b,a).
-  BACKGROUND   Background color. Must be opaque (#RGB/#RRGGBB/rgb()); used as
-               the compositing base when FOREGROUND carries an alpha channel.
-
-Options:
-  --large      Classify the text as large-scale (>=24px, or >=18.66px bold),
-               which uses the 3:1 threshold instead of 4.5:1 for the primary
-               PASS/FAIL. Both thresholds are always reported regardless.
-  --json       Emit a machine-readable JSON object instead of the text report.
-
-Exit codes:
-  0  Ratio meets the applicable threshold (PASS)
-  1  Ratio is below the applicable threshold (FAIL)
-  2  Argument / parse error
-"""
-
-import argparse
-import json
-import re
-import sys
-
-_STANDARD_THRESHOLD = 4.5
-_LARGE_THRESHOLD = 3.0
-
-
-def _parse_color(value):
-    """Return (r, g, b, a) with channels in 0-255 and alpha in 0.0-1.0."""
-    s = value.strip()
-
-    m = re.fullmatch(r"#([0-9a-fA-F]{3})", s)
-    if m:
-        r, g, b = (int(c * 2, 16) for c in m.group(1))
-        return r, g, b, 1.0
-
-    m = re.fullmatch(r"#([0-9a-fA-F]{6})", s)
-    if m:
-        h = m.group(1)
-        return int(h[0:2], 16), int(h[2:4], 16), int(h[4:6], 16), 1.0
-
-    m = re.fullmatch(
-        r"rgba?\(\s*([\d.]+)\s*,\s*([\d.]+)\s*,\s*([\d.]+)\s*(?:,\s*([\d.]+)\s*)?\)",
-        s,
-    )
-    if m:
-        r, g, b = (int(round(float(m.group(i)))) for i in (1, 2, 3))
-        a = float(m.group(4)) if m.group(4) is not None else 1.0
-        for ch in (r, g, b):
-            if not 0 <= ch <= 255:
-                raise ValueError(f"channel out of range in '{value}'")
-        if not 0.0 <= a <= 1.0:
-            raise ValueError(f"alpha out of range in '{value}'")
-        return r, g, b, a
-
-    raise ValueError(
-        f"unrecognized color '{value}' — use #RGB, #RRGGBB, rgb(), or rgba()"
-    )
-
-
-def _composite(fg, bg):
-    """Alpha-composite fg over an opaque bg; return an opaque (r, g, b)."""
-    fr, fgc, fb, fa = fg
-    br, bgc, bb, _ = bg
-    if fa >= 1.0:
-        return fr, fgc, fb
-    return (
-        round(fr * fa + br * (1 - fa)),
-        round(fgc * fa + bgc * (1 - fa)),
-        round(fb * fa + bb * (1 - fa)),
-    )
-
-
-def _relative_luminance(rgb):
-    """WCAG relative luminance for an opaque sRGB (r, g, b) triple."""
-    def _lin(c):
-        c /= 255.0
-        return c / 12.92 if c <= 0.03928 else ((c + 0.055) / 1.055) ** 2.4
-
-    r, g, b = (_lin(c) for c in rgb)
-    return 0.2126 * r + 0.7152 * g + 0.0722 * b
-
-
-def contrast_ratio(foreground, background):
-    """Exact WCAG contrast ratio between two color strings (>= 1.0)."""
-    fg = _parse_color(foreground)
-    bg = _parse_color(background)
-    if bg[3] < 1.0:
-        raise ValueError(
-            f"background '{background}' is translucent — its rendered color "
-            "depends on the layer beneath it and cannot be determined. Resolve "
-            "the effective opaque background and pass that instead."
-        )
-    fg_rgb = _composite(fg, bg)
-    l1 = _relative_luminance(fg_rgb)
-    l2 = _relative_luminance(bg[:3])
-    lighter, darker = (l1, l2) if l1 >= l2 else (l2, l1)
-    return (lighter + 0.05) / (darker + 0.05)
-
-
-def main(argv=None):
-    parser = argparse.ArgumentParser(add_help=True)
-    parser.add_argument("foreground")
-    parser.add_argument("background")
-    parser.add_argument("--large", action="store_true")
-    parser.add_argument("--json", action="store_true", dest="as_json")
-    args = parser.parse_args(argv)
-
-    try:
-        ratio = contrast_ratio(args.foreground, args.background)
-    except ValueError as exc:
-        print(f"ERROR: {exc}", file=sys.stderr)
-        return 2
-
-    threshold = _LARGE_THRESHOLD if args.large else _STANDARD_THRESHOLD
-    passes = ratio >= threshold
-    result = {
-        "foreground": args.foreground,
-        "background": args.background,
-        "ratio": round(ratio, 2),
-        "textClass": "large" if args.large else "standard",
-        "threshold": threshold,
-        "passesStandard": ratio >= _STANDARD_THRESHOLD,
-        "passesLarge": ratio >= _LARGE_THRESHOLD,
-        "verdict": "PASS" if passes else "FAIL",
-    }
-
-    if args.as_json:
-        print(json.dumps(result))
-    else:
-        print(
-            f"{result['ratio']}:1  {result['verdict']} "
-            f"({result['textClass']} text, threshold {threshold}:1)  |  "
-            f"standard 4.5:1 {'pass' if result['passesStandard'] else 'fail'}, "
-            f"large 3:1 {'pass' if result['passesLarge'] else 'fail'}"
-        )
-
-    return 0 if passes else 1
-
-
-if __name__ == "__main__":
-    sys.exit(main())

package/skills/experience-lwc-accessibility-jest-run/references/running-sa11y-jest-tests.md

@@ -1,205 +0,0 @@
-# Sa11y Accessibility Test Instructions
-
-## Environment Detection
-
-Choose the approach based on your environment:
-
-- **Core Build Environment** — contains a `WORKSPACE` file, uses Bazel build system.
-- **Standalone Environment** — no `WORKSPACE` file, uses npm/yarn scripts.
-
-If this is not a Salesforce core build environment, do not mention anything about the core build environment.
-
----
-
-## Core Build Environment (Bazel)
-
-When working within a Salesforce core build environment, use Bazel commands.
-
-### Base Command Structure
-
-```bash
-{coreRootPath}/tools/bazel test [TARGET] --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-**Replacements:**
-
-- `{coreRootPath}` — your actual core root directory path
-- `{moduleName}` — module name (e.g. `ui-content-authoring-components`)
-- `{relativePath}` — test file path **without** `.test.js` extension
-
-### Testing Approaches
-
-#### 1. Single File Testing
-
-```bash
-{coreRootPath}/tools/bazel test //{moduleName}:{relativePath} --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-Example:
-
-```bash
-./core/tools/bazel test //ui-content-authoring-components:modules/es_block_builder/blockBuilder/__tests__/blockBuilder --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-**Use when:** testing a specific component with a known test file path.
-
-#### 2. Module Testing
-
-```bash
-{coreRootPath}/tools/bazel test //{moduleName}:sa11y_jest_test --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-Example:
-
-```bash
-./core/tools/bazel test //ui-content-authoring-components:sa11y_jest_test --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-**Use when:** testing an entire module or when unsure which specific component to target.
-
-#### 3. Multiple Modules
-
-```bash
-{coreRootPath}/tools/bazel test //{module1}:sa11y_jest_test //{module2}:sa11y_jest_test --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-**Use when:** integration testing across module boundaries.
-
-#### 4. Wildcard Testing
-
-```bash
-{coreRootPath}/tools/bazel test //{moduleName}:sa11y_jest_test --test_arg=--testMatch="**/{modulePath}/**" --test_output=streamed --test_env=SA11Y_AUTO=1 --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1
-```
-
-**Use when:** filtering multiple components within a module by pattern.
-
----
-
-## Standalone Environment (Direct Jest)
-
-No `SA11Y_*` environment variables are needed here — `@sa11y/jest` is wired into
-the project's Jest setup, so the accessibility assertions run automatically.
-
-```bash
-# Run all accessibility tests (match by the *.accessibility.test.js convention)
-npm test -- --testMatch="**/*.accessibility.test.js"
-
-# Re-run a single test file — use the filename/path as given in the prompt
-# (a bare filename when the file is "in this directory")
-npm test -- myComponent.accessibility.test.js
-```
-
-### Jest Configuration
-
-Ensure Jest includes Sa11y setup:
-
-```javascript
-// jest.config.js
-module.exports = {
-  setupFilesAfterEnv: ['<rootDir>/test/setup/sa11y-setup.js'],
-  testEnvironment: 'jsdom',
-};
-```
-
-### Sa11y Setup File
-
-```javascript
-// test/setup/sa11y-setup.js
-import { configure } from '@sa11y/jest';
-
-configure({
-  rules: ['wcag2a', 'wcag2aa', 'wcag2aaa'],
-});
-```
-
----
-
-## Path Discovery (Core Build Environment)
-
-```bash
-# Find all test files in a module
-find {coreRootPath}/ui-content-authoring-components -name "*.test.js" -type f
-
-# Explore module structure
-ls {coreRootPath}/ui-content-authoring-components/modules/
-
-# Use Bazel to list test targets
-{coreRootPath}/tools/bazel query "tests(//ui-content-authoring-components:*)"
-```
-
-### Path Construction
-
-- **Module Name** — use directly (e.g. `ui-content-authoring-components`)
-- **Component Path** — `modules/{componentDir}/{componentName}/__tests__/`
-- **Test File** — remove `.test.js` extension
-
----
-
-## Optional Arguments
-
-### Bazel Options
-
-| Option           | Command                                                                                                                           | Purpose                    |
-| ---------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------- |
-| Update Snapshots | `--test_arg="--updateSnapshot"`                                                                                                   | Update test snapshots      |
-| Disable Cache    | `--cache_test_results=no`                                                                                                         | Disable Bazel test caching |
-| Save HTML Files  | `--test_env=SA11Y_ENABLE_RENDERED_DOM_SAVE=1 --test_env=SA11Y_RENDERED_DOM_SAVE_PATH=sfdc-test/unit/javascript/htdocs/sa11y/jest` | Save HTML for analysis     |
-
-**Note:** Use `sfdc-test/unit/javascript/htdocs/sa11y/jest` as the save path to avoid EPERM permission issues.
-
-**Complete example with HTML saving:**
-
-```bash
-./core/tools/bazel test //ui-content-authoring-components:modules/es_block_builder/blockBuilder/__tests__/blockBuilder \
-  --test_output=streamed \
-  --test_env=SA11Y_AUTO=1 \
-  --test_env=SA11Y_ENABLE_DOM_MUTATION_OBSERVER=1 \
-  --test_env=SA11Y_ENABLE_RENDERED_DOM_SAVE=1 \
-  --test_env=SA11Y_RENDERED_DOM_SAVE_PATH=sfdc-test/unit/javascript/htdocs/sa11y/jest
-```
-
-### Jest Options
-
-```bash
-# Update snapshots
-npm test -- --testMatch="**/*.accessibility.test.js" --updateSnapshot
-
-# Run in watch mode
-npm test -- --testMatch="**/*.accessibility.test.js" --watch
-
-# Run with verbose output
-npm test -- --testMatch="**/*.accessibility.test.js" --verbose
-```
-
----
-
-## Expected Exit Codes
-
-### Bazel
-
-- **0** — all tests passed
-- **3** — build succeeded, some tests failed
-- **1** — build or command failed
-
-### Jest
-
-- **0** — all tests passed
-- **1** — some tests failed or error occurred
-
----
-
-## Troubleshooting
-
-### Bazel
-
-- Verify `WORKSPACE` file exists
-- Check Bazel version compatibility
-- Ensure test targets are properly defined
-- Verify repository-specific Bazel binary path
-
-### Jest
-
-- Verify Jest configuration
-- Check test file naming conventions
-- Ensure Sa11y dependencies are installed
-- Verify jsdom environment setup

package/skills/experience-ui-bundle-features-generate/scripts/verify-react-bundle.sh

@@ -1,14 +0,0 @@
-#!/usr/bin/env bash
-# Verify that the project contains a React-based UI bundle
-# Exit 0 if React is found, exit 1 otherwise
-
-set -euo pipefail
-
-if ! grep -q '"react"' uiBundles/*/package.json 2>/dev/null; then
-  echo "ERROR: Not a React bundle - @salesforce/ui-bundle-features requires React"
-  echo "Found bundle type: $(grep '"type"' uiBundles/*/package.json 2>/dev/null || echo 'unknown')"
-  exit 1
-fi
-
-echo "React bundle detected"
-exit 0