syncing-daemon-release

Synchronizes SDK generated types, API docs, and runtime pins with a new wavelength daemon release.

4|4|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/lightninglabs/wavelength-sdk --skill syncing-daemon-release-lightninglabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: syncing-daemon-release
Source: https://github.com/lightninglabs/wavelength-sdk/tree/main/.claude/skills/syncing-daemon-release
Command: npx skills add https://github.com/lightninglabs/wavelength-sdk --skill syncing-daemon-release-lightninglabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the upstream wavelength daemon publishes a new release, this repository's generated facade types, API reference data, and runtime version pin drift out of sync, and updating them by hand misses the many coupled files that must move together. ## Core Features & Use Cases - Coordinated artifact sync: Regenerates generated.ts via pnpm gen:types, rebuilds wallet.json via pnpm gen:api-docs, and updates RUNTIME_MANIFEST_VERSION so all three match the same daemon commit. - Change-class mapping: Maps each upstream change type (facade types, WalletService RPCs, wavecli flags, wasm assets, gomobile bindings) to exactly which files and docs pages must be regenerated or hand-edited. - Verification ladder: Runs build, typecheck, unit tests, and Playwright smoke tests in a defined order, with guidance for diagnosing draft releases, digest mismatches, and stale preview servers. - Use Case: After wavelength tags v0.2.0, use this Skill to pin the new version, regenerate types and API docs from a throwaway worktree, restage wasm and mobile binding assets, and prepare the draft GitHub release that publishes all four npm packages. ## Quick Start Sync this repository to the newly published wavelength release v0.2.0, regenerating types, API docs, and runtime assets, then run the full verification ladder.

Frequently Asked Questions about syncing-daemon-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the SDK when wavelength publishes a new release?

Create a detached git worktree of the wavelength checkout at the release tag, set WAVELENGTH_DIR to it, then bump RUNTIME_MANIFEST_VERSION, run pnpm gen:types and pnpm gen:api-docs, restage runtime assets, and run the verification ladder in order.

How do I regenerate generated.ts and wallet.json from the daemon?

Run pnpm gen:types to regenerate packages/core/src/generated.ts and pnpm gen:api-docs to rebuild apps/docs/src/data/api/wallet.json. Both read the wavelength checkout at WAVELENGTH_DIR and must never be hand-edited.

Why does gen:types fail with an 'any only refers to a type' error?

This happens when the facade adds an exported scalar const assigned from another package, which tygo cannot inline. Fix it by extending the unresolved-const stripping logic in scripts/gen-types.mts, never by editing generated.ts directly.

Why do wasm:fetch and bindings:fetch return 404 for a valid tag?

The fetch scripts build a release URL from the pin, so they 404 for commit-SHA pins, draft releases, or published releases whose asset workflow failed. Check the release assets and the mobile-bindings.yml workflow run, or fall back to the :local build scripts.

Why does the docs Playwright test 404 on a brand-new page?

The docs test webServer reuses an existing server on port 4321, so it may attach to a stale preview from another worktree serving an old build. Pass a free PORT, such as PORT=4399, to force a fresh build and serve.

Should I document wavecli flags from --help output?

No. Document CLI flags from the daemon source in cmd/wavecli/waveclicommands/cmd_*.go, since build tags hide commands and help output omits exit codes and JSON shapes. Verify operational claims against waved/config.go and gateway_server.go.