fix: flatten SignedOrder serialization to match Rust serde (#37)

* fix: flatten owner and signature in SerializedSignedOrder to match Rust serde

Rust's SignedOrder uses #[serde(flatten)] on the Permit2Batch field,
which hoists `owner` and `signature` to be siblings of `permit` in JSON.
The TypeScript type and serialization functions were nesting them inside
`permit`, causing a shape mismatch with the Rust implementation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* docs: add JSDoc to all exports, require JSDoc in CLAUDE.md

Adds JSDoc comments to all exported functions, types, interfaces, and
constants across the codebase. Updates CLAUDE.md code style to require
JSDoc for all exports. Bumps version to 0.4.5.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: James <james@prestwi.ch>

chore: v0.4.4

chore: v0.4.3

chore: v0.4.2

chore: v0.4.1

chore: release v0.4.0 (#25)

* chore: bump version to 0.4.0

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add SKILL.md for SDK documentation

- Add comprehensive skill file for @signet-sh/sdk
- Document OrderEvent, FilledEvent, SweepEvent types (v0.4.0+)
- Include core capabilities, exports, chain configs, common patterns

Related to PR #21

* style: format SKILL.md

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

fix(ci): add --access public to npm publish for scoped packages (#16)

The v0.2.0 release workflow failed because scoped packages with npm
provenance require --access public to be set explicitly. The GitHub
release was created but npm publish failed.

This PR:
- Fixes the release workflow to include --access public
- Bumps to v0.3.0 (v0.2.0 tag exists but was never published to npm)
- Removes thin viem wrappers (passage, weth, witness helpers) per SDK scope
- Documents direct viem usage patterns in README

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

fix(ci): add --access public to npm publish for scoped packages (#16)

The v0.2.0 release workflow failed because scoped packages with npm
provenance require --access public to be set explicitly. The GitHub
release was created but npm publish failed.

This PR:
- Fixes the release workflow to include --access public
- Bumps to v0.3.0 (v0.2.0 tag exists but was never published to npm)
- Removes thin viem wrappers (passage, weth, witness helpers) per SDK scope
- Documents direct viem usage patterns in README

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

chore: release v0.2.0 (#10)

- Bump version to 0.2.0
- Add initial changelog with 0.1.0 and 0.2.0 releases
- Update CLAUDE.md with changelog requirements and correct release process

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

The wonder of their singing, its elusive blend of man and camel