Skip to content

Feat/path fix - #50

Open
dzdidi wants to merge 16 commits into
masterfrom
feat/path-fix
Open

dzdidi wants to merge 16 commits into
masterfrom
feat/path-fix

Conversation

@dzdidi

@dzdidi dzdidi commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

MERGE ONLY AFTER SUCCESSFULL TEST ON STAGING!

Summary

Contract and risk impact

  • Public API or SDK contract
  • Persisted data or migration
  • Authentication, authorization, identity, or secret handling
  • Payment or entitlement behavior
  • Runtime, deployment, or observability
  • No contract/risk impact

Verification

Documentation

Checklist

  • The change is focused and self-reviewed.
  • Regression tests were added where practical.
  • No credentials, identities, private content, payment material, or generated local state are included.
  • Formatting and relevant tests/lints pass.

- add Rust probe for public Paykit v0 namespace data
- expose static JS/WASM discovery methods with custom relay support
- distinguish invalid user input from operational lookup failures
- derive Paykit namespace from pinned paykit-lib at build time
- keep Paykit crypto dependencies outside the WASM runtime graph
- pin compatible pubky-noise rc7 build dependency
- raise workspace MSRV and build toolchain to Rust 1.91.1
- document data-presence semantics and explicit non-claims
- cover Rust, generated API, WASM, and failure behavior

Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Base automatically changed from feat/staging-test to master September 9, 2026 12:17
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
- forward Paykit context through reset helper
- keep Compose context exported throughout walkthrough
- update documentation smoke contracts
- run focused JS behavior tests in CI
- document app.locks namespace cutover

Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
- pin Paykit Server to merged immutable revision
- restore zero-config Compose startup
- retain optional local worktree override
- validate both public and local build contexts
- update demo documentation and smoke contracts

Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
@dzdidi
dzdidi marked this pull request as ready for review September 10, 2026 18:07
Signed-off-by: dzdidi <dzdidi@users.noreply.github.com>
@dzdidi
dzdidi requested a review from ben-kaufman September 11, 2026 12:27
@dzdidi

dzdidi commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator Author

@Taewa may you please have a look at this one and see if it there is actual risk of merging it before testing things e2e on staging?

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.

2 participants