Skip to content

fix: pre-release cleanup — bugs, version sync, and error handling#412

Merged
jackwener merged 2 commits intomainfrom
fix/pre-release-cleanup
Mar 25, 2026
Merged

fix: pre-release cleanup — bugs, version sync, and error handling#412
jackwener merged 2 commits intomainfrom
fix/pre-release-cleanup

Conversation

@jackwener
Copy link
Copy Markdown
Owner

Summary

Pre-release quality sweep addressing bugs, documentation gaps, and code hygiene.

Bug Fixes

  • analysis.ts:167hasLimit was checking SEARCH_PARAMS instead of LIMIT_PARAMS, so classifyQueryParams().hasLimit always returned incorrect results
  • pipeline/executor.ts + validate.tsscroll step was declared in BROWSER_STEPS and KNOWN_STEP_NAMES but never registered in registry.ts. Using it in YAML would crash at runtime. Removed from declarations.
  • validate.tsdownload step was missing from KNOWN_STEP_NAMES, causing false-positive lint warnings on valid YAML pipelines

Docs

  • Sync version numbers across SKILL.md, extension/package.json, extension/manifest.json1.3.3
  • Add jd, web to README command tables (EN + zh-CN)
  • Update xueqiu with new fund-holdings, fund-snapshot commands

Code Quality

  • Replace all 22 catch (err: any) with typed error handling using existing getErrorMessage() utility across 13 files

Test plan

  • tsc --noEmit passes
  • vitest run src/ — 31 files, 328 tests all green
  • Zero remaining catch (err: any) in codebase

Bug fixes:
- Fix hasLimit using wrong Set (SEARCH_PARAMS → LIMIT_PARAMS) in
  analysis.ts classifyQueryParams
- Remove phantom scroll step from BROWSER_STEPS and KNOWN_STEP_NAMES
  (declared but never registered, causes runtime crash if used in YAML)
- Add missing download step to KNOWN_STEP_NAMES (was producing
  false-positive validation warnings)

Docs:
- Sync version numbers: SKILL.md, extension/package.json,
  extension/manifest.json → 1.3.3
- Add jd, web to README command tables (both EN and zh-CN)
- Update xueqiu commands with fund-holdings, fund-snapshot

Code quality:
- Replace all 22 catch (err: any) with typed error handling using
  existing getErrorMessage() utility across 13 files
- antigravity/serve.ts: use typed Error.cause instead of (err as any).cause
- external.ts: move instanceof guard into shouldRetryWithCmdShim,
  accept unknown instead of forcing NodeJS.ErrnoException cast at call site
@jackwener jackwener merged commit 594ad50 into main Mar 25, 2026
24 checks passed
@jackwener jackwener deleted the fix/pre-release-cleanup branch March 25, 2026 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant