@xera-ai/skills 0.12.2 → 0.12.3
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.
- package/CHANGELOG.md +6 -0
- package/package.json +1 -1
- package/xera-run.md +6 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @xera-ai/skills
|
|
2
2
|
|
|
3
|
+
## 0.12.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#111](https://github.com/xera-ai/xera/pull/111) [`ca549e7`](https://github.com/xera-ai/xera/commit/ca549e7d8bd67bd1f48fce41ce7fadefce81b0a4) Thanks [@thanhtrinity](https://github.com/thanhtrinity)! - surface silent modifiesAreas=[] fallback across graph-record, doctor, xera-run (auto-generated from [#111](https://github.com/xera-ai/xera/issues/111))
|
|
8
|
+
|
|
3
9
|
## 0.12.2
|
|
4
10
|
|
|
5
11
|
## 0.12.1
|
package/package.json
CHANGED
package/xera-run.md
CHANGED
|
@@ -14,9 +14,13 @@ If non-zero exit → STOP. Show the output verbatim. Suggest the user fix env an
|
|
|
14
14
|
|
|
15
15
|
## Step 1 — Fetch
|
|
16
16
|
|
|
17
|
-
Follow the same instructions as `xera-fetch.md`, but never prompt the user about re-fetching here
|
|
17
|
+
Follow the same instructions as `xera-fetch.md`, but never prompt the user about re-fetching here.
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
**Sub-steps 1–4 of xera-fetch (Jira call → write `story.md` + `meta.json`)**: skip if `story.md` exists AND `meta.json` shows a `story_hash` < 24 hours old. Otherwise refresh.
|
|
20
|
+
|
|
21
|
+
**Sub-step 5 of xera-fetch (extract-areas → `graph-input.json`)**: gate this on **file existence**, not story freshness. If `.xera/{{TICKET}}/graph-input.json` is missing or fails `JSON.parse`, run the `extract-areas.md` prompt and (over)write the file — even when sub-steps 1–4 were skipped. This is cheap, idempotent, and required by Step 1.5 and by downstream coverage/impact features. Without it, `xera:graph-record fetch` silently records `modifiesAreas=[]` (see [#109](https://github.com/xera-ai/xera/issues/109)).
|
|
22
|
+
|
|
23
|
+
**Sub-step 6 of xera-fetch (`xera:graph-record fetch`)**: always run — it's non-fatal and idempotent. Skipping it is what causes the graph to fall out of sync with `.xera/<TICKET>/`.
|
|
20
24
|
|
|
21
25
|
## Step 1.5 — Auto-trigger impact analysis (v0.6.2)
|
|
22
26
|
|