Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix Published npm package 2026.4.9 is missing qa/scenarios files [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#64348•Fetched 2026-04-11 06:15:17
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
oracle12cr2oracle12cr2
Participants
oracle12cr2oracle12cr2
Timeline (top)
cross-referenced ×1referenced ×1

[email protected] appears to publish without the required qa/scenarios/* files. Because of that, commands that register sub-CLIs and/or generate completion can fail immediately after install/update.

Error Message

Completion cache update failed [OpenClaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md at readQaScenarioPack (.../openclaw/dist/suite-.js) at readQaScenarioById (.../openclaw/dist/suite-.js) at readQaScenarioExecutionConfig (.../openclaw/dist/suite-.js) at readRequiredDiscoveryRefs (.../openclaw/dist/suite-.js) ...

Root Cause

[email protected] appears to publish without the required qa/scenarios/* files. Because of that, commands that register sub-CLIs and/or generate completion can fail immediately after install/update.

Fix Action

Temporary workaround

Manually recreate the missing files under the installed package directory and then rerun:

openclaw completion --write-state -y

PR fix notes

PR #64350: fix(package): include qa/scenarios in npm published files

Description (problem / solution / changelog)

Summary

Fixes #64348 — [email protected] is missing qa/scenarios/* files in the npm tarball, causing CLI crashes:

Error: qa scenario pack not found: qa/scenarios/index.md

Fix

Add qa/ to package.json files array so it's included in the npm package.

Verification

npm pack --dry-run now includes qa/scenarios/*.md files.

Changed files

  • package.json (modified, +1/-0)

Code Example

Completion cache update failed [OpenClaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md
    at readQaScenarioPack (.../openclaw/dist/suite-*.js)
    at readQaScenarioById (.../openclaw/dist/suite-*.js)
    at readQaScenarioExecutionConfig (.../openclaw/dist/suite-*.js)
    at readRequiredDiscoveryRefs (.../openclaw/dist/suite-*.js)
    ...

---

Error: unknown qa scenario: source-docs-discovery-report

---

npm pack openclaw@2026.4.9

tar -tzf openclaw-2026.4.9.tgz | grep '^package/qa/'
# no output

---

openclaw completion --write-state -y
RAW_BUFFERClick to expand / collapse

Summary

[email protected] appears to publish without the required qa/scenarios/* files. Because of that, commands that register sub-CLIs and/or generate completion can fail immediately after install/update.

Observed error

On macOS after update:

Completion cache update failed [OpenClaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md
    at readQaScenarioPack (.../openclaw/dist/suite-*.js)
    at readQaScenarioById (.../openclaw/dist/suite-*.js)
    at readQaScenarioExecutionConfig (.../openclaw/dist/suite-*.js)
    at readRequiredDiscoveryRefs (.../openclaw/dist/suite-*.js)
    ...

After manually creating only qa/scenarios/index.md, the next failure becomes:

Error: unknown qa scenario: source-docs-discovery-report

That indicates at least these files are expected at runtime:

  • qa/scenarios/index.md
  • qa/scenarios/source-docs-discovery-report.md

Reproduction

  1. Install/update [email protected]
  2. Inspect the published package contents
  3. Run openclaw completion --write-state -y

What I verified

Installed package content

On both Linux and macOS installs, the package directory had no qa/ folder at all.

npm tarball content

I also checked the published tarball directly:

npm pack [email protected]

tar -tzf openclaw-2026.4.9.tgz | grep '^package/qa/'
# no output

So this looks like a packaging/publish issue, not local corruption.

Impact

This breaks CLI startup paths that touch QA discovery during command registration/completion generation, so users can hit failures right after updating.

Temporary workaround

Manually recreate the missing files under the installed package directory and then rerun:

openclaw completion --write-state -y

Expected fix

Include the required qa/scenarios files in the published npm package, or guard these QA discovery reads so normal CLI flows do not hard-fail when QA assets are absent.

extent analysis

TL;DR

The most likely fix is to include the required qa/scenarios files in the published npm package to prevent CLI startup failures.

Guidance

  • Verify that the qa/scenarios files are present in the package directory after installation by checking the package contents.
  • Check the npm pack output to ensure the qa/scenarios files are included in the published tarball.
  • Consider adding error handling or guards to prevent hard failures when QA assets are absent, as a temporary workaround until the packaging issue is resolved.
  • Manually recreating the missing files under the installed package directory and rerunning openclaw completion --write-state -y can serve as a temporary workaround.

Example

No code snippet is provided as it is not clearly supported by the issue, but the temporary workaround command is:

openclaw completion --write-state -y

after manually recreating the missing qa/scenarios files.

Notes

The issue seems to be related to a packaging or publishing problem, rather than a code issue, and the fix should involve including the required files in the published package or adding error handling to prevent failures.

Recommendation

Apply the workaround by manually recreating the missing files and rerunning the completion command, as the root cause is likely a packaging issue that needs to be addressed in the publishing process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Temporary workaround

Manually recreate the missing files under the installed package directory and then rerun:

openclaw completion --write-state -y
#chain error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix Published npm package 2026.4.9 is missing qa/scenarios files [1 pull requests, 1 participants]