plan-verify 0.0.0-stage → 0.1.0

package/src/text.ts

@@ -0,0 +1,95 @@
+/** Quote a string for human and JSON-adjacent messages. */
+export function displayQuote(value: string): string {
+  let out = "\"";
+  for (let i = 0; i < value.length; i++) {
+    const code = value.charCodeAt(i);
+    if (code === 34 || code === 92) {
+      out += "\\" + value.slice(i, i + 1);
+    } else if (code === 10) {
+      out += "\\n";
+    } else if (code === 13) {
+      out += "\\r";
+    } else if (code === 9) {
+      out += "\\t";
+    } else if (code < 32) {
+      out += "\\u00" + hexByte(code);
+    } else {
+      out += value.slice(i, i + 1);
+    }
+  }
+  return out + "\"";
+}
+
+export function formatInt(value: number): string {
+  return String(Math.trunc(value));
+}
+
+/** Capitalize the first letter when it is a lowercase ascii letter. */
+export function capitalize(text: string): string {
+  if (text.length === 0) return text;
+  const code = text.charCodeAt(0);
+  if (code >= 97 && code <= 122) return String.fromCharCode(code - 32) + text.slice(1);
+  return text;
+}
+
+/** Replace the first whole word. The replacement may itself contain spaces. */
+export function replaceWord(text: string, word: string, replacement: string): string {
+  const end = wordEnd(text, word);
+  if (end < 0) return text;
+  const start = end - word.length;
+  return text.slice(0, start) + replacement + text.slice(end);
+}
+
+/** Turn the first "is" into "was". Other words stay put. */
+export function pastVoice(text: string): string {
+  return replaceWord(text, "is", "was");
+}
+
+function wordEnd(text: string, word: string): number {
+  const target = lowerAscii(word);
+  let start = 0;
+  for (let i = 0; i <= text.length; i++) {
+    if (i === text.length || text.charCodeAt(i) === 32) {
+      if (i > start && lowerAscii(text.slice(start, i)) === target) return i;
+      start = i + 1;
+    }
+  }
+  return -1;
+}
+
+function lowerAscii(text: string): string {
+  let out = "";
+  for (let i = 0; i < text.length; i++) {
+    const code = text.charCodeAt(i);
+    if (code >= 65 && code <= 90) out += String.fromCharCode(code + 32);
+    else out += text.slice(i, i + 1);
+  }
+  return out;
+}
+
+/** "a", "a and b", or "a, b, and c". */
+export function englishList(parts: string[]): string {
+  if (parts.length === 0) return "";
+  if (parts.length === 1) return parts[0];
+  if (parts.length === 2) return parts[0] + " and " + parts[1];
+  let out = "";
+  for (let i = 0; i < parts.length; i++) {
+    if (i === parts.length - 1) out += ", and ";
+    else if (i > 0) out += ", ";
+    out += parts[i];
+  }
+  return out;
+}
+
+export function formatSmtInt(value: number): string {
+  const n = Math.trunc(value);
+  if (n < 0) return "(- " + formatInt(-n) + ")";
+  return formatInt(n);
+}
+
+function hexByte(code: number): string {
+  const hex = "0123456789abcdef";
+  const hi = Math.trunc(code / 16);
+  const lo = code - hi * 16;
+  return hex.slice(hi, hi + 1) + hex.slice(lo, lo + 1);
+}

package/test/fixtures/malformed.ears.md

@@ -0,0 +1,3 @@
+event order_submitted: Bool "The customer submits an order." phrase "an order is submitted"
+
+R1 When an order is submitted, the Order System should fulfill the order.

package/test/fixtures/unknown-phrase.ears.md

@@ -0,0 +1,5 @@
+event order_submitted: Bool "The customer submits an order." phrase "an order is submitted"
+state inventory_available: Bool "Enough stock is on hand to fill the order." phrase "inventory is available"
+output order_fulfilled: Bool "The order is fulfilled." phrase "fulfill the order" outcome "the order was fulfilled" / "the order was not fulfilled"
+
+R1 When an order was submitted, the Order System shall fulfill the order.

package/test/golden/check-fail-json.exit

@@ -0,0 +1 @@
+1

package/test/golden/check-fail-json.stdout

@@ -0,0 +1,13 @@
+{
+  "ok": false,
+  "spec": "examples/order.ears.md",
+  "scenario": "examples/order-fail.json",
+  "violations": [
+    {
+      "id": "R1",
+      "line": 7,
+      "sentence": "WHEN an order is submitted AND inventory is available, THE Order System SHALL fulfill the order.",
+      "because": "An order was submitted and inventory was available, but the order was not fulfilled."
+    }
+  ]
+}

package/test/golden/check-fail.exit

@@ -0,0 +1 @@
+1

package/test/golden/check-fail.stdout

@@ -0,0 +1,7 @@
+spec: examples/order.ears.md
+scenario: examples/order-fail.json
+violations: 1
+
+R1 line 7
+WHEN an order is submitted AND inventory is available, THE Order System SHALL fulfill the order.
+An order was submitted and inventory was available, but the order was not fulfilled.

package/test/golden/check-pass-json.exit

@@ -0,0 +1 @@
+0

package/test/golden/check-pass-json.stdout

@@ -0,0 +1,6 @@
+{
+  "ok": true,
+  "spec": "examples/order.ears.md",
+  "scenario": "examples/order-pass.json",
+  "violations": []
+}

package/test/golden/check-pass.exit

@@ -0,0 +1 @@
+0

package/test/golden/check-pass.stdout

@@ -0,0 +1,3 @@
+spec: examples/order.ears.md
+scenario: examples/order-pass.json
+violations: 0

package/test/golden/emit-smt-json-usage.exit

@@ -0,0 +1 @@
+2

package/test/golden/emit-smt-json-usage.stdout

@@ -0,0 +1,4 @@
+{
+  "ok": false,
+  "error": "usage: plan-verify emit-smt [--json] <spec>"
+}

package/test/golden/emit-smt-json.exit

@@ -0,0 +1 @@
+0

package/test/golden/emit-smt-json.stdout

@@ -0,0 +1,5 @@
+{
+  "ok": true,
+  "spec": "examples/order.ears.md",
+  "smt": "; spec: examples/order.ears.md\n(set-logic ALL)\n; event order_submitted: Bool \"The customer submits an order.\" phrase \"an order is submitted\"\n(declare-fun order_submitted () Bool)\n; state inventory_available: Bool \"Enough stock is on hand to fill the order.\" phrase \"inventory is available\"\n(declare-fun inventory_available () Bool)\n; output order_fulfilled: Bool \"The order is fulfilled.\" phrase \"fulfill the order\" outcome \"the order was fulfilled\" / \"the order was not fulfilled\"\n(declare-fun order_fulfilled () Bool)\n; R1_L7 line 7: WHEN an order is submitted AND inventory is available, THE Order System SHALL fulfill the order.\n(assert (! (=> (and order_submitted inventory_available) order_fulfilled) :named R1_L7))"
+}

package/test/golden/emit-smt.exit

@@ -0,0 +1 @@
+0

package/test/golden/emit-smt.stdout

@@ -0,0 +1,10 @@
+; spec: examples/order.ears.md
+(set-logic ALL)
+; event order_submitted: Bool "The customer submits an order." phrase "an order is submitted"
+(declare-fun order_submitted () Bool)
+; state inventory_available: Bool "Enough stock is on hand to fill the order." phrase "inventory is available"
+(declare-fun inventory_available () Bool)
+; output order_fulfilled: Bool "The order is fulfilled." phrase "fulfill the order" outcome "the order was fulfilled" / "the order was not fulfilled"
+(declare-fun order_fulfilled () Bool)
+; R1_L7 line 7: WHEN an order is submitted AND inventory is available, THE Order System SHALL fulfill the order.
+(assert (! (=> (and order_submitted inventory_available) order_fulfilled) :named R1_L7))

package/test/golden/help.exit

@@ -0,0 +1 @@
+0

package/test/golden/help.stdout

@@ -0,0 +1,8 @@
+usage:
+  plan-verify check [--json] <spec> --input <scenario>
+  plan-verify emit-smt [--json] <spec>
+  plan-verify lint [--json] <spec>
+  plan-verify report <spec>
+  plan-verify scenarios [--json] <spec>
+  plan-verify policy [--json] <spec> [--property <file>]
+  plan-verify help

package/test/golden/lint-awkward.exit

@@ -0,0 +1 @@
+1

package/test/golden/lint-awkward.stdout

@@ -0,0 +1,29 @@
+spec: examples/order-awkward.ears.md
+conflicts: 0
+gaps: 0
+misuse: 0
+wording: 5
+redundant: 0
+duplicate: 0
+vacuous: 0
+unused: 0
+
+wording line 7
+"shall the ... is ..." is awkward. Write the response as a verb phrase, such as "bill at most 2 seats", and bind it with as.
+When start the subscription, the Checkout shall the lane is fulfill.
+
+wording line 7
+"When" needs a condition with "is", not a bare verb. "When the subscription is started" is the form.
+When start the subscription, the Checkout shall the lane is fulfill.
+
+wording line 8
+"shall the ... is ..." is awkward. Write the response as a verb phrase, such as "bill at most 2 seats", and bind it with as.
+When not start the subscription, the Checkout shall the lane is hold.
+
+wording line 8
+"When" needs a condition with "is", not a bare verb. "When the subscription is started" is the form.
+When not start the subscription, the Checkout shall the lane is hold.
+
+wording line 8
+The trigger is a bare negation. Write a positive condition, such as "When a non-member asks", or declare a positive event.
+When not start the subscription, the Checkout shall the lane is hold.

package/test/golden/lint-chain.exit

@@ -0,0 +1 @@
+1

package/test/golden/lint-chain.stdout

@@ -0,0 +1,56 @@
+spec: examples/order-chain.ears.md
+conflicts: 1
+gaps: 0
+misuse: 0
+wording: 0
+redundant: 0
+duplicate: 0
+vacuous: 0
+unused: 0
+
+conflict {R1, R2, R3}
+R1, R2, and R3 cannot all hold.
+
+R1 line 7
+When an order is submitted, the Order System shall accept the order.
+
+R2 line 8
+When the order is accepted, the Order System shall ship the order.
+
+R3 line 9
+When an order is submitted, the Order System shall not ship the order.
+
+They clash when an order was submitted.
+R1 requires that the order was accepted.
+R3 requires that the order was not shipped.
+
+Example scenario:
+{
+  "order_submitted": true,
+  "order_accepted": true,
+  "order_shipped": true
+}
+This scenario keeps R1 and R2 and breaks R3.
+
+Suggested fix: ask which requirement should win. Removing any one of R1, R2, and R3 leaves the rest consistent.
+
+Candidate repairs follow. This report does not choose one.
+
+repair drop R1
+One repair is to drop R1 and keep R2 and R3 as written.
+When the order is accepted, the Order System shall ship the order.
+When an order is submitted, the Order System shall not ship the order.
+
+repair drop R2
+One repair is to drop R2 and keep R1 and R3 as written.
+When an order is submitted, the Order System shall accept the order.
+When an order is submitted, the Order System shall not ship the order.
+
+repair drop R3
+One repair is to drop R3 and keep R1 and R2 as written.
+When an order is submitted, the Order System shall accept the order.
+When the order is accepted, the Order System shall ship the order.
+
+repair strengthen R2
+One repair is to add "and an order is not submitted" to the condition of R2. R1 and R3 stay as written.
+When the order is accepted and an order is not submitted, the Order System shall ship the order.

package/test/golden/lint-checkout.exit

@@ -0,0 +1 @@
+1

package/test/golden/lint-checkout.stdout

@@ -0,0 +1,301 @@
+spec: examples/checkout.ears.md
+conflicts: 3
+gaps: 2
+misuse: 0
+wording: 0
+redundant: 23
+duplicate: 0
+vacuous: 0
+unused: 0
+
+conflict {R8, R12, R14}
+R8, R12, and R14 cannot all hold.
+
+R8 line 32
+When the customer is subscribing and the customer is not cancelling and the customer is signed in, the Checkout shall start the subscription.
+
+R12 line 36
+When the subscription is started, the Checkout shall route the order to the fulfill lane.
+
+R14 line 38
+When the customer is subscribing, the Checkout shall route the order to the hold lane.
+
+They clash when the cart was not open, an item was not added, checkout was not started, payment was not submitted, payment was not declined, the address was not confirmed, the customer was subscribing, the customer was not cancelling, the customer was signed in, a card was not saved, and stock was not available.
+R8 requires that the subscription was started.
+R14 requires that the order was routed to the hold lane.
+
+Example scenario:
+{
+  "cart_opened": false,
+  "item_added": false,
+  "checkout_started": false,
+  "payment_submitted": false,
+  "payment_declined": false,
+  "address_confirmed": false,
+  "subscribe_clicked": true,
+  "cancel_requested": false,
+  "signed_in": true,
+  "card_saved": false,
+  "stock_ok": false,
+  "order_accepted": false,
+  "order_rejected": false,
+  "subscription_started": true,
+  "receipt_sent": false,
+  "lane": "fulfill",
+  "billed_seats": 1
+}
+This scenario keeps R8 and R12 and breaks R14.
+
+Suggested fix: ask which requirement should win. Removing any one of R8, R12, and R14 leaves the rest consistent.
+
+Candidate repairs follow. This report does not choose one.
+
+repair drop R8
+One repair is to drop R8 and keep R12 and R14 as written.
+When the subscription is started, the Checkout shall route the order to the fulfill lane.
+When the customer is subscribing, the Checkout shall route the order to the hold lane.
+
+repair drop R12
+One repair is to drop R12 and keep R8 and R14 as written.
+When the customer is subscribing and the customer is not cancelling and the customer is signed in, the Checkout shall start the subscription.
+When the customer is subscribing, the Checkout shall route the order to the hold lane.
+
+repair drop R14
+One repair is to drop R14 and keep R8 and R12 as written.
+When the customer is subscribing and the customer is not cancelling and the customer is signed in, the Checkout shall start the subscription.
+When the subscription is started, the Checkout shall route the order to the fulfill lane.
+
+repair strengthen R12
+One repair is to add "and the customer is not subscribing" to the condition of R12. R8 and R14 stay as written.
+When the subscription is started and the customer is not subscribing, the Checkout shall route the order to the fulfill lane.
+
+repair strengthen R12
+One repair is to add "and the customer is cancelling" to the condition of R12. R8 and R14 stay as written.
+When the subscription is started and the customer is cancelling, the Checkout shall route the order to the fulfill lane.
+
+repair strengthen R12
+One repair is to add "and the customer is not signed in" to the condition of R12. R8 and R14 stay as written.
+When the subscription is started and the customer is not signed in, the Checkout shall route the order to the fulfill lane.
+
+repair strengthen R14
+One repair is to add "and the customer is cancelling" to the condition of R14. R8 and R12 stay as written.
+When the customer is subscribing and the customer is cancelling, the Checkout shall route the order to the hold lane.
+
+repair strengthen R14
+One repair is to add "and the customer is not signed in" to the condition of R14. R8 and R12 stay as written.
+When the customer is subscribing and the customer is not signed in, the Checkout shall route the order to the hold lane.
+
+conflict {R1, R4}
+R1 and R4 cannot both hold.
+
+R1 line 25
+When payment is submitted and the address is confirmed, the Checkout shall accept the order.
+
+R4 line 28
+When payment is submitted and the address is confirmed, the Checkout shall not accept the order.
+
+They clash when the cart was not open, an item was not added, checkout was not started, payment was submitted, payment was not declined, the address was confirmed, the customer was not subscribing, the customer was not cancelling, the customer was not signed in, a card was not saved, and stock was not available.
+R1 requires that the order was accepted.
+R4 requires that the order was not accepted.
+
+Example scenario:
+{
+  "cart_opened": false,
+  "item_added": false,
+  "checkout_started": false,
+  "payment_submitted": true,
+  "payment_declined": false,
+  "address_confirmed": true,
+  "subscribe_clicked": false,
+  "cancel_requested": false,
+  "signed_in": false,
+  "card_saved": false,
+  "stock_ok": false,
+  "order_accepted": true,
+  "order_rejected": false,
+  "subscription_started": false,
+  "receipt_sent": false,
+  "lane": "hold",
+  "billed_seats": 1
+}
+This scenario keeps R1 and breaks R4.
+
+Suggested fix: ask which requirement should win. To keep R1, remove R4. To keep R4, remove R1.
+
+Candidate repairs follow. This report does not choose one.
+
+repair drop R1
+One repair is to drop R1 and keep R4 as written.
+When payment is submitted and the address is confirmed, the Checkout shall not accept the order.
+
+repair drop R4
+One repair is to drop R4 and keep R1 as written.
+When payment is submitted and the address is confirmed, the Checkout shall accept the order.
+
+conflict {R15, R16}
+R15 and R16 cannot both hold.
+
+R15 line 39
+When checkout is started and stock is available, the Checkout shall bill at most 2 seats.
+
+R16 line 40
+When checkout is started and stock is available, the Checkout shall bill 3 seats.
+
+They clash when the cart was not open, an item was not added, checkout was started, payment was not submitted, payment was not declined, the address was not confirmed, the customer was not subscribing, the customer was not cancelling, the customer was not signed in, a card was not saved, and stock was available.
+R15 requires that at most 2 seats were billed.
+R16 requires that 3 seats were billed.
+
+Example scenario:
+{
+  "cart_opened": false,
+  "item_added": false,
+  "checkout_started": true,
+  "payment_submitted": false,
+  "payment_declined": false,
+  "address_confirmed": false,
+  "subscribe_clicked": false,
+  "cancel_requested": false,
+  "signed_in": false,
+  "card_saved": false,
+  "stock_ok": true,
+  "order_accepted": false,
+  "order_rejected": false,
+  "subscription_started": false,
+  "receipt_sent": false,
+  "lane": "hold",
+  "billed_seats": 1
+}
+This scenario keeps R15 and breaks R16.
+
+Suggested fix: ask which requirement should win. To keep R15, remove R16. To keep R16, remove R15.
+
+Candidate repairs follow. This report does not choose one.
+
+repair drop R15
+One repair is to drop R15 and keep R16 as written.
+When checkout is started and stock is available, the Checkout shall bill 3 seats.
+
+repair drop R16
+One repair is to drop R16 and keep R15 as written.
+When checkout is started and stock is available, the Checkout shall bill at most 2 seats.
+
+gap receipt_sent
+Nothing says whether a receipt was sent when the cart was open, an item was added, checkout was started, payment was submitted, payment was declined, the address was not confirmed, the customer was subscribing, the customer was cancelling, the customer was signed in, a card was saved, and stock was available. Suggested fix: add a requirement for this situation, and ask what the system shall do. Do not choose the response.
+
+gap billed_seats
+Nothing covers the billed seats when the cart was open, an item was added, checkout was started, payment was submitted, payment was declined, the address was confirmed, the customer was subscribing, the customer was cancelling, the customer was signed in, a card was saved, and stock was not available. Suggested fix: add a requirement for this situation, and ask what the system shall do. Do not choose the response.
+
+redundant R10 line 34
+R10 adds nothing. Whenever the requirements outside a conflict hold, R10 holds too.
+When the customer is cancelling, the Checkout shall not start the subscription.
+Suggested fix: remove R10, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R25 line 49
+R25 adds nothing. Whenever the requirements outside a conflict hold, R25 holds too.
+When payment is submitted and the address is not confirmed and the customer is signed in, the Checkout shall not accept the order.
+Suggested fix: remove R25, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R26 line 50
+R26 adds nothing. Whenever the requirements outside a conflict hold, R26 holds too.
+When payment is submitted and the address is not confirmed and the cart is open, the Checkout shall not accept the order.
+Suggested fix: remove R26, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R27 line 51
+R27 adds nothing. Whenever the requirements outside a conflict hold, R27 holds too.
+When payment is submitted and the address is not confirmed and an item is added, the Checkout shall not accept the order.
+Suggested fix: remove R27, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R28 line 52
+R28 adds nothing. Whenever the requirements outside a conflict hold, R28 holds too.
+When payment is submitted and the address is not confirmed and a card is saved, the Checkout shall not accept the order.
+Suggested fix: remove R28, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R29 line 53
+R29 adds nothing. Whenever the requirements outside a conflict hold, R29 holds too.
+When payment is not submitted and the cart is open, the Checkout shall not accept the order.
+Suggested fix: remove R29, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R30 line 54
+R30 adds nothing. Whenever the requirements outside a conflict hold, R30 holds too.
+When payment is not submitted and an item is added, the Checkout shall not accept the order.
+Suggested fix: remove R30, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R31 line 55
+R31 adds nothing. Whenever the requirements outside a conflict hold, R31 holds too.
+When payment is not submitted and checkout is started, the Checkout shall not accept the order.
+Suggested fix: remove R31, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R32 line 56
+R32 adds nothing. Whenever the requirements outside a conflict hold, R32 holds too.
+When payment is not submitted and the customer is signed in, the Checkout shall not accept the order.
+Suggested fix: remove R32, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R33 line 57
+R33 adds nothing. Whenever the requirements outside a conflict hold, R33 holds too.
+When payment is not submitted and a card is saved, the Checkout shall not accept the order.
+Suggested fix: remove R33, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R34 line 58
+R34 adds nothing. Whenever the requirements outside a conflict hold, R34 holds too.
+When payment is not submitted and stock is available, the Checkout shall not accept the order.
+Suggested fix: remove R34, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R35 line 59
+R35 adds nothing. Whenever the requirements outside a conflict hold, R35 holds too.
+When payment is not submitted and the customer is subscribing, the Checkout shall not accept the order.
+Suggested fix: remove R35, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R39 line 63
+R39 adds nothing. Whenever the requirements outside a conflict hold, R39 holds too.
+When the customer is subscribing and the customer is cancelling, the Checkout shall not start the subscription.
+Suggested fix: remove R39, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R40 line 64
+R40 adds nothing. Whenever the requirements outside a conflict hold, R40 holds too.
+When the customer is cancelling and the cart is open, the Checkout shall not start the subscription.
+Suggested fix: remove R40, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R41 line 65
+R41 adds nothing. Whenever the requirements outside a conflict hold, R41 holds too.
+When the customer is cancelling and an item is added, the Checkout shall not start the subscription.
+Suggested fix: remove R41, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R42 line 66
+R42 adds nothing. Whenever the requirements outside a conflict hold, R42 holds too.
+When the customer is not subscribing and the cart is open, the Checkout shall not start the subscription.
+Suggested fix: remove R42, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R43 line 67
+R43 adds nothing. Whenever the requirements outside a conflict hold, R43 holds too.
+When the customer is not subscribing and an item is added, the Checkout shall not start the subscription.
+Suggested fix: remove R43, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R44 line 68
+R44 adds nothing. Whenever the requirements outside a conflict hold, R44 holds too.
+When the customer is not subscribing and a card is saved, the Checkout shall not start the subscription.
+Suggested fix: remove R44, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R45 line 69
+R45 adds nothing. Whenever the requirements outside a conflict hold, R45 holds too.
+When the customer is subscribing and the customer is not cancelling and the customer is not signed in and the cart is open, the Checkout shall not start the subscription.
+Suggested fix: remove R45, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R46 line 70
+R46 adds nothing. Whenever the requirements outside a conflict hold, R46 holds too.
+When the subscription is not started and the cart is open, the Checkout shall route the order to the hold lane.
+Suggested fix: remove R46, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R47 line 71
+R47 adds nothing. Whenever the requirements outside a conflict hold, R47 holds too.
+When the subscription is not started and an item is added, the Checkout shall route the order to the hold lane.
+Suggested fix: remove R47, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R49 line 73
+R49 adds nothing. Whenever the requirements outside a conflict hold, R49 holds too.
+When payment is submitted and the address is confirmed and the customer is signed in, the Checkout shall send a receipt.
+Suggested fix: remove R49, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.
+
+redundant R50 line 74
+R50 adds nothing. Whenever the requirements outside a conflict hold, R50 holds too.
+When payment is submitted and the address is confirmed and the cart is open, the Checkout shall send a receipt.
+Suggested fix: remove R50, or ask whether it was meant to say something the others do not already require. Do not delete it until the PM agrees.

package/test/golden/lint-clean.exit

@@ -0,0 +1 @@
+0

package/test/golden/lint-clean.stdout

@@ -0,0 +1,9 @@
+spec: examples/order-covered.ears.md
+conflicts: 0
+gaps: 0
+misuse: 0
+wording: 0
+redundant: 0
+duplicate: 0
+vacuous: 0
+unused: 0

package/test/golden/lint-clear.exit

@@ -0,0 +1 @@
+0