Skip to content

Publish canonical leddy-mcp-server.rs repository #18

Description

@ORESoftware

Goal

Create the public short-name repository led-dynamo/leddy-mcp-server.rs after leddy-sync is published.

Required Zed graph

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

[dependencies]
"led-dynamo/leddy-clients" = "^0.1.0"
"led-dynamo/leddy-interfaces" = "^0.1.0"
"led-dynamo/leddy-lib" = "^0.1.0"
"led-dynamo/leddy-cli" = "^0.1.0"
"led-dynamo/leddy-sync" = "^0.1.0"
"shared-auth/shared-auth-clients" = "^0.1.0"

The initial server should expose a read-only Zed dependency graph and device/fleet metadata surfaces. Any write-capable device commands require explicit authentication, authorization, confirmation, audit logging, and rate limits in a later change.

Publication order

  1. merge the executable seed in led-dynamo/.github
  2. publish and validate leddy-sync
  3. publish leddy-mcp-server.rs
  4. validate the initial MCP and Zed CI
  5. add the delivery record to GitHub Project Bootstrap Leddy Zed package family and complete polyglot clients matrix #1 and Linear

Git-submodule interoperability

Canonical package repositories may remain committed gitlinks as exact source transport. Zed owns package identity, dependency intent, materialization, and immutable lock provenance. Adopt existing canonical gitlinks with zed overtake --git-submodules; never create a parallel long-name coordinate or second workspace path.

Tracking

Acceptance criteria

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions