feat(registry): add production source transports - #164
Merged
Conversation
This was referenced Jul 20, 2026
Dencyuman
force-pushed
the
feat/registry-source-transports-127
branch
from
July 20, 2026 19:15
218db40 to
5bdc5ed
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
14 tasks
Dencyuman
force-pushed
the
feat/registry-source-transports-127
branch
from
July 20, 2026 19:52
65b5b20 to
7d0b67b
Compare
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Dencyuman
added a commit
that referenced
this pull request
Jul 21, 2026
) ## Summary Compose the packaged Desktop with the production Ladybug Query, Search, Analysis, search-index, and local-embedding owners. Add release-conformance foundations that execute the installed Desktop executable on macOS, Linux, and Windows, enforce documented performance and isolated-worker memory budgets, and sign the exact scenario result into update metadata. This PR is the production-owner and release-attestation layer on top of #161. It does not claim final Desktop closure. Registry, Review, real external-provider workflows, and the packaged Wails/WebView/MCP-descendant process-tree scenario remain required in #164. ## Linked Issues - Related to #127 ## Contributor Agreement - [x] I have read and agree to the LayerDraw Contributor License Agreement 1.0 and confirm that I have the rights and any employer authorization required to submit this Contribution. See the [Contributor License Agreement](https://github.com/dencyuinc/layerdraw/blob/main/docs/legal/contributor-license-agreement.md) and [Contributor Privacy Notice](https://github.com/dencyuinc/layerdraw/blob/main/docs/legal/contributor-privacy-notice.md). ## Scope - [ ] Documentation only - [ ] LDL / schema / protocol - [x] Engine / Runtime / Query / View - [x] SDK / MCP / client integration - [x] Server / storage / realtime / access - [ ] Registry / packs / templates - [x] Release / governance / legal ## Checks - [x] I did not add secrets, customer data, private deployment config, or local agent config. - [x] I checked the package boundary and licensing docs for affected paths. - [x] I updated generated artifacts or fixtures if a schema changed; no schema changed in this PR. - [x] I documented release and installer impact. - [x] I confirmed there is no state or data migration. - [x] I identified the release-note requirement. ## Contract Impact - Desktop bundles production LadybugDB v0.17.0 native libraries plus FTS, Vector, and Algo extensions. - Installed artifacts execute nine canonical workflow scenarios in isolated worker processes for five iterations and fail on p95 time or isolated-worker peak-RSS budget violations. - The isolated-worker contract does not claim Wails/WebView or MCP descendant-process memory; #164 must add that final packaged UI process-tree scenario. - Signed attestation binds installer digest, conformance declaration, exact installed scenario result, source revision, and platform. - No LDL, schema, protocol, or container contract changes. - Registry, Review, real external-provider, and packaged UI final workflow proof is explicitly deferred to #164. ## Validation - `go test ./apps/desktop ./internal/desktopwails ./tools/desktopattestation ./tools/desktopconformance ./tools/desktoprelease ./tools/licensecheck` - `go test -race ./internal/desktopwails ./tools/desktopattestation ./tools/desktopconformance` - `go run ./tools/desktopconformance -root . verify` - `bash -n tools/build-desktop-installer.sh tools/build-desktop-update-metadata.sh tools/smoke-desktop-installer.sh` - Local installed-binary subprocess run: isolated worker peaks 459–466 MiB under the unchanged 512 MiB budget. - `git diff --check` - `go test ./...` passes except the local environment guard requiring Node v24.18.0 (host has v23.6.0); CI uses the pinned version.
Dencyuman
force-pushed
the
feat/registry-source-transports-127
branch
from
July 21, 2026 00:16
159eb0d to
aaf970e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Complete the docs-defined Desktop delivery channel and its shared production foundations. This closes packaged application composition, native Registry/Library and MCP routing, installed lifecycle and recovery conformance, three-platform installer verification, signed release evidence, disabled-feature closure, accessibility/UI matrix evidence, and whole-process-tree memory budgets.
Linked Issues
Contributor Agreement
See the Contributor License Agreement and Contributor Privacy Notice.
Scope
Checks
Integrated implementation
Validation
Local targeted validation is green for Desktop Wails, attestation, conformance closure, Windows cross-compilation, formatting, and generated diff integrity. GitHub Actions is the final authority for the full build/race/security/license, WASM, CodeQL, native Ladybug, packaged Desktop, and three-OS installer matrices.