Skip to content

About

Generated sdk-consumer test harness for opto-sync-test.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

opto-sync-test/typescript-client-e2e

Generated sdk-consumer harness for opto-sync.

Contract

Profile: sdk-consumer
Source organization: opto-sync

  • TypeScript adapter
  • IndexedDB
  • service worker

Immutable source pins

Source Commit Branch observed
opto-sync/opto-sync-clients fdf4fad9e2e841f66ecee19fca3b408d5fa7fa4c main

Dependency lanes

Mode Source Manager Path/subdir
git-submodule opto-sync/opto-sync-clients - vendor/opto-sync-clients
zed opto-sync/opto-sync-clients - -
native-package opto-sync/opto-sync-clients npm clients/ts

Running

The pull-request workflow validates the generated contract without cross-organization credentials. Product-specific files outside the generated file set are preserved and must add executable assertions without weakening the base contract. Full integration is intentionally release-gated until required source repositories and organization read credentials are present. The generic protected lane reports source-access status only; source certification requires a product-specific executable overlay. A skipped integration job is not source certification. Run the profile-specific checks recorded in test-plan.json after materializing the submodule, Zed, or native-package lane.

About

Generated sdk-consumer test harness for opto-sync-test.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages