What problem does it solve? Creating a ServeTracker affidavit requires pulling recipient, court caption, documents, and service attempt data from the live engine without falling back to static templates or prohibited filler scripts. ## Core Features & Use Cases - Engine-Only Generation: Uses the live ServeTracker affidavitEngine.ts (staging or production) as the sole source for affidavit creation. - Fact Verification: Reads recipient, court caption, exact documents, and chronological service attempts, deriving sworn wording from the recorded service method. - Guardrails: Prohibits NAPPS forms, static PDF templates, and separate HTML/WeasyPrint generators; never defaults missing method data to personal service. - Use Case: A process server needs a sworn affidavit for a completed serve; the Skill reads the recorded attempts from ServeTracker staging and produces the affidavit via the engine, then verifies with bun test tests/affidavit_engine.test.ts. ## Quick Start Generate a ServeTracker affidavit for the current job using the staging affidavit engine and verify it with the engine test suite.
