Publish canonical leddy-sync Zed package

[ORESoftware]

Goal

Create the public short-name repository led-dynamo/leddy-sync before adding the sync coordinate to UI and backend manifests.

Package contract

The root .zpkg.toml must use:

[package]
org = "led-dynamo"
name = "leddy-sync"

[install]
dir = ".vendor/.zed"

[dependencies]
"led-dynamo/leddy-interfaces" = "^0.1.0"
"led-dynamo/leddy-lib" = "^0.1.0"

The package should own versioned state envelopes, conflict/version comparison, and deterministic reconciliation primitives. Transport remains in clients/API code.

Consumers after publication

• leddy-api-server.rs
• leddy-web-server.rs
• future native/Flutter UI repositories
• leddy-monorepo
• leddy-mcp-server.rs

Git-submodule interoperability

A composing repository may retain leddy-sync as an exact committed gitlink. Adopt it with zed overtake --git-submodules: Git remains source transport, while Zed owns package identity, dependency intent, materialization, and immutable lock provenance. Do not create a second workspace path or long-name alias.

Tracking

• GitHub Project: https://github.com/orgs/led-dynamo/projects/1
• Linear project: https://linear.app/denman/project/githubcomled-dynamo-bd51986e8494

Acceptance criteria

• executable repository seed is reviewed and merged in led-dynamo/.github
• public repository exists at led-dynamo/leddy-sync
• Rust formatting, Clippy, tests, and manifest checks pass
• API, web, and monorepo manifests add the canonical sync coordinate
• repository/delivery issue is represented in GitHub Project Bootstrap Leddy Zed package family and complete polyglot clients matrix #1
• Linear topology/status documentation records the repository and initial commit

[ORESoftware]

Seed delivery completed — 2026-08-08

The executable leddy-sync repository seed is merged in .github#19 at 466e7d06069274168ae5d263e7c3a011a59ec1b4 after both organization-baseline and public-privacy workflows passed.

• seed: repository-seeds/leddy-sync/
• Linear issue: DEN-2884
• dependencies: leddy-interfaces and leddy-lib
• materialization: .vendor/.zed
• implementation: deterministic logical versions, versioned state, reconciliation decisions, four unit tests, Rust CI, and an idempotent credential-free publisher

Related dependency work already merged:

• API server PR docs: link GitHub Project and Linear planning #2 at 0e19032e47e50493a80dea948bc07f1394ea6665
• web server PR GitHub Project and Linear workspace links #3 at bfeb6967549c8b955ca066cd28257569123513d5
• E2E quartet PR docs: link GitHub Project and Linear planning #2 at c66c047137a3ec63d6690df967f132080522bc0b

Remaining: publish led-dynamo/leddy-sync, validate its initial CI and real Zed resolution, then add sync to API/web/future UI manifests in focused PRs and record the delivery in GitHub Project #1 and Linear.