@assertrx/dino 1.0.7 → 1.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assertrx/dino",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "A friendly purple dinosaur pi package with a custom TUI header, theme, and Playwright skills.",
   "keywords": [
     "pi-package"
@@ -25,7 +25,7 @@
     "postinstall": "npx playwright install chromium"
   },
   "dependencies": {
-    "@earendil-works/pi-coding-agent": "*",
+    "@earendil-works/pi-coding-agent": "0.84.4",
     "@fastify/cors": "^11.3.0",
     "@mablhq/mabl-cli": "^2.127.20",
     "@modelcontextprotocol/sdk": "^1.30.0",

package/prompts/bdd-from-requirements.md

@@ -0,0 +1,48 @@
+---
+description: Convert a Word or Excel requirements document into Gherkin BDD feature files using the bdd-gherkin skill
+argument-hint: "<requirements-file> [output-dir]"
+---
+
+Convert the requirements document at **$1** into Gherkin BDD feature files using the `bdd-gherkin` skill, and save them to `${2:-tests/features/}` — the same location and format used by "BDD From URL".
+
+## Workflow
+
+1. **Verify the document exists**.
+   - Check that $1 exists and is readable. If not, stop and report the exact problem (missing file, unsupported extension, unreadable content).
+
+2. **Load the BDD skill**.
+   - Read `skills/bdd-gherkin/SKILL.md` first and follow its rules for the rest of this task.
+
+3. **Extract the requirements text**.
+   - $1 may be a Word document (.docx), an Excel workbook (.xlsx/.xlsm), or a plain-text file (.txt/.md/.csv). Extract its full content to work from:
+     - **Plain text (.txt/.md/.csv)** — read the file directly.
+     - **Word (.docx)** — a .docx is a ZIP archive. Try, in order:
+       1. `pandoc "$1" -t gfm` (keeps tables as markdown) if pandoc is installed
+       2. Python with `python-docx` if available
+       3. Raw fallback: extract `word/document.xml` from the archive (`unzip -p "$1" word/document.xml`, or PowerShell's `System.IO.Compression.ZipFile` on Windows) and strip the XML tags. Convert `<w:p>` elements to line breaks and `<w:tbl>` table rows to pipe-delimited rows so tabular requirements survive.
+     - **Excel (.xlsx/.xlsm)** — also a ZIP archive. Try, in order:
+       1. Python with `openpyxl` or `pandas` if available
+       2. Raw fallback: extract `xl/workbook.xml`, `xl/sharedStrings.xml`, and `xl/worksheets/sheet*.xml` from the archive and reconstruct the rows — shared strings give the text values, the sheet XML gives the cell positions. Emit each sheet as a separate section, headed by the sheet name.
+   - If the extracted text is too long to keep in the conversation, write it to a temporary file **outside** the workspace (e.g. in the OS temp dir) and delete it when done. Never modify or move the original document.
+   - If extraction yields garbled or clearly incomplete content, say so and stop instead of inventing requirements.
+
+4. **Analyze the requirements**.
+   - Identify the business capability or capabilities, the primary actor(s), the business value, business rules, constraints, and any acceptance criteria.
+   - Requirements documents follow recognizable structures — user stories ("As a… I want… So that…"), Jira-style fields (Summary / Observed Behavior / Expected Behavior / Conditions / Replication Steps / Acceptance Criteria), requirement tables with IDs (REQ-001, AC-02, …), or spreadsheets with one requirement per row. Map these to scenarios using the skill's Jira-ticket rules where applicable.
+   - For spreadsheets with multiple sheets, treat each sheet as a section of the requirements.
+
+5. **Generate the Gherkin scenarios**.
+   - Ground every scenario in what the document actually states — do **not** invent requirements that are not in the document.
+   - Cover, as far as the document supports them: happy paths, validation / invalid input, business-rule and state-based cases, boundary / edge cases, and error cases.
+   - Where the document is ambiguous, choose the most reasonable interpretation, proceed, and record the assumption in the final summary. This action usually runs unattended from Dino Desktop, so do not block on clarifying questions.
+
+6. **Save the feature files**.
+   - Write each capability to `${2:-tests/features/}/<capability-name>.feature` using a clear kebab-case file name (e.g. `loan-approval.feature`, `customer-onboarding.feature`).
+   - If the document covers multiple distinct capabilities, split it into multiple feature files in the output directory.
+   - When the document numbers its requirements (REQ-014, AC-2, …), add a brief `# REQ-014` comment above each scenario it produced, so coverage stays traceable back to the document.
+
+## Output
+
+- The saved `.feature` file path(s).
+- A coverage summary: how many requirements / acceptance criteria were found, how many scenarios were generated per category (happy path, validation, edge cases, errors), and any requirement IDs that could not be covered — with the reason.
+- Any assumptions made about ambiguous requirements.

package/scripts/api-server.mjs

@@ -61,6 +61,14 @@ const PROMPT_REGISTRY = {
     ],
     description: "Generate Gherkin BDD scenarios for a page by inspecting it with playwright-cli",
   },
+  "bdd-from-requirements": {
+    file: "bdd-from-requirements.md",
+    params: [
+      { name: "requirementsFile", required: true, description: "Path to the requirements document (.docx, .xlsx, .txt, .md, .csv)" },
+      { name: "outputDir", required: false, description: "Output directory (default: tests/features/)" },
+    ],
+    description: "Convert a Word or Excel requirements document into Gherkin BDD feature files",
+  },
   "generate-spec-from-feature": {
     file: "generate-spec-from-feature.md",
     params: [

package/scripts/setup-dino-api.bat

@@ -31,7 +31,7 @@ if !ERRORLEVEL! EQU 0 (
     for /f "tokens=*" %%v in ('pi --version 2^>^&1') do echo           Found pi %%v
 ) else (
     echo           Installing pi...
-    call npm install -g @earendil-works/pi-coding-agent --silent --no-fund --no-audit
+    call npm install -g @earendil-works/pi-coding-agent@0.84.4 --silent --no-fund --no-audit
     if !ERRORLEVEL! NEQ 0 (
         echo ERROR: Failed to install pi.
         pause
@@ -56,6 +56,43 @@ if not exist "%DINO_DIR%" (
     echo           Dino already installed at %DINO_DIR%
 )
 
+:: ── 3b. Pin pi-coding-agent to last known-good version ───────────────
+:: pi-coding-agent@0.85.0 imports @earendil-works/pi-server at runtime
+:: without declaring it as a dependency (upstream packaging bug), which
+:: breaks the API server with ERR_MODULE_NOT_FOUND. 0.84.4 is the last
+:: version that works out of the box, so force it in pi's package dir
+:: regardless of what dino's "*" dependency resolved to.
+set "PI_NPM_DIR=%USERPROFILE%\.pi\agent\npm"
+set "PINNED_PI=0.84.4"
+node -e "const fs=require('fs');let v='';try{v=JSON.parse(fs.readFileSync(process.env.PI_NPM_DIR+'/node_modules/@earendil-works/pi-coding-agent/package.json','utf8')).version}catch(e){}process.exit(v===process.env.PINNED_PI?0:1)"
+if errorlevel 1 (
+    echo           Pinning @earendil-works/pi-coding-agent to %PINNED_PI% ...
+    pushd "%PI_NPM_DIR%"
+    call npm install "@earendil-works/pi-coding-agent@%PINNED_PI%" --save-exact --no-fund --no-audit --loglevel=error
+    if errorlevel 1 (
+        popd
+        echo ERROR: Failed to install @earendil-works/pi-coding-agent@%PINNED_PI%.
+        pause
+        exit /b 1
+    )
+    popd
+    echo           Pinned to %PINNED_PI%.
+) else (
+    echo           pi-coding-agent %PINNED_PI% ^(known-good^) installed.
+)
+
+:: Verify the package imports cleanly before starting the server.
+pushd "%PI_NPM_DIR%"
+node --input-type=module -e "await import('@earendil-works/pi-coding-agent')"
+if errorlevel 1 (
+    popd
+    echo ERROR: pi-coding-agent failed to import - see message above.
+    pause
+    exit /b 1
+)
+popd
+echo           pi-coding-agent import check OK.
+
 :: ── 4. Start server ───────────────────────────────────────────────────
 echo [4/4] Starting Dino API server...
 echo.

package/scripts/setup-dino-api.sh

@@ -21,7 +21,7 @@ if command -v pi &>/dev/null; then
     echo "       Found pi $(pi --version 2>&1 || echo '(unknown version)')"
 else
     echo "       Installing pi..."
-    npm install -g @earendil-works/pi-coding-agent
+    npm install -g @earendil-works/pi-coding-agent@0.84.4
     echo "       pi installed successfully."
 fi
 
@@ -36,6 +36,28 @@ else
     echo "       Dino already installed at ${DINO_DIR}"
 fi
 
+# pi-coding-agent@0.85.0 imports @earendil-works/pi-server at runtime
+# without declaring it as a dependency (upstream packaging bug), which
+# breaks the API server with ERR_MODULE_NOT_FOUND. 0.84.4 is the last
+# version that works out of the box, so force it in pi's package dir
+# regardless of what dino's "*" dependency resolved to.
+PI_NPM_DIR="${HOME}/.pi/agent/npm"
+PINNED_PI="0.84.4"
+export PI_NPM_DIR PINNED_PI
+if ! node -e "const fs=require('fs');let v='';try{v=JSON.parse(fs.readFileSync(process.env.PI_NPM_DIR+'/node_modules/@earendil-works/pi-coding-agent/package.json','utf8')).version}catch(e){}process.exit(v===process.env.PINNED_PI?0:1)"; then
+    echo "       Pinning @earendil-works/pi-coding-agent to ${PINNED_PI}..."
+    (cd "${PI_NPM_DIR}" && npm install "@earendil-works/pi-coding-agent@${PINNED_PI}" --save-exact --no-fund --no-audit --loglevel=error)
+    echo "       Pinned to ${PINNED_PI}."
+else
+    echo "       pi-coding-agent ${PINNED_PI} (known-good) installed."
+fi
+
+if ! (cd "${PI_NPM_DIR}" && node --input-type=module -e "await import('@earendil-works/pi-coding-agent')"); then
+    echo "ERROR: pi-coding-agent failed to import."
+    exit 1
+fi
+echo "       pi-coding-agent import check OK."
+
 # ── 4. Start server ───────────────────────────────────────────────────
 echo "[4/4] Starting Dino API server..."
 echo ""

package/scripts/start-dino-server.bat

@@ -10,6 +10,18 @@ if not exist "%DINO_DIR%" (
     exit /b 1
 )
 
+:: Self-heal: force known-good pi-coding-agent (0.85.0 has a missing
+:: dependency that breaks the API server - see setup-dino-api.bat).
+set "PI_NPM_DIR=%USERPROFILE%\.pi\agent\npm"
+set "PINNED_PI=0.84.4"
+node -e "const fs=require('fs');let v='';try{v=JSON.parse(fs.readFileSync(process.env.PI_NPM_DIR+'/node_modules/@earendil-works/pi-coding-agent/package.json','utf8')).version}catch(e){}process.exit(v===process.env.PINNED_PI?0:1)"
+if errorlevel 1 (
+    echo Installing @earendil-works/pi-coding-agent@%PINNED_PI% ...
+    pushd "%PI_NPM_DIR%"
+    call npm install "@earendil-works/pi-coding-agent@%PINNED_PI%" --save-exact --no-fund --no-audit --loglevel=error
+    popd
+)
+
 echo Starting Dino API server on port %PORT% (default: 4003)...
 
 :: The published npm package may not include api-server.mjs, so fall back

package/scripts/start-dino-server.sh

@@ -12,5 +12,15 @@ if [ ! -d "${DINO_DIR}" ]; then
     exit 1
 fi
 
+# Self-heal: force known-good pi-coding-agent (0.85.0 has a missing
+# dependency that breaks the API server - see setup-dino-api.sh).
+PI_NPM_DIR="${HOME}/.pi/agent/npm"
+PINNED_PI="0.84.4"
+export PI_NPM_DIR PINNED_PI
+if ! node -e "const fs=require('fs');let v='';try{v=JSON.parse(fs.readFileSync(process.env.PI_NPM_DIR+'/node_modules/@earendil-works/pi-coding-agent/package.json','utf8')).version}catch(e){}process.exit(v===process.env.PINNED_PI?0:1)"; then
+    echo "Installing @earendil-works/pi-coding-agent@${PINNED_PI}..."
+    (cd "${PI_NPM_DIR}" && npm install "@earendil-works/pi-coding-agent@${PINNED_PI}" --save-exact --no-fund --no-audit --loglevel=error)
+fi
+
 echo "Starting Dino API server on port ${PORT:-4003}..."
 exec node "${DINO_DIR}/scripts/api-server.mjs"