chore: improve prompting for templates

Author: mefellows

README.md

@@ -29,11 +29,11 @@ pactflow-ai generate \
   --output ./src/api.pact.spec.ts \
   --language typescript \
   --openapi ./products.yml \
-  --endpoint "/product/{id}" \
+  --endpoint "**" \
   --code ./src/product.js \
   --code ./src/api.js \
   --template ./src/pact.test.template \
-  --instructions "Write test cases for the positive (HTTP 200) scenario and negative scenarios, specifically the case of 400, 401 and 404"
+  --instructions @./src/test.instructions.txt
 ```
 
 #### Other variations

src/pact.test.template

@@ -11,6 +11,7 @@ describe("🧱 Thing API", () => {
     consumer: "ThingConsumer",
     provider: "ThingProvider",
     spec: SpecificationVersion.SPECIFICATION_VERSION_V4,
+    logLevel: "error",
   });
 
   // Level 2 - Describe block for the specific API endpoint

src/test.instructions.txt

@@ -1,5 +1,7 @@
 * Make sure to cover happy and non-happy paths
   * Specifically, ensure to include test cases for the positive (HTTP 200) scenario and negative scenarios, specifically the case of 400, 401 and 404
+* Only include endpoints/properties used by the API client - do not include additional fields in the OAS that are not in the client code
+  * You can check the properties used in the Product class to help make this determination
 * Use the Jest testing framework
 * Use the native Jest expect (https://jestjs.io/docs/expect) matchers such as `toEqual` and `toBeTruthy`
 * Prefer the use of the async/await pattern when using Promises