Affected component
ego-browser runtime or CLI
What happened?
On the current official ego lite 0.4.6.14 app, help() is still non-functional even though #84 was closed as fixed.
Every helper name returns Unknown helper: <name>, and help() with no arguments returns an empty string. The helpers themselves work. Only the self-discovery catalog is empty.
This matches the original #84 failure mode: the shipped browser loads the SDK from a compiled / eval resource, so a docs map that is not actually present at runtime stays empty. #85 embedded docs at build time on dev, but that catalog is not present in the 0.4.6.14 app runtime. typeof click === "function" while help("click") still says unknown.
Related: the app-bundled skill is still 1.2.3 (2026-06-25), which is the same lag described in #273.
Steps to reproduce
ego-browser --version
# ego-browser 0.4.6.14
# chromium 150.0.7871.101
# node v24.18.0
ego-browser nodejs <<'EOF'
cliLog(help())
cliLog(help('click'))
cliLog(help('snapshotText'))
cliLog(typeof click)
EOF
Expected behavior
help() lists available helpers. help('click') prints the click signature and usage, as documented in SKILL.md.
Actual behavior
Unknown helper: click
Unknown helper: snapshotText
function
help() with no arguments prints an empty string.
Version
ego lite 0.4.6.14; bundled ego-browser skill 1.2.3 (2026-06-25); Chromium 150.0.7871.101; Node v24.18.0
Environment
macOS 26.5.0, Apple Silicon (arm64), Claude Code
Additional context
- Official channels all report 0.4.6.14 as latest:
ego-browser upgrade → "already up to date"; About page after recheck → "ego 已是最新版本 / 版本 0.4.6.14"; Omaha updatecheck.status=noupdate; changelog latest heading is 0.4.6.14; official DMG x-amz-meta-omaha-version: 0.4.6.14.
- A PR will add a runtime fallback so
help() can recover signatures from live functions when the embedded catalog is empty or missing a helper. That is a defense in depth for the next app ship; the app still needs to ship the built catalog from dev.
Before submitting
Affected component
ego-browser runtime or CLI
What happened?
On the current official ego lite 0.4.6.14 app,
help()is still non-functional even though #84 was closed as fixed.Every helper name returns
Unknown helper: <name>, andhelp()with no arguments returns an empty string. The helpers themselves work. Only the self-discovery catalog is empty.This matches the original #84 failure mode: the shipped browser loads the SDK from a compiled / eval resource, so a docs map that is not actually present at runtime stays empty. #85 embedded docs at build time on
dev, but that catalog is not present in the 0.4.6.14 app runtime.typeof click === "function"whilehelp("click")still says unknown.Related: the app-bundled skill is still
1.2.3(2026-06-25), which is the same lag described in #273.Steps to reproduce
Expected behavior
help()lists available helpers.help('click')prints the click signature and usage, as documented inSKILL.md.Actual behavior
help()with no arguments prints an empty string.Version
ego lite 0.4.6.14; bundled ego-browser skill 1.2.3 (2026-06-25); Chromium 150.0.7871.101; Node v24.18.0
Environment
macOS 26.5.0, Apple Silicon (arm64), Claude Code
Additional context
ego-browser upgrade→ "already up to date"; About page after recheck → "ego 已是最新版本 / 版本 0.4.6.14"; Omahaupdatecheck.status=noupdate; changelog latest heading is 0.4.6.14; official DMGx-amz-meta-omaha-version: 0.4.6.14.help()can recover signatures from live functions when the embedded catalog is empty or missing a helper. That is a defense in depth for the next app ship; the app still needs to ship the built catalog fromdev.Before submitting