@seanmars/tospec 0.26.0-beta → 0.27.0

package/schemas/issue/schema.yaml

@@ -12,15 +12,19 @@ artifacts:
     requires: []
     instruction: |
       Diagnose and write the issue task: first build a tight feedback loop (one
-      command that turns this bug red), list as many falsifiable hypotheses as
+      command that turns this bug red; for a performance bug, a measured number
+      recorded with its run count, range, and limiter), list as many falsifiable hypotheses as
       the evidence supports (one or two is fine when the loop already points at
       one cause) and rank them, verify each, then write down the root cause.
       Redact secrets as <REDACTED> in everything pasted here: task.md is
       committed and kept in the archive. Quote only the lines that carry the
       signal, and do not redact the error message itself. A step that needs
       the user's login is theirs to run; do not capture its output.
-      Contents: root-cause analysis, fix plan, test plan (why existing tests missed it / which edge
-      cases are missing), and a task checkbox list.
+      Contents: root-cause analysis, fix plan (why it fixes where the state
+      went wrong rather than guarding where it surfaced, and the one fact the
+      fix is safe because of, proven or marked unproven), test plan (why
+      existing tests missed it / which edge cases are missing), and a task
+      checkbox list.
     validation:
       requiredSections: [Feedback Loop, Root Cause, Fix Plan, Test Plan, Tasks]
   - id: specs