wai-quantum: the job service on the MCP Registry, and wai-quantum-cli 0.2.1 for the command line's listing #528

Merged

dcharlot merged 2 commits from wai/quantum-mcp-registry into main 2026-10-29 03:19:36 -04:00

Conversation 0 Commits 2 Files changed 10 +23 -19

dcharlot commented 2026-10-29 01:10:28 -04:00

Owner

Copy link

The MCP Registry now lists the job service as science.transaction.wai/quantum-jobs 0.2.0 (remote, streamable HTTP, https://wai.transaction.science/quantum-jobs/mcp), under the namespace proved by https://wai.transaction.science/.well-known/mcp-registry-auth. This PR makes the repository match, and releases wai-quantum-cli 0.2.1 so the command line can be listed too.

• server.json (both): repository dropped. The registry refuses it for the forge's address and for the public mirror's, and the field is optional. The service's file is what was published, byte for byte. No test reads the field.
• wai-quantum-cli/README.md: an HTML comment carrying mcp-name: science.transaction.wai/quantum, the line the registry reads from a crate's README. crates.io's 0.2.0 README lacks it, so the registry refused that entry.
• wai-quantum-cli 0.2.1: no code change. Cargo.toml and server.json (both of its version fields) are bumped, the desktop app requires 0.2.1, and both lockfiles that hold the crate move with it (cargo metadata --locked resolves both).
• READMEs: the CLI's README (and its translation) and the service's README no longer say "not submitted".
• wai/CHANGELOG.md: a wai-quantum-cli 0.2.1 heading under Unreleased.

After the merge: cargo publish of wai-quantum-cli 0.2.1, the tag wai-quantum-cli-v0.2.1 (binaries, wheels, tap and bucket), then the registry entry science.transaction.wai/quantum 0.2.1.

The first run's one red check, joule-code-rs on linux-arm64, is joule-moq-relay's age_rising timing test (line 138: a group reached the slow viewer before the rise was held). This PR does not touch that crate.

Public-name check: clean.

🤖 Generated with Claude Code

The MCP Registry now lists the job service as `science.transaction.wai/quantum-jobs` 0.2.0 (remote, streamable HTTP, `https://wai.transaction.science/quantum-jobs/mcp`), under the namespace proved by `https://wai.transaction.science/.well-known/mcp-registry-auth`. This PR makes the repository match, and releases `wai-quantum-cli` 0.2.1 so the command line can be listed too. - **`server.json` (both):** `repository` dropped. The registry refuses it for the forge's address and for the public mirror's, and the field is optional. The service's file is what was published, byte for byte. No test reads the field. - **`wai-quantum-cli/README.md`:** an HTML comment carrying `mcp-name: science.transaction.wai/quantum`, the line the registry reads from a crate's README. crates.io's 0.2.0 README lacks it, so the registry refused that entry. - **`wai-quantum-cli` 0.2.1:** no code change. `Cargo.toml` and `server.json` (both of its version fields) are bumped, the desktop app requires 0.2.1, and both lockfiles that hold the crate move with it (`cargo metadata --locked` resolves both). - **READMEs:** the CLI's README (and its translation) and the service's README no longer say "not submitted". - **`wai/CHANGELOG.md`:** a `wai-quantum-cli 0.2.1` heading under Unreleased. After the merge: `cargo publish` of wai-quantum-cli 0.2.1, the tag `wai-quantum-cli-v0.2.1` (binaries, wheels, tap and bucket), then the registry entry `science.transaction.wai/quantum` 0.2.1. The first run's one red check, `joule-code-rs` on linux-arm64, is `joule-moq-relay`'s `age_rising` timing test (line 138: a group reached the slow viewer before the rise was held). This PR does not touch that crate. Public-name check: clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-10-29 01:10:28 -04:00

wai-quantum: the job service listed on the MCP Registry; the command line's README ready for it ... 7bb75bc2e7

The MCP Registry now lists the job service as science.transaction.wai/quantum-jobs
0.2.0, under the namespace that the site's /.well-known/mcp-registry-auth proves.

- Both server.json files drop `repository`, which the registry refuses for the
  forge's address (and for the public mirror's). What was published is these
  files, byte for byte.
- The command line's README carries the `mcp-name` line that the registry reads
  from a crate's README. 0.2.0's README on crates.io lacks it, so the registry
  refused science.transaction.wai/quantum; the next wai-quantum-cli can be listed.
- The two READMEs that said "not submitted" (and the translation) say what is so;
  the changelog records it under Unreleased.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot changed title from wai-quantum: the job service on the MCP Registry; the CLI's README ready for its listing to wai-quantum: the job service on the MCP Registry, and wai-quantum-cli 0.2.1 for the command line's listing 2026-10-29 01:24:44 -04:00

dcharlot added 1 commit 2026-10-29 01:24:46 -04:00

wai-quantum-cli 0.2.1: the README line the MCP Registry reads ... 2300afdaf9

0.2.1 is 0.2.0 with no code change, published so that crates.io carries the
README with `mcp-name: science.transaction.wai/quantum` and the registry can
list the command line's server.

- Cargo.toml and server.json (its version and its package's): 0.2.1.
- The desktop app requires 0.2.1; both lockfiles that hold wai-quantum-cli move.
- The changelog's Unreleased entry becomes the 0.2.1 release heading.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit f13707d47a into main 2026-10-29 03:19:36 -04:00

dcharlot referenced this pull request from a commit 2026-10-29 03:19:37 -04:00

Merge pull request 'wai-quantum: the job service on the MCP Registry, and wai-quantum-cli 0.2.1 for the command line's listing' (#528) from wai/quantum-mcp-registry into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!528

No description provided.