@kody-ade/kody-engine 0.4.122 → 0.4.123

package/dist/executables/qa-engineer/profile.json

@@ -9,7 +9,7 @@
       "flag": "--url",
       "type": "string",
       "required": false,
-      "describe": "Base URL the agent should browse. Optional — resolveQaUrl preflight falls back to the goal-branch Vercel deployment (when --goal is set), then $PREVIEW_URL, then qa.fallbackUrl from kody.config.json. Errors if none resolve."
+      "describe": "Base URL the agent should browse. Optional — resolveQaUrl preflight falls back to the goal-branch Vercel deployment (when --goal is set), then $PREVIEW_URL, then the `QA_URL` variable in .kody/variables.json. Errors if none resolve."
     },
     {
       "name": "scope",
@@ -87,7 +87,7 @@
     "preflight": [
       { "script": "resolveQaUrl" },
       { "script": "discoverQaContext" },
-      { "script": "loadQaGuide" },
+      { "script": "loadQaContext" },
       { "script": "loadConventions" },
       { "script": "warmupMcp" },
       { "script": "composePrompt" }

package/dist/executables/qa-engineer/prompt.md

@@ -7,8 +7,7 @@ You may write throwaway artifacts (screenshots, ad-hoc Playwright specs) under `
 Base URL: `{{previewUrl}}` (resolved from: {{previewUrlSource}})
 {{#args.scope}}Focus: **{{args.scope}}**{{/args.scope}}
 {{^args.scope}}Focus: broad smoke across discovered routes.{{/args.scope}}
-{{#args.authProfile}}Auth: a saved Playwright `storageState.json` is available at `{{args.authProfile}}`. Pass it to `mcp__playwright__browser_navigate` via the `storageState` parameter so the session starts pre-authenticated.{{/args.authProfile}}
-{{^args.authProfile}}Auth: log in fresh using credentials from the QA guide if needed.{{/args.authProfile}}
+{{qaAuthBlock}}
 
 Report destination: {{#args.goal}}existing kody goal `{{args.goal}}` (each finding becomes a `goal:{{args.goal}}` task issue){{/args.goal}}{{^args.goal}}{{#args.issue}}existing issue #{{args.issue}} (postflight will comment on it){{/args.issue}}{{^args.issue}}a new kody goal (postflight will append to the goals manifest and open one task issue per finding){{/args.issue}}{{/args.goal}}.
 
@@ -30,9 +29,9 @@ If that errors (timeout, DNS, connection refused), the app is unreachable. STOP
 {{qaContext}}
 ```
 
-# QA guide (committed in the repo — authoritative over the auto-discovery above)
+# QA scenarios & notes (hand-written, authoritative over auto-discovery above)
 
-{{qaGuide}}
+{{qaProfile}}
 
 {{conventionsBlock}}
 
@@ -40,9 +39,9 @@ If that errors (timeout, DNS, connection refused), the app is unreachable. STOP
 
 # What to do
 
-1. **Plan the session.** From the QA context, the QA guide, and the focus, build a short test matrix. For each candidate UI surface, list the user-visible behaviors worth verifying. Skip surfaces unrelated to the focus.
+1. **Plan the session.** From the QA context, the QA scenarios & notes, and the focus, build a short test matrix. For each candidate UI surface, list the user-visible behaviors worth verifying. Skip surfaces unrelated to the focus.
 
-2. **Authenticate if required.** If a route under test needs a role and you have credentials (in the QA guide or via `--auth-profile`), log in once. If credentials for a needed role are missing, note it as a gap and browse only what you can.
+2. **Authenticate if required.** Follow the Auth instruction in the Target section above. If a route under test needs a role and you have credentials, log in once. If credentials for a needed role are missing, note it as a gap and browse only what you can.
 
 3. **Exercise each surface.** For every UI surface in your matrix, run through the relevant states. Don't pad — apply the checklist where it actually matters:
    - **Happy path.** The user-visible behavior the surface exists to support, end to end.

package/dist/executables/ui-review/profile.json

@@ -72,7 +72,7 @@
       { "script": "loadTaskState" },
       { "script": "loadConventions" },
       { "script": "discoverQaContext" },
-      { "script": "loadQaGuide" },
+      { "script": "loadQaContext" },
       { "script": "resolvePreviewUrl" },
       { "script": "composePrompt" }
     ],

package/dist/executables/ui-review/prompt.md

@@ -30,9 +30,11 @@ If `browser_navigate` errors out (timeout, DNS, connection refused, navigation a
 {{qaContext}}
 ```
 
-# QA guide (committed in the repo — authoritative over the auto-discovery above)
+# QA scenarios & notes (hand-written, authoritative over auto-discovery above)
 
-{{qaGuide}}
+{{qaProfile}}
+
+{{qaAuthBlock}}
 
 # Diff
 
@@ -48,7 +50,7 @@ If `browser_navigate` errors out (timeout, DNS, connection refused, navigation a
 
 1. **Identify UI-affecting changes.** Read the diff. Which pages / components / forms / styles did this PR change? Which user-visible behavior should be verified in the browser? If the diff has no UI surface (pure backend, pure config, pure tests), say so and produce a diff-only review — do not spin up Playwright for nothing.
 
-2. **Plan the browse session.** For each UI-affecting change, pick 1–3 routes from the QA context that exercise it. If the change requires an authenticated role, grab credentials from the QA guide above. If no credentials are available for a role the change depends on, note that as a gap and browse only public pages.
+2. **Plan the browse session.** For each UI-affecting change, pick 1–3 routes from the QA context that exercise it. If the change requires an authenticated role, follow the Auth instruction above. If no credentials are available for a role the change depends on, note that as a gap and browse only public pages.
 
 3. **Write a Playwright spec.** Create exactly one file at `.kody/ui-review/browse.spec.ts`. Use `process.env.UI_REVIEW_BASE_URL` as the base URL. For each route you plan to check, write a test that:
    - navigates there,

package/kody.config.schema.json

@@ -420,17 +420,6 @@
       },
       "additionalProperties": false
     },
-    "qa": {
-      "type": "object",
-      "description": "qa-engineer defaults. Used by the resolveQaUrl preflight when no explicit --url is passed and no $PREVIEW_URL env var is set.",
-      "properties": {
-        "fallbackUrl": {
-          "type": "string",
-          "description": "Fallback URL the qa-engineer should target. Typically the project's stable dev environment (e.g. 'https://dev.example.com'). No localhost defaults — CI has no localhost to fall back to."
-        }
-      },
-      "additionalProperties": false
-    },
     "devServer": {
       "type": "object",
       "description": "Dev server configuration for browser tool verification. Works with any provider (MCP or CLI-based).",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine",
-  "version": "0.4.122",
+  "version": "0.4.123",
   "description": "kody — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   "license": "MIT",
   "type": "module",