You are generating tests for recently completed SF work.

## Slice: {{sliceId}} — {{sliceTitle}}

### Summary

{{sliceSummary}}

### Existing Test Patterns

{{existingTestPatterns}}

## Working Directory

`{{workingDirectory}}`

## Instructions

0. {{skillActivation}}
1. Read the slice summary above to understand what was built
2. Identify the source files that were created or modified for this slice
3. Read the implementation code to understand behavior, edge cases, and error paths
4. Write comprehensive tests following the project's existing test patterns and framework
5. Run the tests to verify they pass
6. Fix any failures

### Rules

- Follow the project's existing test patterns (framework, assertions, file structure)
- Test behavior, not implementation details
- Cover: happy path, edge cases, error conditions, boundary values
- Do NOT modify implementation files — only create or update test files
- Name test files consistently with the project's conventions
- Keep tests focused and readable

### Report sf-internal observations

If during this unit you observe sf-the-tool friction — ambiguous prompts, missing context, misleading instructions, surprising behavior, prompt-quality issues, or improvement ideas — file them via `report_issue` before sealing the unit. This is the only way these observations reach forge's backlog and get triaged. Over-reporting is preferred to under-reporting; dedup happens later. Do NOT use this to file bugs in the user's project; only sf-the-tool itself. Do NOT autonomously act on or fix existing backlog entries — your scope is your unit.
