onde-cli 0.4.3__tar.gz → 0.5.0__tar.gz

{onde_cli-0.4.3 → onde_cli-0.5.0}/.agents/AGENTS.md

@@ -64,7 +64,7 @@ The `onde` crate provides the inference engine (`onde::mistralrs`, a vendored mi
 - **Commits:** include `Co-Authored-By: siGit Code <297239231+sigitc@users.noreply.github.com>` trailer when committing with the agent.
 - **`[patch.crates-io]` and `path =` deps:** commented out in `Cargo.toml` for local dev against `onde`/`smbcloud-*`/`candle`. Never commit with these uncommented.
 - **Distribution:** before touching any wrapper package (npm, PyPI, NuGet, pub.dev, Homebrew), read `.agents/skills/distribution/SKILL.md`. Keep all channel versions aligned with the Rust crate version in `Cargo.toml`.
-- **MCP Registry:** the listing's ownership markers ship inside the published npm and NuGet artifacts, so a version published without them can never be listed. See `docs/mcp-registry.md` before touching `server.json` or either marker.
-- **Wrapper packages** are in `npm/`, `pypi/`, `nuget/`, `pub/`. The npm base manifest is rewritten at release time by `npm/scripts/render-main-package.cjs`; do not hand-edit committed package.json versions as the source of truth for releases.
+- **MCP Registry:** the listing's ownership markers ship inside the published npm and NuGet artifacts, so a version published without them can never be listed. See `docs/mcp-registry.md` before touching `packaging/mcp/server.json` or either marker.
+- **Wrapper packages** are in `packaging/npm/`, `packaging/pypi/`, `packaging/nuget/`, `packaging/pub/`. The npm base manifest is rewritten at release time by `packaging/npm/scripts/render-main-package.cjs`; do not hand-edit committed package.json versions as the source of truth for releases.
 - **Clippy** runs with `-D warnings` in CI; all lints must pass.
 - **Rust edition:** 2024; toolchain: stable.

{onde_cli-0.4.3 → onde_cli-0.5.0}/.agents/skills/distribution/SKILL.md

@@ -56,9 +56,9 @@ Good fit for users who already live in npm tooling.
 
 Important release detail:
 
-- the committed `npm/onde-cli/package.json` is a working file, not the publish-time source of truth
-- the release workflow rewrites the base package manifest with `npm/scripts/render-main-package.cjs`
-- platform package manifests are generated on the fly with `npm/scripts/render-platform-package.cjs`
+- the committed `packaging/npm/onde-cli/package.json` is a working file, not the publish-time source of truth
+- the release workflow rewrites the base package manifest with `packaging/npm/scripts/render-main-package.cjs`
+- platform package manifests are generated on the fly with `packaging/npm/scripts/render-platform-package.cjs`
 - the actual npm version comes from the release tag via `RELEASE_VERSION`, not from manually editing the committed npm manifest before publish
 
 ### PyPI
@@ -177,7 +177,7 @@ That makes the safest design a thin Dart launcher that downloads the right nativ
 
 Practical consequences:
 
-- `pub/onde_cli/native/` should stay out of the published package
+- `packaging/pub/onde_cli/native/` should stay out of the published package
 - do not set `publish_to: https://pub.dev` in `pubspec.yaml`; omit `publish_to` for normal pub.dev publishing
 - use package-level ignore rules so local native staging does not leak into publish input
 - keep release asset names aligned with the GitHub Release workflow, because the launcher depends on them
@@ -186,9 +186,9 @@ Practical consequences:
 
 Run these during verification:
 
-- `dart pub get --directory pub/onde_cli`
-- `dart analyze pub/onde_cli`
-- `dart pub publish --dry-run --directory pub/onde_cli`
+- `dart pub get --directory packaging/pub/onde_cli`
+- `dart analyze packaging/pub/onde_cli`
+- `dart pub publish --dry-run --directory packaging/pub/onde_cli`
 
 ## NuGet-specific notes
 
@@ -210,10 +210,10 @@ Every user-facing channel should document the same product with channel-specific
 Main files:
 
 - `README.md`
-- `npm/onde-cli/README.md`
-- `pypi/README.md`
-- `nuget/onde-cli/README.md`
-- `pub/onde_cli/README.md`
+- `packaging/npm/onde-cli/README.md`
+- `packaging/pypi/README.md`
+- `packaging/nuget/onde-cli/README.md`
+- `packaging/pub/onde_cli/README.md`
 
 Keep these aligned on:
 

{onde_cli-0.4.3/.claude → onde_cli-0.5.0/.agents}/skills/release/SKILL.md

@@ -24,18 +24,19 @@ and the distribution skill (channel details) — this skill is the concrete runb
 These files pin the crate version and must all move together:
 
 - `Cargo.toml` — `version = "X.Y.Z"` in `[package]`
-- `pub/onde_cli/pubspec.yaml` — `version: X.Y.Z`
-- `server.json` — three occurrences: top-level `version`, and the npm and NuGet
+- `packaging/pub/onde_cli/pubspec.yaml` — `version: X.Y.Z`
+- `packaging/mcp/server.json` — three occurrences: top-level `version`, and the npm and NuGet
   `packages[].version` entries (search for the old version string to catch all)
 
 `docs/mcp-registry.md` and `.github/workflows/release-mcp-registry.yml` mention
 past versions only as historical examples — do not bump those.
 
 The npm wrapper manifests are NOT bump targets: the committed `package.json` files
-are rewritten at release time by `npm/scripts/render-*.cjs` from the tag.
+are rewritten at release time by `packaging/npm/scripts/render-*.cjs` from the tag.
 
-After editing, run `cargo check --locked` (or let the build update `Cargo.lock`)
-so the lockfile carries the new version, and commit it in the same bump commit.
+After editing, run `cargo check` so `Cargo.lock` picks up the new version, then
+`cargo check --locked` to confirm, and commit the lockfile in the bump commit.
+(`--locked` refuses to rewrite the lockfile, so it can't be the step that updates it.)
 
 ## Sequence
 
@@ -43,6 +44,7 @@ Follow the git skill's branch flow — `release/vX.Y.Z → development → main`
 `--no-ff` at every hop, tag on the final `main` merge commit. Concretely:
 
 ```bash
+git fetch <remote>                     # pre-flight: local development/main must match the remote tips
 git checkout development
 git pull <remote> development          # start from the pushed tip
 git checkout -b release/vX.Y.Z
@@ -58,6 +60,10 @@ git push <remote> development main vX.Y.Z
 git branch -d release/vX.Y.Z           # only after the merge lands
 ```
 
+Before the checkout, compare local `development` and `main` with the remote tips
+(`git rev-list --left-right --count development...<remote>/development`). If a checkout
+is blocked by untracked leftovers, move them aside; don't delete them.
+
 The remote here is the one whose URL is the sigit.si or GitHub org repo —
 check `git remote -v`; this repo is commonly cloned with per-account remotes
 (`gh-setoelkahfi`, `gh-paydii`, `gh-keypair34`) rather than `origin`.
@@ -101,18 +107,23 @@ Every `git commit` and `git merge` in this flow creates a commit — configure
 signing so merges are signed too, or amend unsigned ones before pushing
 (`git commit --amend --no-edit -S`, only on unpushed commits).
 
-Commit trailer: end release-related commit messages with
-
-```
-Co-Authored-By: siGit Code v1.6.7-acp <noreply@sigit.si>
-```
+Commit trailer: end release commits with the co-author trailer of the agent making
+the commit, exactly as that agent's system prompt gives it, for example
+`OndeCode v<version>-<surface> <noreply@ondeinference.com>` or
+`siGit Code v<version>-<surface> <noreply@sigit.si>`. Don't copy a version from an
+older commit or from this file.
 
 ## The tag push is the release
 
-Pushing `vX.Y.Z` triggers `release-crates.yml`, which verifies the tag against
-`Cargo.toml` and `pubspec.yaml`, publishes the crate, then dispatches the
-wrapper workflows (GitHub Releases, npm, NuGet, PyPI, then Homebrew and pub.dev
-after the GitHub Release assets exist). There is no separate "publish" step.
+Pushing `vX.Y.Z` triggers a three-level chain. There is no separate "publish" step.
+
+1. `release-crates.yml` (CLI Release Crates.io) checks the tag against `Cargo.toml` and
+   `packaging/pub/onde_cli/pubspec.yaml`, publishes the crate, then dispatches
+   **GitHub, npm, NuGet and PyPI**.
+2. `release-github.yml` (CLI Release GitHub) then dispatches **Homebrew, pub.dev, Scoop and winget**
+   once the release assets exist. A failed Scoop or winget dispatch only logs a warning
+   (`core.warning`), so it is easy to miss.
+3. `release-nuget.yml` (CLI Release NuGet) then dispatches the **MCP Registry Release**.
 
 Watch it land:
 
@@ -121,7 +132,7 @@ gh run list --branch vX.Y.Z
 gh run watch <run-id> --exit-status
 ```
 
-`CI` also runs on the tag push; both should be green. If `release-crates` fails,
+`Tests` (`ci.yml`) also runs on the tag push; both should be green. If `release-crates` fails,
 no wrapper publishes — fix the cause, move the tag only if it has not published
 anything yet (crates.io versions are immutable; a failed verify is safe to retry,
 a published crate is not).
@@ -132,9 +143,14 @@ After the pipeline finishes, spot-check the fan-out (all idempotent, safe to re-
 
 - crates.io: `cargo search onde-cli --limit 1`
 - GitHub Release: `gh release view vX.Y.Z`
-- npm: `npm view onde-cli version`
+- npm: `npm view @ondeinference/cli version`
 - PyPI: `https://pypi.org/pypi/onde-cli/json` → `info.version`
-- NuGet: flat container index for `onde-cli`
+- NuGet: `https://api.nuget.org/v3-flatcontainer/onde.cli/index.json`
+- pub.dev: `https://pub.dev/api/packages/onde_cli` → `latest.version`
+- MCP Registry: the `MCP Registry Release` run is green
+- Scoop / winget: `gh run list --workflow release-scoop.yml` / `--workflow release-winget.yml`
+  show a run for the tag (they can silently not dispatch). winget lands as a PR to
+  `microsoft/winget-pkgs` and only appears after Microsoft's review.
 - Homebrew/pub.dev trail the GitHub Release; they may take a few extra minutes
 
 ## Failure modes seen before
@@ -145,5 +161,8 @@ After the pipeline finishes, spot-check the fan-out (all idempotent, safe to re-
 - Deleting a leftover `release/` branch that contained unsigned bump commits and
   redoing the bump fresh — fine, but check it first.
 - Forgetting `Cargo.lock` in the bump commit.
+- Stale local `development`/`main` (once 12 commits behind the remote), with checkout
+  blocked by untracked leftovers from a branch made before the `packaging/` move, at
+  paths the newer branch tracks. Fetch first, move the leftovers aside, don't delete.
 - Pushing with the wrong `gh` account active — the push works, but PR/issue
   actions afterwards get attributed to the wrong identity.

{onde_cli-0.4.3 → onde_cli-0.5.0}/.agents/skills/release/evals/evals.json

@@ -4,7 +4,7 @@
     {
       "id": 1,
       "prompt": "Cut release v0.4.3 for onde-cli. Bump all version pins, follow the repo's release branch flow, tag, and push.",
-      "expected_output": "Agent bumps Cargo.toml, pubspec.yaml, server.json (3 spots), commits signed with Co-Authored-By trailer, creates release/v0.4.3 from development, merges --no-ff into development then main, tags the main merge commit, pushes development+main+tag, and watches the release pipeline.",
+      "expected_output": "Agent bumps Cargo.toml, pubspec.yaml, packaging/mcp/server.json (3 spots), commits signed with Co-Authored-By trailer, creates release/v0.4.3 from development, merges --no-ff into development then main, tags the main merge commit, pushes development+main+tag, and watches the release pipeline.",
       "files": []
     },
     {
@@ -22,7 +22,7 @@
     {
       "id": 4,
       "prompt": "Update the README install instructions for the npm wrapper and fix the NuGet README badge that points at the wrong package id.",
-      "expected_output": "Should NOT deeply engage the release skill beyond reading it; this is distribution/README work. Agent edits npm/onde-cli/README.md and nuget/onde-cli/README.md without cutting a release, bumping versions, or tagging.",
+      "expected_output": "Should NOT deeply engage the release skill beyond reading it; this is distribution/README work. Agent edits packaging/npm/onde-cli/README.md and packaging/nuget/onde-cli/README.md without cutting a release, bumping versions, or tagging.",
       "files": []
     },
     {

{onde_cli-0.4.3 → onde_cli-0.5.0}/.claude/skills/distribution/SKILL.md

@@ -56,9 +56,9 @@ Good fit for users who already live in npm tooling.
 
 Important release detail:
 
-- the committed `npm/onde-cli/package.json` is a working file, not the publish-time source of truth
-- the release workflow rewrites the base package manifest with `npm/scripts/render-main-package.cjs`
-- platform package manifests are generated on the fly with `npm/scripts/render-platform-package.cjs`
+- the committed `packaging/npm/onde-cli/package.json` is a working file, not the publish-time source of truth
+- the release workflow rewrites the base package manifest with `packaging/npm/scripts/render-main-package.cjs`
+- platform package manifests are generated on the fly with `packaging/npm/scripts/render-platform-package.cjs`
 - the actual npm version comes from the release tag via `RELEASE_VERSION`, not from manually editing the committed npm manifest before publish
 
 ### PyPI
@@ -177,7 +177,7 @@ That makes the safest design a thin Dart launcher that downloads the right nativ
 
 Practical consequences:
 
-- `pub/onde_cli/native/` should stay out of the published package
+- `packaging/pub/onde_cli/native/` should stay out of the published package
 - do not set `publish_to: https://pub.dev` in `pubspec.yaml`; omit `publish_to` for normal pub.dev publishing
 - use package-level ignore rules so local native staging does not leak into publish input
 - keep release asset names aligned with the GitHub Release workflow, because the launcher depends on them
@@ -186,9 +186,9 @@ Practical consequences:
 
 Run these during verification:
 
-- `dart pub get --directory pub/onde_cli`
-- `dart analyze pub/onde_cli`
-- `dart pub publish --dry-run --directory pub/onde_cli`
+- `dart pub get --directory packaging/pub/onde_cli`
+- `dart analyze packaging/pub/onde_cli`
+- `dart pub publish --dry-run --directory packaging/pub/onde_cli`
 
 ## NuGet-specific notes
 
@@ -210,10 +210,10 @@ Every user-facing channel should document the same product with channel-specific
 Main files:
 
 - `README.md`
-- `npm/onde-cli/README.md`
-- `pypi/README.md`
-- `nuget/onde-cli/README.md`
-- `pub/onde_cli/README.md`
+- `packaging/npm/onde-cli/README.md`
+- `packaging/pypi/README.md`
+- `packaging/nuget/onde-cli/README.md`
+- `packaging/pub/onde_cli/README.md`
 
 Keep these aligned on:
 

{onde_cli-0.4.3/.agents → onde_cli-0.5.0/.claude}/skills/release/SKILL.md

@@ -24,18 +24,19 @@ and the distribution skill (channel details) — this skill is the concrete runb
 These files pin the crate version and must all move together:
 
 - `Cargo.toml` — `version = "X.Y.Z"` in `[package]`
-- `pub/onde_cli/pubspec.yaml` — `version: X.Y.Z`
-- `server.json` — three occurrences: top-level `version`, and the npm and NuGet
+- `packaging/pub/onde_cli/pubspec.yaml` — `version: X.Y.Z`
+- `packaging/mcp/server.json` — three occurrences: top-level `version`, and the npm and NuGet
   `packages[].version` entries (search for the old version string to catch all)
 
 `docs/mcp-registry.md` and `.github/workflows/release-mcp-registry.yml` mention
 past versions only as historical examples — do not bump those.
 
 The npm wrapper manifests are NOT bump targets: the committed `package.json` files
-are rewritten at release time by `npm/scripts/render-*.cjs` from the tag.
+are rewritten at release time by `packaging/npm/scripts/render-*.cjs` from the tag.
 
-After editing, run `cargo check --locked` (or let the build update `Cargo.lock`)
-so the lockfile carries the new version, and commit it in the same bump commit.
+After editing, run `cargo check` so `Cargo.lock` picks up the new version, then
+`cargo check --locked` to confirm, and commit the lockfile in the bump commit.
+(`--locked` refuses to rewrite the lockfile, so it can't be the step that updates it.)
 
 ## Sequence
 
@@ -43,6 +44,7 @@ Follow the git skill's branch flow — `release/vX.Y.Z → development → main`
 `--no-ff` at every hop, tag on the final `main` merge commit. Concretely:
 
 ```bash
+git fetch <remote>                     # pre-flight: local development/main must match the remote tips
 git checkout development
 git pull <remote> development          # start from the pushed tip
 git checkout -b release/vX.Y.Z
@@ -58,6 +60,10 @@ git push <remote> development main vX.Y.Z
 git branch -d release/vX.Y.Z           # only after the merge lands
 ```
 
+Before the checkout, compare local `development` and `main` with the remote tips
+(`git rev-list --left-right --count development...<remote>/development`). If a checkout
+is blocked by untracked leftovers, move them aside; don't delete them.
+
 The remote here is the one whose URL is the sigit.si or GitHub org repo —
 check `git remote -v`; this repo is commonly cloned with per-account remotes
 (`gh-setoelkahfi`, `gh-paydii`, `gh-keypair34`) rather than `origin`.
@@ -101,18 +107,23 @@ Every `git commit` and `git merge` in this flow creates a commit — configure
 signing so merges are signed too, or amend unsigned ones before pushing
 (`git commit --amend --no-edit -S`, only on unpushed commits).
 
-Commit trailer: end release-related commit messages with
-
-```
-Co-Authored-By: siGit Code v1.6.7-acp <noreply@sigit.si>
-```
+Commit trailer: end release commits with the co-author trailer of the agent making
+the commit, exactly as that agent's system prompt gives it, for example
+`OndeCode v<version>-<surface> <noreply@ondeinference.com>` or
+`siGit Code v<version>-<surface> <noreply@sigit.si>`. Don't copy a version from an
+older commit or from this file.
 
 ## The tag push is the release
 
-Pushing `vX.Y.Z` triggers `release-crates.yml`, which verifies the tag against
-`Cargo.toml` and `pubspec.yaml`, publishes the crate, then dispatches the
-wrapper workflows (GitHub Releases, npm, NuGet, PyPI, then Homebrew and pub.dev
-after the GitHub Release assets exist). There is no separate "publish" step.
+Pushing `vX.Y.Z` triggers a three-level chain. There is no separate "publish" step.
+
+1. `release-crates.yml` (CLI Release Crates.io) checks the tag against `Cargo.toml` and
+   `packaging/pub/onde_cli/pubspec.yaml`, publishes the crate, then dispatches
+   **GitHub, npm, NuGet and PyPI**.
+2. `release-github.yml` (CLI Release GitHub) then dispatches **Homebrew, pub.dev, Scoop and winget**
+   once the release assets exist. A failed Scoop or winget dispatch only logs a warning
+   (`core.warning`), so it is easy to miss.
+3. `release-nuget.yml` (CLI Release NuGet) then dispatches the **MCP Registry Release**.
 
 Watch it land:
 
@@ -121,7 +132,7 @@ gh run list --branch vX.Y.Z
 gh run watch <run-id> --exit-status
 ```
 
-`CI` also runs on the tag push; both should be green. If `release-crates` fails,
+`Tests` (`ci.yml`) also runs on the tag push; both should be green. If `release-crates` fails,
 no wrapper publishes — fix the cause, move the tag only if it has not published
 anything yet (crates.io versions are immutable; a failed verify is safe to retry,
 a published crate is not).
@@ -132,9 +143,14 @@ After the pipeline finishes, spot-check the fan-out (all idempotent, safe to re-
 
 - crates.io: `cargo search onde-cli --limit 1`
 - GitHub Release: `gh release view vX.Y.Z`
-- npm: `npm view onde-cli version`
+- npm: `npm view @ondeinference/cli version`
 - PyPI: `https://pypi.org/pypi/onde-cli/json` → `info.version`
-- NuGet: flat container index for `onde-cli`
+- NuGet: `https://api.nuget.org/v3-flatcontainer/onde.cli/index.json`
+- pub.dev: `https://pub.dev/api/packages/onde_cli` → `latest.version`
+- MCP Registry: the `MCP Registry Release` run is green
+- Scoop / winget: `gh run list --workflow release-scoop.yml` / `--workflow release-winget.yml`
+  show a run for the tag (they can silently not dispatch). winget lands as a PR to
+  `microsoft/winget-pkgs` and only appears after Microsoft's review.
 - Homebrew/pub.dev trail the GitHub Release; they may take a few extra minutes
 
 ## Failure modes seen before
@@ -145,5 +161,8 @@ After the pipeline finishes, spot-check the fan-out (all idempotent, safe to re-
 - Deleting a leftover `release/` branch that contained unsigned bump commits and
   redoing the bump fresh — fine, but check it first.
 - Forgetting `Cargo.lock` in the bump commit.
+- Stale local `development`/`main` (once 12 commits behind the remote), with checkout
+  blocked by untracked leftovers from a branch made before the `packaging/` move, at
+  paths the newer branch tracks. Fetch first, move the leftovers aside, don't delete.
 - Pushing with the wrong `gh` account active — the push works, but PR/issue
   actions afterwards get attributed to the wrong identity.

{onde_cli-0.4.3 → onde_cli-0.5.0}/.claude/skills/release/evals/evals.json

@@ -4,7 +4,7 @@
     {
       "id": 1,
       "prompt": "Cut release v0.4.3 for onde-cli. Bump all version pins, follow the repo's release branch flow, tag, and push.",
-      "expected_output": "Agent bumps Cargo.toml, pubspec.yaml, server.json (3 spots), commits signed with Co-Authored-By trailer, creates release/v0.4.3 from development, merges --no-ff into development then main, tags the main merge commit, pushes development+main+tag, and watches the release pipeline.",
+      "expected_output": "Agent bumps Cargo.toml, pubspec.yaml, packaging/mcp/server.json (3 spots), commits signed with Co-Authored-By trailer, creates release/v0.4.3 from development, merges --no-ff into development then main, tags the main merge commit, pushes development+main+tag, and watches the release pipeline.",
       "files": []
     },
     {
@@ -22,7 +22,7 @@
     {
       "id": 4,
       "prompt": "Update the README install instructions for the npm wrapper and fix the NuGet README badge that points at the wrong package id.",
-      "expected_output": "Should NOT deeply engage the release skill beyond reading it; this is distribution/README work. Agent edits npm/onde-cli/README.md and nuget/onde-cli/README.md without cutting a release, bumping versions, or tagging.",
+      "expected_output": "Should NOT deeply engage the release skill beyond reading it; this is distribution/README work. Agent edits packaging/npm/onde-cli/README.md and packaging/nuget/onde-cli/README.md without cutting a release, bumping versions, or tagging.",
       "files": []
     },
     {

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: CI
+name: Tests
 
 on:
   push:
@@ -121,7 +121,7 @@ jobs:
           dotnet-version: 8.0.x
 
       - name: Build .NET tool launcher
-        run: dotnet build nuget/onde-cli/Onde.Cli.csproj --configuration Release
+        run: dotnet build packaging/nuget/onde-cli/Onde.Cli.csproj --configuration Release
 
   dart-package:
     name: Dart pub package check
@@ -134,11 +134,11 @@ jobs:
         uses: dart-lang/setup-dart@v1
 
       - name: Get package dependencies
-        working-directory: pub/onde_cli
+        working-directory: packaging/pub/onde_cli
         run: dart pub get
 
       - name: Analyze Dart package
-        working-directory: pub/onde_cli
+        working-directory: packaging/pub/onde_cli
         run: dart analyze
 
   build:

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-crates.yml

@@ -1,4 +1,4 @@
-name: Release crates.io
+name: CLI Release Crates.io
 
 # This is the only workflow that reacts to a tag push. It verifies the tag,
 # publishes the crate, and then dispatches every distribution workflow with the
@@ -93,7 +93,7 @@ jobs:
       - name: Ensure the pub.dev wrapper matches the tag
         shell: bash
         run: |
-          pub_version="$(sed -n 's/^version: \(.*\)/\1/p' pub/onde_cli/pubspec.yaml | head -n 1)"
+          pub_version="$(sed -n 's/^version: \(.*\)/\1/p' packaging/pub/onde_cli/pubspec.yaml | head -n 1)"
           if [ "$pub_version" != "${{ steps.release.outputs.version }}" ]; then
             echo "::error::pubspec.yaml is ${pub_version} but the tag is ${{ steps.release.outputs.version }}"
             exit 1

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-github.yml

@@ -1,4 +1,4 @@
-name: GitHub Release
+name: CLI Release GitHub
 
 # Dispatched by release-crates.yml once the crate publish succeeds.
 on:

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-homebrew.yml

@@ -1,4 +1,4 @@
-name: Homebrew CLI Release
+name: CLI Release Homebrew
 
 on:
   workflow_dispatch:

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-mcp-registry.yml

@@ -36,24 +36,24 @@ jobs:
       - name: Check the server name is consistent across packages
         shell: bash
         run: |
-          server_name="$(jq -r '.name' server.json)"
+          server_name="$(jq -r '.name' packaging/mcp/server.json)"
           echo "Server name: ${server_name}"
 
           # npm proves ownership through `mcpName` in the published package.json,
           # rendered at release time from this template.
-          grep -q "\"mcpName\": \"${server_name}\"" npm/package-main.json.tmpl
+          grep -q "\"mcpName\": \"${server_name}\"" packaging/npm/package-main.json.tmpl
 
           # NuGet proves ownership through an `mcp-name:` marker in the package README.
-          grep -q "mcp-name: ${server_name}" nuget/onde-cli/README.md
+          grep -q "mcp-name: ${server_name}" packaging/nuget/onde-cli/README.md
 
       - name: Set the version in server.json
         shell: bash
         run: |
           jq --arg v "${RELEASE_VERSION}" \
             '.version = $v | .packages |= map(.version = $v)' \
-            server.json > server.tmp
-          mv server.tmp server.json
-          cat server.json
+            packaging/mcp/server.json > server.tmp
+          mv server.tmp packaging/mcp/server.json
+          cat packaging/mcp/server.json
 
       - name: Verify the published packages carry the ownership marker
         shell: bash
@@ -62,7 +62,7 @@ jobs:
           # listed package and looking for a marker naming this server. Checking
           # the sources isn't enough: a package published before the marker
           # landed will still be missing it. Both comparisons are case-sensitive.
-          server_name="$(jq -r '.name' server.json)"
+          server_name="$(jq -r '.name' packaging/mcp/server.json)"
 
           # npm is queryable within seconds of publishing, but the npm release
           # workflow may still be building its platform packages when this runs.
@@ -121,10 +121,11 @@ jobs:
 
       - name: Publish
         shell: bash
-        run: ./mcp-publisher publish
+        working-directory: packaging/mcp
+        run: ../../mcp-publisher publish
 
       - name: Verify the server is listed
         shell: bash
         run: |
-          server_name="$(jq -r '.name' server.json)"
+          server_name="$(jq -r '.name' packaging/mcp/server.json)"
           curl -fsSL "https://registry.modelcontextprotocol.io/v0.1/servers?search=${server_name}" | jq .

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-npm.yml

@@ -1,4 +1,4 @@
-name: NPM Release
+name: CLI Release NPM
 
 # Dispatched by release-crates.yml once the crate publish succeeds.
 on:
@@ -113,7 +113,7 @@ jobs:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         shell: bash
         run: |
-          cd npm
+          cd packaging/npm
 
           # Binary name from Cargo.toml
           cargo_bin="onde"
@@ -153,7 +153,7 @@ jobs:
             cargo_bin="${cargo_bin}.exe"
           fi
 
-          cp "../target/${{ matrix.build.TARGET }}/release/${cargo_bin}" "${node_pkg}/bin"
+          cp "../../target/${{ matrix.build.TARGET }}/release/${cargo_bin}" "${node_pkg}/bin"
 
           cd "${node_pkg}"
 
@@ -198,7 +198,7 @@ jobs:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         shell: bash
         run: |
-          cd npm/onde-cli
+          cd packaging/npm/onde-cli
 
           # Rewrite package.json with the correct release version and
           # matching optionalDependency versions

{onde_cli-0.4.3 → onde_cli-0.5.0}/.github/workflows/release-nuget.yml

@@ -1,4 +1,4 @@
-name: NuGet Release
+name: CLI Release NuGet
 
 # Dispatched by release-crates.yml once the crate publish succeeds.
 on:
@@ -142,7 +142,7 @@ jobs:
         uses: actions/download-artifact@v4
         with:
           pattern: nuget-native-*
-          path: nuget/onde-cli/native
+          path: packaging/nuget/onde-cli/native
           merge-multiple: true
 
       - name: Setup .NET SDK
@@ -153,16 +153,16 @@ jobs:
       - name: Pack .NET tool
         shell: bash
         run: |
-          dotnet pack nuget/onde-cli/Onde.Cli.csproj \
+          dotnet pack packaging/nuget/onde-cli/Onde.Cli.csproj \
             --configuration Release \
-            --output nuget/dist \
+            --output packaging/nuget/dist \
             -p:PackageVersion=${RELEASE_VERSION}
 
       - name: Upload package artifact
         uses: actions/upload-artifact@v4
         with:
           name: nuget-package
-          path: nuget/dist/*.nupkg
+          path: packaging/nuget/dist/*.nupkg
 
   smoke-test:
     name: Smoke test (${{ matrix.os }})
@@ -197,7 +197,7 @@ jobs:
         uses: actions/download-artifact@v4
         with:
           name: nuget-package
-          path: nuget/dist
+          path: packaging/nuget/dist
 
       - name: Setup .NET SDK
         uses: actions/setup-dotnet@v4
@@ -207,7 +207,7 @@ jobs:
       - name: Install tool from local package
         shell: pwsh
         run: |
-          $packageSource = (Resolve-Path "nuget/dist").Path
+          $packageSource = (Resolve-Path "packaging/nuget/dist").Path
           @"
           <?xml version="1.0" encoding="utf-8"?>
           <configuration>
@@ -216,11 +216,11 @@ jobs:
               <add key="local" value="$packageSource" />
             </packageSources>
           </configuration>
-          "@ | Set-Content -Path "nuget/NuGet.Config"
+          "@ | Set-Content -Path "packaging/nuget/NuGet.Config"
 
           dotnet tool install `
             --tool-path ".tool" `
-            --configfile "nuget/NuGet.Config" `
+            --configfile "packaging/nuget/NuGet.Config" `
             --version "$env:RELEASE_VERSION" `
             "$env:NUGET_PACKAGE_ID"
 
@@ -272,7 +272,7 @@ jobs:
         uses: actions/download-artifact@v4
         with:
           name: nuget-package
-          path: nuget/dist
+          path: packaging/nuget/dist
 
       - name: Setup .NET SDK
         uses: actions/setup-dotnet@v4
@@ -297,7 +297,7 @@ jobs:
           NUGET_API_KEY: ${{ secrets.NUGET_API_KEY }}
         shell: bash
         run: |
-          dotnet nuget push nuget/dist/*.nupkg \
+          dotnet nuget push packaging/nuget/dist/*.nupkg \
             --api-key "${NUGET_API_KEY}" \
             --source https://api.nuget.org/v3/index.json \
             --skip-duplicate