@salesforce/afv-skills 1.20.0 → 1.22.0

package/skills/platform-trust-archive-manage/examples/monitor-failed-jobs.md

@@ -0,0 +1,47 @@
+# Example — Monitor failed archive jobs and download their logs
+
+End-to-end flow for the most common archive-admin task: find the jobs that failed or stalled, read why, and pull the logs that show which records didn't make it.
+
+## 1. Find the jobs (query ArchiveActivity)
+
+`ArchiveActivity` is not Flow-queryable, so use SOQL/Connect:
+
+```sql
+SELECT Id, Name, Status, Type, StartTime, ProgressPercentage,
+       TotalRecordCount, SucceededCount, FailedCount, SkippedRootRecordsCount,
+       RootEntityName, FailureReason
+FROM ArchiveActivity
+WHERE (Status = 'Failed' OR Status = 'In Progress' OR Status = 'Ended With Errors')
+  AND StartTime >= LAST_N_DAYS:7
+ORDER BY StartTime DESC
+```
+
+Read each row's `ProgressPercentage`, `SucceededCount`/`FailedCount`, `RootEntityName`, and `FailureReason` to summarize health. In-progress jobs have a blank `EndTime`.
+
+## 2. For each failed job, get the logs
+
+Take the job's `Id` (`8qv…`) as `requestId` and its `Type` as `reportType`. `{activity.Type}` below is a placeholder for that job's own `Type` field value (e.g. `Archive`, `Purge`, `Unarchive`, `Analyzer`) — substitute the actual value per job; a hardcoded/mismatched `reportType` returns no log.
+
+**Execution-detail log:**
+```
+GET /platform/data-resilience/archive/log/execution-details-stream-url
+    ?requestId={activity.Id}&reportType={activity.Type}
+```
+
+**Failed-records log:**
+```
+GET /platform/data-resilience/archive/log/failed-records-stream-url
+    ?requestId={activity.Id}&reportType={activity.Type}
+```
+
+Each returns `{ url }`. **Check `url != null`** before using it — a `null` url means no log was resolved for that job/type (e.g. the job produced no failed-records file), not an error to retry blindly.
+
+## 3. Summarize
+
+Per failed/in-progress job, report: Name, Status, ProgressPercentage, SucceededCount, FailedCount, RootEntityName (target object), FailureReason, and the two log URLs (or "no log available" when `url` is null).
+
+## Pitfalls this flow avoids
+
+- **Not** attempting a Flow over `ArchiveActivity` (`isProcessEnabled=false` → "You can't get ArchiveActivity records in a flow").
+- Passing the activity's real `Type` as `reportType` (a mismatch returns no log).
+- Treating a 201 with `url: null` as a usable log.

package/skills/platform-trust-archive-manage/references/archive-activity-entity.md

@@ -0,0 +1,59 @@
+# ArchiveActivity — Data Model Reference
+
+`ArchiveActivity` is the platform entity that records **job metadata for Salesforce Archive jobs** (archive, purge, analyze, unarchive, export). Every archive job produces one `ArchiveActivity` record; you read it to learn a job's status, progress, and outcome, and you use its `Id` + `Type` to download the job's logs.
+
+## Entity facts
+
+| Property | Value |
+|----------|-------|
+| API name | `ArchiveActivity` |
+| Key prefix | `8qv` (record Ids start `8qv…`) |
+| Owning product | Salesforce Archive (Trusted Services Archive) |
+| Kind | **Standard platform entity** (not a custom object) |
+| License gate | Requires the Trusted Services Archive add-on (`TrustedServicesArchive.hasTrustedServicesArchive`) — absent on orgs without the add-on |
+| Name field | Auto-number, mask `ARCV-{0000000000}` |
+| Flow-enabled? | **No** — `isProcessEnabled=false`. A Flow "Get Records" element on it fails: "You can't get ArchiveActivity records in a flow." Query via SOQL / Connect / Reports. |
+
+## Fields
+
+| Field | Type | Meaning |
+|-------|------|---------|
+| `Name` | Auto-number | `ARCV-…` job identifier |
+| `Status` | enum `ArchiveActivityStatus` | Lifecycle: scheduled, running / **In Progress**, completed, **Failed**, canceled, **Ended With Errors** |
+| `Type` | enum `ArchiveActivityType` | The job mode: Archive, Purge, Analyze(r), Unarchive, Export-to-external-bucket, Export-and-download. **This is the `reportType` for log downloads.** |
+| `StartTime` | DateTime | When execution began |
+| `EndTime` | DateTime | When execution finished/terminated (blank while running) |
+| `ArchivePolicyDefinition` | Lookup (FK) | Parent `ArchivePolicyDefinition`; child relationship `ArchiveActivities` |
+| `RootEntityName` | Text | API name of the target sObject being archived |
+| `TotalRecordCount` | Long | Records initially selected (succeeded + failed + skipped) |
+| `AttemptedRootRecordsCount` | Long (formula) | `SkippedRootRecordsCount + FailedCount + SucceededCount` — top-level records actually attempted |
+| `SkippedRootRecordsCount` | Long | Top-level records skipped (validation, exclusion filters, data-protection thresholds) |
+| `SucceededCount` | Long | Records processed without error |
+| `FailedCount` | Long | Records that failed (validation, missing refs, exceptions) |
+| `ProgressPercentage` | Double | Percent complete |
+| `FailureReason` | Long text | Why the job failed/partially completed (system error messages or policy-level failures) |
+| `RecordsSizeInMb` | Text | Estimated total size of processed records (MB) |
+
+> The entity also defines a `ProgressIcon` display formula for list views; it is not useful for programmatic monitoring — read `Status`, `ProgressPercentage`, and the count fields directly.
+
+## How ArchiveActivity links to the Connect API
+
+The log-download endpoints (`get-execution-details-stream-url`, `get-failed-records-stream-url`) take:
+
+- `requestId` = an `ArchiveActivity` **`Id`** (`8qv…`) of a completed, log-producing job, and
+- `reportType` = that same activity's **`Type`** value.
+
+So the monitoring pattern is: **query `ArchiveActivity` → pick the job(s) of interest → pass each job's `Id` and `Type` to the stream-url operation → check `url != null`.** See `../examples/monitor-failed-jobs.md`.
+
+## Example SOQL
+
+```sql
+-- Failed or in-progress jobs in the last 7 days, newest first
+SELECT Id, Name, Status, Type, StartTime, EndTime, ProgressPercentage,
+       TotalRecordCount, SucceededCount, FailedCount, SkippedRootRecordsCount,
+       RootEntityName, FailureReason, ArchivePolicyDefinitionId
+FROM ArchiveActivity
+WHERE (Status = 'Failed' OR Status = 'In Progress' OR Status = 'Ended With Errors')
+  AND StartTime >= LAST_N_DAYS:7
+ORDER BY StartTime DESC
+```

package/skills/platform-trust-archive-manage/references/connect-api-operations.md

@@ -0,0 +1,157 @@
+# Salesforce Archive Connect API — Operations Reference
+
+All operations are under the base path `/platform/data-resilience/archive/`. Contracts verified live against archived data. Read the operation you need before constructing the call — several contracts are non-obvious.
+
+## Operations Summary
+
+| Operation | Purpose | Method + Path | Verify with |
+|-----------|---------|---------------|-------------|
+| `search-archived-records` | read | `POST /search` | — |
+| `search-archived-records-with-sharing-rules` | read (Agentforce) | `POST /search/with-sharing-rules` | — |
+| `get-search-archived-records-next-page` | read | `GET /search/next/{scrollId}` | — |
+| `run-analyzer` | write | `POST /analyzer/run` | `get-analyzer-report` |
+| `get-analyzer-report` | read | `GET /analyzer/report` | — |
+| `unarchive-records` | write | `POST /unarchive` | re-run `search-archived-records` |
+| `forget-archived-records` (RTBF) | write | `POST /rtbf` | `get-rtbf-status` |
+| `get-rtbf-status` | read | `GET /rtbf/{requestId}` | — |
+| `mask-archived-records` | write | `POST /mask` | `get-masking-status` |
+| `get-masking-status` | read | `GET /mask/{requestId}` | — |
+| `get-execution-details-stream-url` | read | `GET /log/execution-details-stream-url` | — |
+| `get-failed-records-stream-url` | read | `GET /log/failed-records-stream-url` | — |
+| `get-archive-storage-used` | read | `GET /storage/archive-used` | — |
+
+**Deprecated — do not use** (no successor; currently 500): `global-search-by-id`, `get-global-search-results`, `view-archived-records`. Use `search-archived-records` (+ `get-search-archived-records-next-page`) for all archived-record lookups.
+
+### Verify-after-write dependencies
+
+```mermaid
+graph TD
+  run_analyzer["run-analyzer"] -.verify.-> get_analyzer_report["get-analyzer-report"]
+  forget_archived_records["forget-archived-records"] -.verify.-> get_rtbf_status["get-rtbf-status"]
+  mask_archived_records["mask-archived-records"] -.verify.-> get_masking_status["get-masking-status"]
+  unarchive_records["unarchive-records"] -.verify.-> search_archived_records["search-archived-records"]
+```
+
+---
+
+## search-archived-records (`POST /search`)
+
+Search archived records by object, filters, date ranges, and sort.
+
+**Required**: `sobjectName` + at least 1 filter. Missing them returns a clean envelope validation error (`statusCode 400`).
+
+**Inputs**:
+- `sobjectName` *(string)* — API name of the sObject to search.
+- `filters` *(array)* — Filter conditions, each `{field, value}` where **both are required strings**. `value` is a single string — **not** an array, **not** nullable (null/omitted → `400 "This field may not be null"`). There is **no `operator` field**. **At least 1, up to 6 filters, combined with AND only** (OR is not supported). Example: `[{"field":"Subject","value":"Foo"}]`.
+- `dateRanges` *(array)* — Primary date filter: array of `{field, from, to}`. `from`/`to` must be full ISO-8601 datetime (`"2020-01-01T00:00:00Z"`); date-only → `400 JSON_PARSER_ERROR` (xsd:dateTime). Use the special field `archive_date` to filter by archive date instead of `CreatedDate`/`ModifiedDate`.
+- `dateRange` *(object)* — Optional **singular** convenience range `{field, from, to}`; the controller folds it into `dateRanges` (one-element equivalent). Same singular shape that `unarchive-records` uses.
+- `fields` *(array)* — Field API names to return.
+- `pageSize` *(integer)* — Records per page; default 25, max 1000.
+- `sortDirection` *(string)* — `asc`/`desc`, case-insensitive, default `asc`; an invalid value → 400.
+
+**Output**: HTTP **201**, `body = { records[], total_result_count, scroll_id }`, `body.statusCode = 200`, `errorMessage` null on success. **Branch on `body.statusCode`, not the HTTP code** — once past framework validation the response is always 200/201 even on logical failure, with the error in `errorMessage` + `statusCode`.
+
+**Excluded objects**: `Feed`, `History`, `Relation`, `Share` are not searchable; Files/Attachments are not retrievable.
+
+### Pagination
+
+Read records inline from each response. If `body.scroll_id != "-1"`, call `get-search-archived-records-next-page` with that `scroll_id`. **STOP when `scroll_id == "-1"`** — calling next-page with `"-1"` (the terminal sentinel) → 500. There is no separate fetch-by-requestId step.
+
+## get-search-archived-records-next-page (`GET /search/next/{scrollId}`)
+
+**Input**: `scrollId` *(string, path param)* — the `body.scroll_id` from a prior search. Stop when it is `"-1"`; never call with `"-1"`.
+**Output**: `body` (next page), `errorMessage`, `statusCode` — same envelope as search.
+
+---
+
+## search-archived-records-with-sharing-rules (`POST /search/with-sharing-rules`)
+
+Archive search **optimized for Agentforce agents**. (There is no `/search/related` endpoint — this is the operation that takes the JSON filter map.) Gated by the **`ViewArchivedRecords`** user permission (unlike plain `search-archived-records`, which uses `ViewSearchPage`).
+
+**Required**: `objectName`, `filtersJson`.
+
+**Inputs**:
+- `objectName` *(string)* — API name of the sObject.
+- `filtersJson` *(string)* — JSON-encoded **OBJECT MAP** of `fieldName → value`, e.g. `"{\"Subject\":\"Foo\",\"Status\":\"New\"}"`. **NOT** an array of `{field,value}` objects — the array form is rejected with `isSuccess:false "No valid filters provided. Please provide filtersJson"`.
+- `dateField` *(string)* — API name of the date field for temporal filtering.
+- `startDate` / `endDate` *(string)* — search window bounds (ISO-8601).
+- `maxResults` *(integer)* — max records to return; default 100.
+
+**Output**: `isSuccess` *(boolean — **branch on THIS, not the HTTP status**)*, `totalResultCount`, `records` (rich-text summary of ~5 key fields per record), `recordsJson` (HTML-entity-encoded JSON string), `errorMessage`, `message`, `warnings` (schema-validation/auto-fix advisories). **Validation failures surface as HTTP 201 + `isSuccess:false` + `errorMessage`, never a 4xx.** Pattern: `isSuccess:false` + `errorMessage` → caller bug; `isSuccess:true` + `recordsJson` → success.
+
+---
+
+## run-analyzer (`POST /analyzer/run`) + get-analyzer-report (`GET /analyzer/report`)
+
+`run-analyzer` triggers the analyzer; HTTP 201, output `message` *(string, human-readable status)*. **`isRunning` is ALWAYS `null`** — the controller only populates `message`; never branch on `isRunning`. Poll `get-analyzer-report` to confirm completion. Non-destructive / idempotent.
+
+`get-analyzer-report` returns `body` with: `topRecords[]` (`{objectName, objectLabel, objectIcon, size, count, usagePercent}` per archivable sObject), `topFiles[]` (parallel shape for files), `fileGeneralStorage`/`dataGeneralStorage` (`{storageUsed, storageRemaining, usagePercent}`), and `createdDateReport` (`"DD/MM/YYYY HH:MM:SS"`).
+
+---
+
+## unarchive-records (`POST /unarchive`)
+
+Restore archived records back into live storage by criteria.
+
+**Inputs**:
+- `sobjectName` *(string)* — sObject whose records to unarchive.
+- `filters` *(array)* — criteria identifying which archived records to restore.
+- `dateRange` *(object)* — optional **SINGULAR** range `{field, from, to}` (reads `getDateRange()`, unlike `/search` which uses plural `dateRanges`); full ISO-8601 datetimes. Omit to unarchive by filters alone.
+
+**Caps**: ≤1000 matched records (else not processed); ≤50 unarchive requests/hour/org. Restores the **whole archived hierarchy** of each match. Requires the **`UnarchiveSdk`** user permission (on top of org-level Archive enablement).
+
+**Output**: `body` (unarchive job details incl. job id), `errorMessage`, `statusCode`. **Verify** by re-running `search-archived-records`. **Rollback**: re-archive via a new archive job with the same criteria.
+
+---
+
+## forget-archived-records / RTBF (`POST /rtbf`) + get-rtbf-status (`GET /rtbf/{requestId}`)
+
+Submits a Right-To-Be-Forgotten erasure request.
+
+**Input**: `criteria` *(array of `{sobject, field, value}`)* — ≤10 items, **one per object type**; ≤10,000 root records erased per org/day; field/object names case-insensitive. Deletes the **entire archived hierarchy** of each match (no partial deletion). Note: the criterion must match a record archived **as a root** — filtering a parent (e.g. Account by Id) when only its children were archived matches nothing.
+
+**Output**: HTTP 201, `body.request_id` *(UUID)*. Poll `get-rtbf-status` (path param `requestId` = that UUID) → `body.status` (e.g. `"Request is open. Scan is still in progress"`). **Rollback**: none — RTBF erasure is permanent.
+
+---
+
+## mask-archived-records (`POST /mask`) + get-masking-status (`GET /mask/{requestId}`)
+
+Submits a PII-masking (anonymization) request — irreversibly replaces detected PII values with placeholders (e.g. `redacted@example.com`) while keeping the record + non-PII fields searchable.
+
+**Input**: `criteria` *(array of `{sobject, field, value}`)* — same shape as RTBF.
+
+**Behavior**: permanent; one-time per record (re-requests on an already-masked record are ignored); shares the 10,000/day RTBF rate limit; **PII fields are auto-detected** (you cannot choose them); records under legal hold / retention lock are excluded; cascades to child records. Available **only via this API** (not in the Archive UI).
+
+**Permission**: gated by the **`Rtbf`** user permission — the SAME permission as RTBF (`maskArchivedRecords` runs the RTBF access check), not a separate masking entitlement.
+
+**Output**: HTTP 201, `body.request_id` *(UUID)*. Poll `get-masking-status` (path param `requestId`); status reaches **HANDLED** when complete. **Rollback**: none — anonymization is permanent.
+
+---
+
+## Log Downloads — get-execution-details-stream-url / get-failed-records-stream-url
+
+Both are `GET /log/...` and mint a one-time presigned download URL. `get-execution-details-stream-url` → the execution-detail log; `get-failed-records-stream-url` → the failed-records log (records that did not process). Identical contract.
+
+**Output**: `{ url }`. **`url != null` is success; `url: null` means no log was resolved** (missing/incorrect `requestId`/`reportType`, or the activity produced no such log) — always check `url != null`; never treat `url:null` or the 201 status alone as success.
+
+**Required inputs**:
+- `requestId` *(string)* — the **`ArchiveActivity` Id** (`8qv…` key) of a completed, log-producing job present in the archiver backend — **not** a search requestId. A missing/non-matching id → `url:null`.
+- `reportType` *(string)* — that activity's `Type`: `Archive | Unarchive | Analyzer | Purge | Export-to-external-bucket | Export-and-download`. Omitting it → `url:null`.
+- `sobjectName` *(string, optional)* — the backend self-resolves it.
+
+This is the bridge between `ArchiveActivity` (see `archive-activity-entity.md`) and downloadable logs.
+
+---
+
+## get-archive-storage-used (`GET /storage/archive-used`)
+
+Returns `body.usedStorage[4]` (doubles — per-tier bytes consumed) and `body.availableStorage[4]` (per-tier capacity) — two **parallel positional arrays** (NOT a flat metric, NOT key/value maps). The 4 slots are the same in both:
+
+| Index | Meaning |
+|-------|---------|
+| 0 | Salesforce org **DATA** storage |
+| 1 | Salesforce org **FILE** storage |
+| 2 | Archive-tier **RECORDS** storage |
+| 3 | Archive-tier **FILE** storage |
+
+**`availableStorage[2]` and `[3]` (the archive tier) are ALWAYS 0**: the controller hardcodes them (`ARCHIVER_AVAILABLE_STORAGE = 0`) because archive storage is unmetered, so a `0` there means "not tracked", NOT "no space left". Only `availableStorage[0]`/`[1]` (live org data/file remaining) are real. All values rounded to 2 decimals.

package/skills/platform-validation-rule-generate/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: platform-validation-rule-generate
+description: "Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work."
+metadata:
+  version: "1.0"
+---
+
+## When to Use This Skill
+
+Use this skill when you need to:
+- Create validation rules to enforce data quality
+- Prevent invalid records from being saved
+- Generate validation rule metadata with formulas
+- Add business logic validation to objects
+- Troubleshoot deployment errors related to validation rules
+
+## Specification
+
+# ValidationRule Metadata Specification
+
+### 📋 Overview
+Validation Rules are declarative metadata components used to enforce data quality and business logic in Salesforce. They evaluate a formula expression when a record is saved and prevent the save operation if the expression returns TRUE.
+
+### 🎯 Purpose
+-Enforce business rules at the data layer
+-Prevent invalid or incomplete records from being saved
+-Display meaningful error messages to guide users
+
+### ⚙️ Required Properties
+
+#### Core Validation Rule Properties
+
+- **fullName**
+    - The unique API name of the validation rule
+    - Must start with a letter
+        - Can contain letters, numbers, and underscores
+    - Cannot end with an underscore
+    - Cannot contain consecutive underscores
+    - Cannot exceed 40 character.
+
+- **active**
+  -Indicates whether the validation rule is enabled
+  true → Rule is enforced
+  false → Rule is inactive
+
+- **errorConditionFormula**
+- The logical formula that evaluates record data
+- Must return TRUE or FALSE
+- If TRUE, the validation rule triggers an error
+
+- **errorMessage**
+    - The message displayed to the user when validation fails
+- Maximum length: 255 characters
+
+### Specific Function Guidelines
+- TEXT - TEXT() function MUST NOT be used with Text fields, to fix this you can just remove the TEXT() function.
+- CASE - In salesforce CASE() function, last parameter is the default value. Admins often miss to provide this and number of parameters to CASE() function are always even.
+- VALUE - VALUE() function should only be used with Text fields. If a number is being used as a parameter to the VALUE() function, remove the VALUE() function.
+- DAY - DAY() function should only be used with Date fields. If a Datetime field is being used as a parameter to the DAY() function, convert it into a Date first.
+- MONTH - MONTH() function should only be used with Date fields. If a Datetime field is being used as a parameter to the MONTH() function, convert it into a Date first.
+- DATEVALUE - DATEVALUE() function should only be used with DateTime fields. If a Date is being used as a parameter to the DATEVALUE() function, remove the DATEVALUE() function.
+- ISPICKVAL - If checking equality of a picklist type field, the function ISPICKVAL() MUST be used.
+- ISCHANGE - Use ISCHANGE() function to check the value of a record has changed.
+
+### Critical Rules
+1. Formula XML Handling(MOST COMMON ERROR)
+    - ANY errorConditionFormula containing XML tags MUST be inside a CDATA section in the metadata XML.
+
+2. Interpretation of "Update" Instructions. When receiving instructions to modify a formula, distinguish between a replacement and an addition:
+    - "Update the formula to [Action]": Completely replace the existing formula logic with the new requirement.
+    - "Update the formula to also [Action]": Keep the existing logic and append the new requirement (usually by wrapping the logic in an AND() or OR() function).
+
+3. File Format Requirement
+    - Validation rule files MUST always use the `.validationRule-meta.xml` extension.

package/skills/recommending-devops-tests/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: recommending-devops-tests
-description: "Analyzes a commit diff and available DevOps Center test suite metadata to recommend the most relevant existing test suites, then flags coverage gaps where no suite covers a new method — via pure reasoning, no system calls beyond the prerequisite queries. Use this skill when a developer wants to know which test suites to run for a specific commit or diff, what tests cover their changes, or wants suite recommendations at commit time. TRIGGER when: the user asks which test suites to run for a commit/diff, asks what tests cover their changes, or asks for suite recommendations before promoting. DO NOT TRIGGER when: authoring new tests (use generating-apex-test) or running sf apex run test directly (use running-apex-tests)."
+description: "Analyzes a commit diff and available DevOps Center test suite metadata to recommend the most relevant existing test suites, then flags coverage gaps where no suite covers a new method — via pure reasoning, no system calls beyond the prerequisite queries. Use this skill when a developer wants to know which test suites to run for a specific commit or diff, what tests cover their changes, or wants suite recommendations at commit time. TRIGGER when: the user asks which test suites to run for a commit/diff, asks what tests cover their changes, or asks for suite recommendations before promoting. DO NOT TRIGGER when: authoring new tests (use platform-apex-test-generate) or running sf apex run test directly (use platform-apex-test-run)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"

package/skills/running-devops-test-suite/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: running-devops-test-suite
-description: "Triggers async execution of one or more DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) via the Connect API, after an explicit user confirmation gate, then hands off to result polling via the `polling-test-results` skill. Also re-runs (retriggers) a quality gate after fixes — but only once validation confirms the coverage threshold is now met. TRIGGER when: the user wants to run, kick off, or launch test suites on a pipeline stage; execute tests before or after a promotion; trigger a Pre-Promote, Post-Promote, or Review-event run; re-run a quality gate after fixing failures; retry a failed gate once coverage is met; or unblock a blocked promotion after adding tests. DO NOT TRIGGER when: running sf apex run test directly (use running-apex-tests); or configuring a NEW gate or threshold (use configuring-quality-gate)."
+description: "Triggers async execution of one or more DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) via the Connect API, after an explicit user confirmation gate, then hands off to result polling via the `polling-test-results` skill. Also re-runs (retriggers) a quality gate after fixes — but only once validation confirms the coverage threshold is now met. TRIGGER when: the user wants to run, kick off, or launch test suites on a pipeline stage; execute tests before or after a promotion; trigger a Pre-Promote, Post-Promote, or Review-event run; re-run a quality gate after fixing failures; retry a failed gate once coverage is met; or unblock a blocked promotion after adding tests. DO NOT TRIGGER when: running sf apex run test directly (use platform-apex-test-run); or configuring a NEW gate or threshold (use configuring-quality-gate)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"

package/skills/activating-datacloud/CREDITS.md

@@ -1,5 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in:
-- [../orchestrating-datacloud/CREDITS.md](../orchestrating-datacloud/CREDITS.md)
-- [../orchestrating-datacloud/UPSTREAM.md](../orchestrating-datacloud/UPSTREAM.md)