@salesforce/afv-skills 1.7.5 → 1.9.0

package/skills/retrieving-datacloud/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: retrieving-datacloud
+description: "Salesforce Data Cloud Retrieve phase. Use this skill when the user runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. TRIGGER when: user runs Data Cloud SQL, describe, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. DO NOT TRIGGER when: the task is standard CRM SOQL (use querying-soql), segment creation or calculated insight design (use segmenting-datacloud), or STDM/session tracing/parquet analysis (use observing-agentforce)."
+license: MIT
+compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
+metadata:
+  version: "1.0"
+---
+
+# retrieving-datacloud: Data Cloud Retrieve Phase
+
+Use this skill when the user needs **query, search, and metadata introspection** for Data Cloud: sync SQL, paginated SQL, async query workflows, table describe, vector search, hybrid search, or search index operations.
+
+## When This Skill Owns the Task
+
+Use `retrieving-datacloud` when the work involves:
+- `sf data360 query *`
+- `sf data360 search-index *`
+- `sf data360 metadata *`
+- `sf data360 profile *` or `sf data360 insight *` inspection
+- understanding Data Cloud SQL results or query shape
+
+Delegate elsewhere when the user is:
+- writing standard CRM SOQL only → [querying-soql](../querying-soql/SKILL.md)
+- designing segment or calculated insight assets → [segmenting-datacloud](../segmenting-datacloud/SKILL.md)
+- analyzing STDM/session tracing/parquet telemetry → [observing-agentforce](../observing-agentforce/SKILL.md)
+
+---
+
+## Required Context to Gather First
+
+Ask for or infer:
+- target org alias
+- whether the user needs quick count, medium result set, large export, schema inspection, or semantic search
+- table/index name if known
+- whether the task is read-only SQL or search-index lifecycle management
+
+---
+
+## Core Operating Rules
+
+- Treat Data Cloud SQL as its own query language, not SOQL.
+- Run the shared readiness classifier before relying on query/search surfaces: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json`.
+- Use describe before guessing columns.
+- Prefer `sqlv2` or async query flows for larger result sets.
+- Use vector search or hybrid search only when the search index lifecycle is healthy.
+- Keep STDM/parquet/session-tracing workflows out of this skill family.
+
+---
+
+## Recommended Workflow
+
+### 1. Classify readiness for retrieve work
+```bash
+node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
+# optional query-plane probe, only with a real table name
+node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
+```
+
+### 2. Choose the smallest correct query shape
+```bash
+sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
+sf data360 query sqlv2 -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
+sf data360 query async-create -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
+```
+
+### 3. Use describe before guessing fields
+```bash
+sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
+```
+
+### 4. Use vector or hybrid search only when an index exists
+```bash
+sf data360 search-index list -o <org> 2>/dev/null
+sf data360 query vector -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
+sf data360 query hybrid -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
+sf data360 query hybrid -o <org> --index Insurance_Index --query "weather damage coverage" --prefilter "Type_of_Insurance__c='Home'" --limit 10 2>/dev/null
+```
+
+### 5. Reuse curated search-index examples when creating indexes
+Use the phase-owned examples instead of inventing JSON from scratch:
+- `examples/search-indexes/vector-knowledge.json`
+- `examples/search-indexes/hybrid-structured.json`
+
+---
+
+## High-Signal Gotchas
+
+- Data Cloud SQL is not SOQL.
+- Table names should be double-quoted in SQL.
+- `sqlv2` is better than ad hoc OFFSET paging for medium result sets.
+- async query is preferable for large results.
+- search-index operations and vector/hybrid queries depend on the index lifecycle being healthy.
+- Hybrid search can use `--prefilter`, but only on fields configured as prefilter-capable when the search index was created.
+- HNSW index parameters are typically read-only on create; leave `userValues: []` unless the platform explicitly documents otherwise.
+- `query describe` is not a universal tenant probe; only run it with a known DMO or DLO table after broader readiness has been confirmed.
+
+---
+
+## Output Format
+
+```text
+Retrieve task: <sql / sqlv2 / async / describe / vector / search-index>
+Target org: <alias>
+Target object: <table or index>
+Commands: <key commands run>
+Verification: <query rows / schema / status>
+Next step: <segment / harmonize / follow-up>
+```
+
+---
+
+## References
+
+- [README.md](README.md)
+- [examples/search-indexes/vector-knowledge.json](examples/search-indexes/vector-knowledge.json)
+- [examples/search-indexes/hybrid-structured.json](examples/search-indexes/hybrid-structured.json)
+- [../orchestrating-datacloud/assets/definitions/search-index.template.json](../orchestrating-datacloud/assets/definitions/search-index.template.json)
+- [../orchestrating-datacloud/references/plugin-setup.md](../orchestrating-datacloud/references/plugin-setup.md)
+- [../orchestrating-datacloud/references/feature-readiness.md](../orchestrating-datacloud/references/feature-readiness.md)

package/skills/retrieving-datacloud/examples/search-indexes/hybrid-structured.json

@@ -0,0 +1,44 @@
+{
+  "label": "<INDEX_NAME>",
+  "developerName": "<INDEX_NAME>",
+  "description": "Hybrid search index on a structured Data Cloud DMO",
+  "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
+  "chunkDmoName": "<INDEX_NAME> chunk",
+  "chunkDmoDeveloperName": "<INDEX_NAME>_chunk",
+  "vectorDmoName": "<INDEX_NAME> index",
+  "vectorDmoDeveloperName": "<INDEX_NAME>_index",
+  "searchType": "HYBRID",
+  "vectorEmbedding": {
+    "vectorEmbeddingRelatedFields": []
+  },
+  "rankingConfigurations": [],
+  "chunkingConfiguration": {
+    "fieldLevelConfigurations": [
+      {
+        "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
+        "sourceDmoFieldDeveloperName": "<TEXT_FIELD>__c",
+        "config": {
+          "id": "passage_extraction",
+          "userValues": [
+            { "id": "max_tokens", "value": "512" },
+            { "id": "strip_html", "value": "true" }
+          ]
+        }
+      }
+    ]
+  },
+  "vectorEmbeddingConfiguration": {
+    "embeddingModel": {
+      "id": "e5_large_v2",
+      "userValues": [
+        { "id": "dimension", "value": "1024" },
+        { "id": "max_token_limit", "value": "512" }
+      ]
+    },
+    "index": {
+      "id": "HNSW",
+      "userValues": []
+    },
+    "similarityMetric": "COSINE"
+  }
+}

package/skills/retrieving-datacloud/examples/search-indexes/vector-knowledge.json

@@ -0,0 +1,43 @@
+{
+  "label": "My_kav",
+  "developerName": "My_kav",
+  "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
+  "chunkDmoName": "My_kav chunk",
+  "chunkDmoDeveloperName": "My_kav_chunk",
+  "vectorDmoName": "My_kav index",
+  "vectorDmoDeveloperName": "My_kav_index",
+  "searchType": "VECTOR",
+  "vectorEmbedding": {
+    "vectorEmbeddingRelatedFields": []
+  },
+  "chunkingConfiguration": {
+    "fieldLevelConfigurations": [
+      {
+        "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
+        "sourceDmoFieldDeveloperName": "ssot__Name__c",
+        "config": {
+          "id": "passage_extraction",
+          "userValues": [
+            { "id": "strip_html", "value": "true" },
+            { "id": "max_tokens", "value": "512" }
+          ]
+        }
+      }
+    ]
+  },
+  "vectorEmbeddingConfiguration": {
+    "embeddingModel": {
+      "id": "e5_large_v2",
+      "userValues": [
+        { "id": "dimension", "value": "1024" },
+        { "id": "max_token_limit", "value": "512" }
+      ]
+    },
+    "index": {
+      "id": "HNSW",
+      "userValues": []
+    },
+    "similarityMetric": "COSINE"
+  },
+  "rankingConfigurations": []
+}

package/skills/running-apex-tests/CREDITS.md

@@ -0,0 +1,22 @@
+# Credits & Acknowledgments
+
+This skill integrates concepts and patterns from Salesforce documentation and the broader Salesforce developer community. The goal is to move beyond minimum coverage targets toward true unit testing with proper isolation, mocking, and disciplined test-fix workflows.
+
+---
+
+## Key Patterns Integrated
+
+| Pattern | Integration |
+|---------|-------------|
+| DML Mocking | `assets/dml-mock.cls` |
+| Mocking vs Stubbing | `references/mocking-patterns.md` |
+| Test Data Factory | `assets/test-data-factory.cls` |
+| HttpCalloutMock | `assets/mock-callout-test.cls` |
+| StubProvider | `assets/stub-provider-example.cls` |
+| Performant Tests | `references/performance-optimization.md` |
+
+---
+
+## Philosophy
+
+This skill teaches Apex developers how to write fast, reliable, maintainable tests using vanilla Apex patterns — no external packages or libraries required. All patterns work in any Salesforce org out of the box.

package/skills/running-apex-tests/README.md

@@ -0,0 +1,94 @@
+# running-apex-tests
+
+Comprehensive Salesforce testing skill with test execution, code coverage analysis, and agentic test-fix loops. Run tests, analyze coverage, and automatically fix failing tests.
+
+## Features
+
+- **Test Execution**: Run Apex tests via sf CLI with coverage analysis
+- **Coverage Analysis**: Parse reports, identify untested code paths
+- **Failure Analysis**: Parse failures, identify root causes, suggest fixes
+- **Agentic Test-Fix Loop**: Automatically fix failing tests and re-run
+- **120-Point Scoring**: Validation across 6 categories
+- **Bulk Testing**: Validate with 251+ records for governor limits
+
+## Quick Start
+
+### 1. Invoke the skill
+
+```
+Skill: running-apex-tests
+Request: "Run all tests and show coverage report for org dev"
+```
+
+### 2. Common operations
+
+| Operation | Example Request |
+|-----------|-----------------|
+| Run class | "Run AccountServiceTest in org dev" |
+| Run all | "Run all local tests with coverage" |
+| Coverage report | "Show code coverage for AccountService" |
+| Fix loop | "Run tests and fix failures automatically" |
+| Generate tests | "Create tests for AccountService class" |
+
+## Key Commands
+
+```bash
+# Run single test class
+sf apex run test --class-names MyClassTest --code-coverage --result-format json --target-org [alias]
+
+# Run all local tests
+sf apex run test --test-level RunLocalTests --code-coverage --result-format json --target-org [alias]
+
+# Run specific methods
+sf apex run test --tests MyClassTest.testMethod1 --target-org [alias]
+
+# Run with output directory
+sf apex run test --class-names MyClassTest --output-dir test-results --target-org [alias]
+```
+
+## Scoring System (120 Points)
+
+| Category | Points | Focus |
+|----------|--------|-------|
+| Coverage | 25 | Overall and per-class coverage |
+| Assertions | 25 | Meaningful assertions, edge cases |
+| Bulk Testing | 20 | 251+ records, governor limits |
+| Data Isolation | 20 | @TestSetup, test data factories |
+| Negative Tests | 15 | Error paths, exceptions |
+| Documentation | 15 | Test descriptions, clear naming |
+
+## Test Thresholds
+
+| Level | Coverage | Purpose |
+|-------|----------|---------|
+| Production | 75% minimum | Required for deployment |
+| Recommended | 90%+ | Best practice target |
+| Critical paths | 100% | Business-critical code |
+
+## Cross-Skill Integration
+
+| Related Skill | When to Use |
+|---------------|-------------|
+| sf-apex | Fix failing Apex code |
+| debugging-apex-logs | Analyze test failures with debug logs |
+| handling-sf-data | Generate 251+ bulk test records |
+| deploying-metadata | Validate before deployment |
+
+## Agentic Test-Fix Loop
+
+When enabled, the skill will:
+1. Run tests and capture failures
+2. Analyze error messages and stack traces
+3. Generate fixes for common issues
+4. Apply fixes and re-run tests
+5. Repeat until all tests pass or max iterations reached
+
+## Documentation
+
+- [Testing Best Practices](references/testing-best-practices.md)
+
+## Requirements
+
+- sf CLI v2
+- Target Salesforce org
+- Test classes in org or local project

package/skills/running-apex-tests/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: running-apex-tests
+description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use generating-apex), Agentforce agent testing (use testing-agentforce), or Jest/LWC tests (use generating-lwc-components)."
+license: MIT
+metadata:
+  version: "1.1"
+---
+
+# running-apex-tests: Salesforce Test Execution & Coverage Analysis
+
+Use this skill when the user needs **Apex test execution and failure analysis**: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code.
+
+## When This Skill Owns the Task
+
+Use `running-apex-tests` when the work involves:
+- `sf apex run test` workflows
+- Apex unit-test failures
+- code coverage analysis
+- identifying uncovered lines and missing test scenarios
+- structured test-fix loops for Apex code
+
+Delegate elsewhere when the user is:
+- writing or refactoring production Apex → `generating-apex` skill
+- testing Agentforce agents → `testing-agentforce` skill
+- testing LWC with Jest → [generating-lwc-components](../generating-lwc-components/SKILL.md)
+
+---
+
+## Required Context to Gather First
+
+Ask for or infer:
+- target org alias
+- desired test scope: single class, specific methods, suite, or local tests
+- coverage threshold expectation
+- whether the user wants diagnosis only or a test-fix loop
+- whether related test data factories already exist
+
+---
+
+## Recommended Workflow
+
+### 1. Discover test scope
+Identify:
+- existing test classes
+- target production classes
+- test data factories / setup helpers
+
+### 2. Run the smallest useful test set first
+Start narrow when debugging a failure; widen only after the fix is stable.
+
+### 3. Analyze results
+Focus on:
+- failing methods
+- exception types and stack traces
+- uncovered lines / weak coverage areas
+- whether failures indicate bad test data, brittle assertions, or broken production logic
+
+### 4. Run a disciplined fix loop
+When the issue is code or test quality:
+- delegate code fixes to `generating-apex` skill when needed
+- add or improve tests
+- rerun focused tests before broader regression
+
+### 5. Improve coverage intentionally
+Cover:
+- positive path
+- negative / exception path
+- bulk path (251+ records where appropriate)
+- callout or async path when relevant
+
+---
+
+## High-Signal Rules
+
+| Rule | Rationale |
+|------|-----------|
+| Default to `SeeAllData=false` | Ensures test isolation; prevents reliance on org-specific data |
+| Every test must assert meaningful outcomes | Tests with no assertions prove nothing and give false confidence |
+| Test bulk behavior with 251+ records | Triggers process in batches of 200; 251 records crosses the boundary |
+| Use factories / `@TestSetup` when they improve clarity | Consistent data creation in one place; rolled back between test methods |
+| Pair `Test.startTest()` with `Test.stopTest()` for async | Ensures async operations (queueable, future) complete before assertions |
+| Do not hide flaky org dependencies inside tests | Prevents intermittent failures tied to org state |
+
+---
+
+## Gotchas
+
+| Issue | Resolution |
+|-------|------------|
+| Test passes locally but fails in CI org | Check for `SeeAllData=true` or undeclared dependencies on org-specific records |
+| Coverage drops unexpectedly after refactor | Run focused class-level tests first, then widen to `RunLocalTests` to confirm |
+| "Uncommitted work pending" error in callout test | DML and HTTP callouts cannot be mixed in the same test context without `Test.startTest()` wrapping |
+| Mock not taking effect in test | Ensure `Test.setMock()` is called before the code that makes the callout |
+| `@TestSetup` data missing in test method | `@TestSetup` data is committed per test method — re-query it; do not store in static variables |
+
+---
+
+## Output Format
+
+When finishing, report in this order:
+1. **What tests were run**
+2. **Pass/fail summary**
+3. **Coverage result**
+4. **Root-cause findings**
+5. **Fix or next-run recommendation**
+
+Suggested shape:
+
+```text
+Test run: <scope>
+Org: <alias>
+Result: <passed / partial / failed>
+Coverage: <percent / key classes>
+Issues: <highest-signal failures>
+Next step: <fix class, add test, rerun scope, or widen regression>
+```
+
+---
+
+## Cross-Skill Integration
+
+| Need | Delegate to | Reason |
+|------|-------------|--------|
+| Fix production code or author test classes | `generating-apex` skill | Code generation and repair |
+| Create bulk / edge-case test data | [handling-sf-data](../handling-sf-data/SKILL.md) | Realistic test datasets |
+| Deploy updated tests to org | [deploying-metadata](../deploying-metadata/SKILL.md) | Deployment workflows |
+| Inspect detailed runtime logs | [debugging-apex-logs](../debugging-apex-logs/SKILL.md) | Deeper failure analysis |
+
+---
+
+## Reference File Index
+
+| File | When to read |
+|------|-------------|
+| `references/cli-commands.md` | All `sf apex run test` command flags, output formats, async execution, and coverage commands |
+| `references/test-patterns.md` | Test class templates — basic, bulk (251+), mock callout, and data factory patterns |
+| `references/testing-best-practices.md` | Core testing principles — AAA pattern, naming conventions, bulk, negative, and mock strategies |
+| `references/test-fix-loop.md` | Agentic test-fix loop implementation and failure analysis decision tree |
+| `references/mocking-patterns.md` | HttpCalloutMock, DML mocking, StubProvider, and selector mocking patterns |
+| `references/performance-optimization.md` | Techniques to reduce test execution time — DML mocking, SOQL mocking, loop optimizations |
+| `assets/basic-test.cls` | Template: standard test class with `@TestSetup`, positive / negative / bulk / edge-case methods |
+| `assets/bulk-test.cls` | Template: bulk test with 251+ records that crosses the 200-record trigger batch boundary |
+| `assets/mock-callout-test.cls` | Template: HTTP callout mock using `HttpCalloutMock` |
+| `assets/test-data-factory.cls` | Template: reusable `TestDataFactory` with create and insert helpers |
+| `assets/dml-mock.cls` | Template: `IDML` interface + `DMLMock` implementation for database-free unit tests |
+| `assets/stub-provider-example.cls` | Template: `StubProvider`-based dependency injection stub |
+| `hooks/scripts/parse-test-results.py` | Post-tool hook — parses `sf apex run test` JSON output and formats failures for the auto-fix loop |
+
+---
+
+## Score Guide
+
+| Score | Meaning |
+|---|---|
+| 108+ | strong production-grade test confidence |
+| 96–107 | good test suite with minor gaps |
+| 84–95 | acceptable but strengthen coverage / assertions |
+| < 84 | below standard; revise before relying on it |

package/skills/running-apex-tests/assets/basic-test.cls

@@ -0,0 +1,169 @@
+/**
+ * @description Test class for {{ClassName}}
+ *              Tests core functionality with positive, negative, and bulk scenarios.
+ * @created     {{Date}}
+ * @coverage    Target: 90%+
+ */
+@IsTest
+private class {{ClassName}}Test {
+
+    // ═══════════════════════════════════════════════════════════════════════════
+    // TEST DATA SETUP
+    // ═══════════════════════════════════════════════════════════════════════════
+
+    @TestSetup
+    static void setupTestData() {
+        // Create test data using Test Data Factory pattern
+        // This data is available to all test methods and rolled back after each
+        List<{{ObjectName}}> records = TestDataFactory.create{{ObjectName}}s(5);
+        insert records;
+    }
+
+    // ═══════════════════════════════════════════════════════════════════════════
+    // POSITIVE TESTS
+    // ═══════════════════════════════════════════════════════════════════════════
+
+    /**
+     * @description Tests successful {{methodUnderTest}} with valid input
+     */
+    @IsTest
+    static void test{{MethodUnderTest}}_ValidInput_Success() {
+        // ─────────────────────────────────────────────────────────────────────
+        // GIVEN - Set up test conditions
+        // ─────────────────────────────────────────────────────────────────────
+        {{ObjectName}} testRecord = [SELECT Id, Name FROM {{ObjectName}} LIMIT 1];
+        // TODO: Add any additional setup needed
+
+        // ─────────────────────────────────────────────────────────────────────
+        // WHEN - Execute the method under test
+        // ─────────────────────────────────────────────────────────────────────
+        Test.startTest();
+        {{ReturnType}} result = {{ClassName}}.{{methodUnderTest}}(testRecord);
+        Test.stopTest();
+
+        // ─────────────────────────────────────────────────────────────────────
+        // THEN - Verify expected outcomes
+        // ─────────────────────────────────────────────────────────────────────
+        Assert.isNotNull(result, 'Result should not be null');
+        // TODO: Add specific assertions for expected values
+        // Assert.areEqual(expectedValue, result, 'Result should match expected value');
+    }
+
+    // ═══════════════════════════════════════════════════════════════════════════
+    // NEGATIVE TESTS
+    // ═══════════════════════════════════════════════════════════════════════════
+
+    /**
+     * @description Tests {{methodUnderTest}} throws exception with null input
+     */
+    @IsTest
+    static void test{{MethodUnderTest}}_NullInput_ThrowsException() {
+        // ─────────────────────────────────────────────────────────────────────
+        // GIVEN - Null input
+        // ─────────────────────────────────────────────────────────────────────
+        {{ObjectName}} nullRecord = null;
+
+        // ─────────────────────────────────────────────────────────────────────
+        // WHEN/THEN - Verify exception is thrown
+        // ─────────────────────────────────────────────────────────────────────
+        try {
+            Test.startTest();
+            {{ClassName}}.{{methodUnderTest}}(nullRecord);
+            Test.stopTest();
+            Assert.fail('Expected exception was not thrown');
+        } catch (IllegalArgumentException e) {
+            Assert.isTrue(
+                e.getMessage().containsIgnoreCase('null') ||
+                e.getMessage().containsIgnoreCase('required'),
+                'Error message should indicate null/required issue: ' + e.getMessage()
+            );
+        }
+    }
+
+    /**
+     * @description Tests {{methodUnderTest}} handles invalid data gracefully
+     */
+    @IsTest
+    static void test{{MethodUnderTest}}_InvalidData_ReturnsError() {
+        // ─────────────────────────────────────────────────────────────────────
+        // GIVEN - Invalid input data
+        // ─────────────────────────────────────────────────────────────────────
+        {{ObjectName}} invalidRecord = new {{ObjectName}}(
+            // TODO: Set invalid field values that should fail validation
+        );
+
+        // ─────────────────────────────────────────────────────────────────────
+        // WHEN - Execute with invalid data
+        // ─────────────────────────────────────────────────────────────────────
+        Test.startTest();
+        // TODO: Call method and capture result/exception
+        Test.stopTest();
+
+        // ─────────────────────────────────────────────────────────────────────
+        // THEN - Verify appropriate error handling
+        // ─────────────────────────────────────────────────────────────────────
+        // TODO: Assert error message or state
+    }
+
+    // ═══════════════════════════════════════════════════════════════════════════
+    // BULK TESTS (251+ records)
+    // ═══════════════════════════════════════════════════════════════════════════
+
+    /**
+     * @description Tests {{methodUnderTest}} handles bulk operations (251 records)
+     *              251 records crosses the 200-record trigger batch boundary
+     */
+    @IsTest
+    static void test{{MethodUnderTest}}_BulkOperation_Success() {
+        // ─────────────────────────────────────────────────────────────────────
+        // GIVEN - 251 records (crosses 200-record batch boundary)
+        // ─────────────────────────────────────────────────────────────────────
+        List<{{ObjectName}}> bulkRecords = TestDataFactory.create{{ObjectName}}s(251);
+
+        // ─────────────────────────────────────────────────────────────────────
+        // WHEN - Process bulk records
+        // ─────────────────────────────────────────────────────────────────────
+        Test.startTest();
+        insert bulkRecords;  // Triggers fire in batches of 200, then 51
+        Test.stopTest();
+
+        // ─────────────────────────────────────────────────────────────────────
+        // THEN - Verify all records processed without governor limit issues
+        // ─────────────────────────────────────────────────────────────────────
+        Integer recordCount = [SELECT COUNT() FROM {{ObjectName}}];
+        Assert.isTrue(recordCount >= 251, 'All 251 records should be processed');
+
+        // Verify governor limits not approached
+        Assert.isTrue(Limits.getQueries() < 90,
+            'SOQL queries should stay well under limit: ' + Limits.getQueries() + '/100');
+        Assert.isTrue(Limits.getDmlStatements() < 140,
+            'DML statements should stay under limit: ' + Limits.getDmlStatements() + '/150');
+    }
+
+    // ═══════════════════════════════════════════════════════════════════════════
+    // EDGE CASE TESTS
+    // ═══════════════════════════════════════════════────────────────────────────
+
+    /**
+     * @description Tests {{methodUnderTest}} with empty list input
+     */
+    @IsTest
+    static void test{{MethodUnderTest}}_EmptyList_NoError() {
+        // ─────────────────────────────────────────────────────────────────────
+        // GIVEN - Empty list
+        // ─────────────────────────────────────────────────────────────────────
+        List<{{ObjectName}}> emptyList = new List<{{ObjectName}}>();
+
+        // ─────────────────────────────────────────────────────────────────────
+        // WHEN - Process empty list
+        // ─────────────────────────────────────────────────────────────────────
+        Test.startTest();
+        // TODO: Call method with empty list
+        Test.stopTest();
+
+        // ─────────────────────────────────────────────────────────────────────
+        // THEN - Should handle gracefully (no exception)
+        // ─────────────────────────────────────────────────────────────────────
+        // TODO: Assert appropriate handling
+    }
+}