create-pathfinder 1.5.0 → 1.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -53,6 +53,25 @@ Choose tests by behavior and risk:
|
|
|
53
53
|
|
|
54
54
|
Avoid tests that only reproduce implementation detail.
|
|
55
55
|
|
|
56
|
+
## Verification Evidence
|
|
57
|
+
|
|
58
|
+
These apply to any claim that something works — a test, a manual check, or a
|
|
59
|
+
verification step in a feature's acceptance criteria.
|
|
60
|
+
|
|
61
|
+
- **Exercise the artifact a user receives, the way a user exercises it.** A
|
|
62
|
+
hand-written sample of generated output, a local imitation of an external
|
|
63
|
+
system, or the working tree in place of the built and published thing is
|
|
64
|
+
evidence about the stand-in, not about the artifact. Prefer one check against
|
|
65
|
+
the real artifact over several against convenient substitutes.
|
|
66
|
+
- **When a mechanism can fail by doing nothing, observe that the right thing
|
|
67
|
+
happened.** A clean exit says the command ran. It does not say the effect
|
|
68
|
+
occurred, and a step that silently does nothing usually reports success.
|
|
69
|
+
- **Beware a check whose every input it supplied itself.** If the test chose the
|
|
70
|
+
fixtures, the environment, and the trigger, it has confirmed its own
|
|
71
|
+
assumptions. Name which inputs came from the real system.
|
|
72
|
+
- State what was verified and what was only reasoned about. An unobserved
|
|
73
|
+
criterion is recorded as unobserved, not as passed.
|
|
74
|
+
|
|
56
75
|
## Dependencies
|
|
57
76
|
|
|
58
77
|
Before adding one, assess necessity, maintenance, security, runtime cost, licensing, portability, and simpler alternatives. Follow the approval policy in `context/ai-interaction.md`.
|
package/package.json
CHANGED
|
@@ -8,8 +8,8 @@ description: Close an accepted feature through final verification, records, deli
|
|
|
8
8
|
1. Confirm review findings are resolved or explicitly accepted.
|
|
9
9
|
2. Run final project-appropriate verification.
|
|
10
10
|
3. Confirm each acceptance criterion with evidence.
|
|
11
|
-
4. Follow the approved commit, PR, merge, changelog, versioning, release, and deployment policy—requesting approval where required.
|
|
12
|
-
5. Append the durable outcome to `context/history.md
|
|
11
|
+
4. Follow the approved commit, PR, merge, changelog, versioning, release, and deployment policy—requesting approval where required. After the merge, verify the merged mainline and clean up the merged branch as that policy requires.
|
|
12
|
+
5. Append the durable outcome to `context/history.md` while completing the feature, not afterwards. If the feature was merged without this skill running, still write the entry and record that it was written after the fact.
|
|
13
13
|
6. Mark/reset `context/current-feature.md` and identify the next action.
|
|
14
14
|
7. Offer or invoke `learn-feature` when learning is enabled.
|
|
15
15
|
8. Produce a compact completion summary.
|