@xera-ai/skills 0.14.0 → 0.15.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @xera-ai/skills
 
+## 0.15.0
+
+### Minor Changes
+
+- [#123](https://github.com/xera-ai/xera/pull/123) [`e2f8694`](https://github.com/xera-ai/xera/commit/e2f8694017cc06f00515d8dc605ec7c2a8634925) Thanks [@thanhtrinity](https://github.com/thanhtrinity)! - deterministic OpenAPI loading + opt-in sample tickets (auto-generated from [#123](https://github.com/xera-ai/xera/issues/123))
+
 ## 0.14.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xera-ai/skills",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "files": [
     "*.md",
     "version.json"

package/xera-script.md

@@ -19,12 +19,9 @@ The user invoked `/xera-script <TICKET>`. If no key, ask.
 
    Follow that prompt's hard rules.
 
-   When `adapter === "http"` AND `xera.config.ts` has `http.spec` configured, additionally:
-   - Load the OpenAPI spec at `http.spec` (path or URL).
-   - Find the operation referenced by the failing Gherkin step (matching method + path).
-   - Pass the dereferenced operation schema to your generation context as the `openapi` input.
-
-   When `adapter === "http"` and no `http.spec`: pass `openapi: null` to your generation context.
+   When `adapter === "http"`, additionally:
+   - Run `bun run xera:openapi-resolve {{TICKET}}` — this writes `.xera/{{TICKET}}/openapi-input.json`, a deterministic JSON file containing `{ openapi: <dereferenced doc> | null }`. The subcommand handles path/URL resolution and `$ref` dereferencing for you; never read the raw OpenAPI file yourself.
+   - Read `.xera/{{TICKET}}/openapi-input.json` and pass the value of its `openapi` field to your generation context as the `openapi` input (it will be `null` when `http.spec` is not configured or the spec failed to load).
 
 5. Before reading the test.feature + story.md content into your generation context, mint a fresh per-invocation nonce by running: