Repository navigation
Releases
AgentTCDH v0.1.6
AgentTCDH v0.1.6
This release bundles six improvements for managing multiple hubs and maintaining registrations after import:
- Named private hub profiles with explicit activation, read/admin credential reference separation, and previewed mutations.
- Import-profile selection and source-path editing without discarding managed ownership or automatically pruning registrations.
- A unified status report for registry access, registration counts, local source drift, environment prerequisites, and stored metadata observations.
- Revision-bound metadata freshness and explicit consumer-side inspection/refresh of stale, changed, unknown, or unsuccessful targets.
- Transactional, bounded registry history and guarded single-target undo that refuses subsequent edits and deletion/recreation conflicts.
- Guided first-use setup that composes source selection, previewed registration, optional import-profile storage, and explicitly selected client configuration output.
See the management guide for commands, limits, credential precedence, partial failures, and recovery.
Compatibility and scope
Node.js 24+ remains required. SQLite schema advances from 2 to 3 transactionally and accepts existing versions 0–2. Preserve a database backup before upgrading; older binaries reject schema 3. Existing target definitions, revisions, snapshot format 1, and MCP/A2A discovery messages remain compatible. New HTTP APIs provide administrator history/undo and observation recording, with read-only metadata freshness. Discovery is still separate from execution.
Hub profiles are local, private, and independent of import profiles and server setup. Their active selection never changes serve or init. Credential values remain in the consuming environment. Metadata observations explicitly identify consumer reports and never assert tool/task execution. Existing metadata commands do not implicitly record observations.
History starts at upgrade time and retains at most 1000 events within a 16 MiB UTF-8 definition/overhead budget. It is not an archival audit system. Undo restores registry definitions only and does not rewrite import ownership or reverse external effects. Inspect full history definitions only through administrator access.
Verification and publication
Release requires regression/type checks, installed-package verification of all six workflows, native Linux/macOS/Windows checks, and container checks. Exact release assets must be verified before publication. Local execution, CI execution, GitHub release availability, and public npm availability are separate gates; no configured-but-unrun check implies a passed result.
Executed verification
- Source:
7151d3f, merged through PR #26. - Local typecheck/regression: 287 tests passed. Real Linux terminal setup selection and a write-free preview also passed.
- Native Linux, macOS ARM, macOS Intel, Windows, and container checks passed for the PR, main, and release.
- Installed-package verification covers all six new management workflows, existing discovery/direct-call fixtures, and restart persistence. GitHub assets match the locally verified final candidate byte for byte.
- A post-download verification initially reported one failed stdio metadata observation. The unchanged artifact passed a complete rerun and 20 additional focused fixture inspections (maximum 677 ms). The initial cause was not isolated; the failed attempt is retained in the local release evidence.
- Public npm metadata,
latest, tarball integrity, a fresh-cache npm pack, installed CLI identity, private hub/import profiles, profile editing, and guided setup preview passed at 2026-11-08T06:09:42.974Z. These are fixture/package checks; no commercial agents, public target providers, or models were invoked.
Artifact SHA-256: 1706481db13b2f2874294fd8194d48c6a1711fc30c2739d0e1447d4e584bb29a.
Availability
Published on npm as agent-tcdh@0.1.6; the public latest tag is 0.1.6. npm and GitHub tarballs are identical.
npm install --global agent-tcdh@0.1.6
agent-tcdh --versionAgentTCDH v0.1.5
AgentTCDH v0.1.5
Version 0.1.5 bundles the complete local connection import and maintenance flow. Bring existing MCP/A2A declarations into the registry, select them interactively, save a reusable private profile, and maintain their metadata and source changes. The hub continues to return discovery metadata; consumers connect directly.
Preparation, GitHub publication, and npm publication are separate. A source version or verified candidate does not establish that either public destination has been published. Check the destination before installing.
Publication status — 2026-11-04
GitHub and npm v0.1.5 publication completed. Public npm version and latest both report 0.1.5. The public registry SHA-512 integrity and downloaded bytes match the verified GitHub tarball; an independent npm download using an empty cache matched as well. Fresh installed CLI version/help, local import preview, private profile creation/listing, and offline backup listing passed at 2026-11-04T08:42:32.843Z.
Source commit: 7dd36d8e2099d95146afd29be9e50818a08e71dc.
Tarball SHA-256: 5fcf262fee3b4f00209a64e100d696508c036eb9dcb827df69908893aaef00f1.
Validation: 270 local Linux regression tests passed with no failures/skips. All native Linux, macOS ARM64/x64, Windows, and container jobs passed in PR CI, main CI, and the release workflow. Installed-package verification and platform-specific lifecycle checks ran in their applicable native jobs. The downloaded public GitHub bundle separately passed exact-source/checksum/installed-workflow verification before npm publication.
npm install --global agent-tcdh@0.1.5
agent-tcdh registry import-local --interactive --save-profile workIncluded workflow
- Local discovery/import: locate bounded Codex, Claude Code, OpenCode, Gemini CLI, Cursor, and VS Code configuration sources. Preserve origins, show source-qualified keys, coalesce compatible declarations conservatively, and import a selected group atomically. Gemini remote A2A definitions support inline cards; URL-only cards require explicit metadata lookup.
- Interactive selection: a terminal checkbox list supports arrows, space, select-all, acceptance, and cancellation. No connections are preselected. Automated usage retains explicit
--selectkeys and JSON output. - Private import profiles: save pinned source locations, selectors, hub identity, optional credential environment names, and synchronization fingerprints. Reuse a named profile without copying source commands or credential values into the ledger. Offline list/show/removal commands manage the private store.
- Source synchronization: preview additions, field changes, disappeared declarations, and conflicts. Preserve hub-only edits; conflicting edits to the same field block writes. Existing IDs survive representative-origin changes. Removal requires explicit
--prune --applyand an unchanged managed definition. - Metadata follow-up: optionally refresh and diagnose imported/synchronized targets with one metadata observation each. Conditional writes preserve labels/state/auth references and no-op revisions. A failed optional phase does not undo successful registration, and acknowledged ownership is checkpointed before follow-up.
- Registry duplicate cleanup: inspect compatible existing connections, show differing label/capability fields, and explicitly select a representative plus redundant IDs. Fresh versions guard independent removals; different credentials/enabled states are not conflated.
- Opt-in stdio metadata: explicitly authorize consumer-side process startup to initialize and list tools, with bounded output, pagination, deadline, minimal environment, portable Windows shims, and owned-process teardown. This does not call tools/tasks or turn the hub into an executor.
See local import and import management for supported locations, commands, outputs, and boundaries.
Example flow
Requires Node.js 24 or newer:
agent-tcdh registry import-local --interactive --save-profile work --apply
agent-tcdh registry sync-local --profile work
agent-tcdh registry sync-local --profile work --apply --refresh --diagnose
agent-tcdh registry duplicatesUse --fetch-a2a-cards when selected definitions require a remote card lookup. To authorize local server startup for metadata follow-up, additionally pass --inspect-stdio; use --stdio-cwd when a different consumer working directory is required. These permissions are not saved in the profile.
Installation and publication checks
From the verified source checkout, prepare a new local bundle with the release commands. For directory release/v0.1.5:
npm install --global ./release/v0.1.5/agent-tcdh-0.1.5.tgz
agent-tcdh --version --jsonThe built CLI tarball, release.json, and SHA256SUMS bind the package bytes to an exact source commit. Preparation does not publish anything.
Check npm before installing from its registry:
npm view agent-tcdh@0.1.5 versionAfter npm reports 0.1.5, install with npm install --global agent-tcdh@0.1.5 or run npx --yes agent-tcdh@0.1.5 --help. Confirm the GitHub v0.1.5 release exists before downloading its installable assets. Verify its bundle from the tagged checkout, publish those exact tarball bytes to npm, then verify public integrity, latest, and a fresh installation. A committed OIDC workflow does not establish package-side Trusted Publisher authorization.
Compatibility and operational scope
Node.js 24+, SQLite schema version 2, snapshot format version 1, and HTTP/MCP/A2A discovery contracts remain unchanged. Existing registry data, source files, explicit-file import behavior, and default single-target refresh behavior can be reused. New private import-profile storage has its own format version 1 and is machine-local. YAML parsing is supplied by pinned yaml@2.9.1; existing cross-spawn@7.0.6 is now a production dependency for explicit stdio inspection. No provider allowlist, proxy, model planner, or hosted credential service is added.
Profiles use atomic private writes/backups and cooperating operation locks. Limits include 50 profiles and 1 MiB total profile storage, up to 1,000 managed registrations subject to that byte bound, and the existing local scan bounds. Hub and filesystem changes are not a distributed transaction. Initial imports and sync additions use atomic conflict-checked import requests; existing sync changes and duplicate removals have independent conditions/outcomes without automatic rollback or retry. Review state after an unacknowledged request, forced termination, or ledger-write failure. Managed missing IDs are not silently recreated or adopted. Removing a profile does not remove registry entries.
Default previews do not start target processes. Explicit stdio inspection starts executable code with that user's filesystem access and can have program-defined side effects; it is not an OS sandbox. Only initialization/tool listing is requested. Output and lifetime bounds and normal/error/deadline teardown do not guarantee cleanup after forced host termination or escape from the owned process tree. Remote metadata lookup/refresh is also an explicit outbound operation. executionVerified: false distinguishes metadata observation from successful tool/task execution.
Verification scope
Regression coverage exercises source/profile isolation, terminal selection/cancellation, three-way field comparison, conservative pruning, concurrent conditional writes, durable ownership before follow-up, duplicate cleanup, and bounded stdio lifecycle/environment/output behavior. Real PTY checks additionally cover choosing only one connection and cancelling without profile changes.
Installed-package verification uses production dependencies, isolated user/project/profile paths, and local protocol fixtures to run discovery/import, profile persistence, metadata inspection, source synchronization/pruning, duplicate cleanup, persistence/restart, and direct-call examples. Native CI covers Linux x64, macOS ARM64/x64, Windows x64, plus a Linux container. Windows shim inspection and POSIX graceful-interrupt checks are platform-specific; only completed native jobs establish their results. The exact public GitHub bundle is separately verified before npm publication.
Personal AI client settings are not modified by verification. Public providers and real models remain opt-in; this release does not refresh earlier live-provider/model evidence or establish new model executions for every client.
AgentTCDH v0.1.4
AgentTCDH v0.1.4
Version 0.1.4 adds preview-first batch metadata refresh, explicit target groups for diagnosis and refresh, and local CLI version/runtime identity. Consumers still discover connection metadata centrally and execute directly against their selected targets.
Release preparation is separate from publication. Source metadata and candidate verification do not establish that npm or GitHub publication has completed. Confirm the requested destination before installing from it.
Publication status — 2026-11-04
GitHub release published. Its downloaded tarball, manifest, and checksums passed source-identity and isolated installation/runtime verification at commit 0a766cec2f2bb6980ee771aba188b6d5721001f5.
npm package published as jiind. The public version and latest tag both report 0.1.4. Public registry SHA-512 integrity and downloaded bytes match the GitHub tarball; an independent npm download using an empty cache matched as well. Installed CLI help, configuration-independent runtime identity, and offline backup listing passed verification.
npm install --global agent-tcdh@0.1.4
agent-tcdh --version --jsonPublic npm verification completed at 2026-11-04T07:01:49.801Z.
Validation: 234 local regression tests passed. All native Linux, macOS ARM64/x64, Windows, and container jobs passed in final main CI and the release workflow. PR #23 replaced a timing-dependent concurrency assertion with synchronized coverage before publication.
Tarball SHA-256: 0baf0f2cf92c15e9c7d6ea837be10f8ecbfe8aba71195faf6480dfdc77dbcd11.
Included changes
target refresh --all: collect a bounded, filtered group and preview remote metadata changes. Explicit--applysaves changed registrations independently with per-target version checks. Unchanged definitions retain their versions and timestamps.doctor --select ID --select IDandtarget refresh --select ID --select ID: resolve an explicit group without enumerating catalog pages, preserve request order, and validate every selected registration before provider work. Missing/unreadable IDs or disabled entries without--include-disabledreject the complete selection.--version/-v: print the declared package version without loading configuration, resolving credentials, or contacting a hub.--version --jsonincludes the CLI name, version, Node version, platform, and architecture. Doctor reports include the same local runtime identity.
See batch metadata refresh, explicit target selection, and runtime diagnostics for options, limits, and outcomes.
Install a prepared candidate
Requires Node.js 24 or newer. From the verified release source checkout, prepare and verify a new local bundle as described in the release process. For output directory release/v0.1.4:
npm install --global ./release/v0.1.4/agent-tcdh-0.1.4.tgz
agent-tcdh --version --jsonThe bundle contains the built CLI tarball, release.json, and SHA256SUMS, bound to the exact source commit. Preparation does not create a tag, publish a GitHub release, or publish to npm.
Published artifacts
Check npm availability before using the new version:
npm view agent-tcdh@0.1.4 versionAfter npm reports 0.1.4, install with npm install --global agent-tcdh@0.1.4 or run npx --yes agent-tcdh@0.1.4 --version --json. Existing hub configuration and registry storage can be reused.
Confirm that the GitHub v0.1.4 release exists before downloading its built tarball, manifest, and checksums. Verify the exact release bundle from the tagged source checkout. GitHub and npm publication are separate; publish the same verified tarball and verify its public registry integrity and latest tag afterwards. A configured workflow does not establish package-side npm trusted-publisher authorization.
Compatibility and verification scope
The minimum Node.js version remains 24, SQLite schema remains version 2, and portable snapshots remain format version 1. HTTP/MCP/A2A contracts and existing registrations are unchanged. No dependency changes or database migration are needed. Doctor JSON adds a top-level runtime object; existing status and exit semantics are preserved.
Batch refresh performs outbound metadata inspection in the CLI environment, including in preview mode. It does not execute tools/tasks or launch registered stdio commands. Unsupported transports/authentication are skipped; supported Bearer credentials come from each target's own environment reference. Hub credentials are not reused for providers. Selection defaults to at most 100 targets (maximum 1000), with concurrency 3 (maximum 8).
Selection and inspection are observations, not a transactional snapshot. Apply performs fresh lookups/inspection and is not bound to an earlier preview. Conditional writes are independent: failures do not roll back successful updates, and conflicts are not automatically retried. Review individual outcomes before retrying. Explicit groups validate completely before provider work, but registrations can still change later.
Version/runtime identity describes the local CLI process, not the remote hub or consuming agent. The declared version does not identify a Git revision or certify which unreleased changes a source checkout contains.
Local and native CI use isolated configuration files and local protocol fixtures. The matrix covers Linux x64, macOS ARM64/x64, Windows x64, and an independent Linux container. Package verification exercises explicit HTTP/stdio MCP diagnosis groups, remote MCP batch refresh and no-op preservation, configuration-independent installed version output, discovery protocols, persistence, and direct-call examples. The exact release bundle is separately verified before publication.
Earlier live provider and model evidence retains its original dates and scope. This release does not establish new model-driven executions for each supported client. External calls and real model runs remain opt-in. Consumers own target selection, credentials, protocol support, permissions, and execution.
AgentTCDH v0.1.3
AgentTCDH v0.1.3
GitHub and npm publication are complete. Install with npm install --global agent-tcdh@0.1.3 or run npx --yes agent-tcdh@0.1.3 --help.
Release source: 92d04d121e19c4f4fb3d4d4ec863fe6bf03d9811. Tarball SHA-256: 26e57f98547251049a7c3624703c405e07a07cbacd64c90b1065f67f0cb85c3d.
Publication verification checked npm version/latest, SHA-512 integrity, exact downloaded bytes against the GitHub tarball, execution from a fresh npm cache, and the installed backup-listing command. Native Linux, macOS ARM64/x64, Windows x64, and container CI passed; the Linux regression suite has 217 passing tests.
Version 0.1.3 adds local client connection checks, disconnection, backup discovery, and whole-file recovery. The commands work with the seven existing client profiles and preserve the discovery/direct-execution architecture.
Release preparation is separate from publication. Source metadata and candidate verification do not establish that npm or GitHub publication has completed. Confirm the requested destination before installing from it.
Included changes
connect CLIENT --check FILE: compare a saved named entry with this installation's generated profile. Report missing or differing settings without writes, network calls, or source values in output. Matches exit 0; missing/mismatched profiles exit 1.disconnect CLIENT --file FILE: preview named-entry removal. Explicit--applysaves an exact backup before replacement. Missing files/entries are successful no-ops. Codex managed blocks preserve surrounding text; other TOML layouts require an explicit--normalizechoice.config backups --file FILE: list matching sibling backup metadata by modification time, with a bounded scan, per-entry status, and installation-specific restore preview commands. Backup contents are not opened or validated during listing.config restore BACKUP_FILE --file FILE: preview whole-file recovery. Explicit--applyrestores the selected text and backs up an existing destination. Identical content is a no-op; a missing destination is created only on apply.
See connection checks, disconnection, backup discovery, and restoration for options, result codes, and scope.
Install a prepared candidate
Requires Node.js 24 or newer. From the verified release source checkout, prepare and verify a new local bundle as described in the release process. For output directory release/v0.1.3:
npm install --global ./release/v0.1.3/agent-tcdh-0.1.3.tgz
agent-tcdh --helpThe bundle contains the built CLI tarball, release.json, and SHA256SUMS, bound to the exact source commit. Preparation does not create a tag, publish a GitHub release, or publish to npm.
Published artifacts
Check npm availability before using the new version:
npm view agent-tcdh@0.1.3 versionAfter npm reports 0.1.3, install with npm install --global agent-tcdh@0.1.3 or run npx --yes agent-tcdh@0.1.3 --help. Existing hub configuration and registry storage can be reused.
Confirm that the GitHub v0.1.3 release exists before downloading its built tarball, manifest, and checksums. Verify the exact release bundle from the tagged source checkout. GitHub and npm publication are separate; publish the same verified tarball and verify its public registry integrity and latest tag afterwards. A configured workflow does not establish package-side npm trusted-publisher authorization.
Compatibility and verification scope
The minimum Node.js version remains 24, SQLite schema remains version 2, and portable snapshots remain format version 1. HTTP/MCP/A2A contracts and existing registrations are unchanged. No dependency changes or database migration are needed.
A connection check verifies generated settings, not client loading or successful authentication/execution. Disconnection selects the complete named entry, including custom settings, without inferring ownership. Restoration replaces the entire selected UTF-8 file, including unrelated settings, and does not validate backup provenance or client-specific syntax. Backup discovery uses names and filesystem metadata, not validated content or immutable creation history. Reload clients after applying configuration changes.
Local and native CI use isolated configuration files and local protocol fixtures. The matrix covers Linux x64, macOS ARM64/x64, Windows x64, and an independent Linux container. Package verification exercises configuration checks, disconnection, backup discovery, whole-file restoration, direct-call examples, and restart persistence. The exact release bundle is separately verified before publication.
Earlier live provider and model evidence retains its original dates and scope. This release does not establish new model-driven executions for each supported client. External calls and real model runs remain opt-in. The hub continues to return connection metadata; consumers own target selection, credentials, protocol support, permissions, and execution.
AgentTCDH v0.1.2
AgentTCDH v0.1.2
Available on npm as agent-tcdh@0.1.2, with latest pointing to 0.1.2.
npm install --global agent-tcdh@0.1.2
agent-tcdh init
agent-tcdh serveFor a hub without global installation, use npx --yes agent-tcdh@0.1.2 serve. Requires Node.js 24 or newer.
What is included
init: interactive or automated local/remote setup with reusable defaults and credential variable references.- Quick registration: inspect remote MCP/A2A metadata or record a stdio command without executing it.
connect: Codex, OpenCode v1/v2, Claude Code, Gemini CLI, Cursor, and VS Code profiles with preview, explicit file merging, and backups.registry import-configandpreset: offline-first conversion/selection and explicit atomic registration.doctoranddoctor --all: hub access, consumer prerequisites, metadata drift, bounded concurrency, and per-target versions.target edit,enable, anddisable: file-free management with conditional writes and idempotent no-ops.target remove --dry-runreviews a registration before guarded deletion.registry diffand import/preset--compare: read-only differences, retained registrations, and existing import-policy effects.
See guided setup, client connections, imports/presets, management, and comparison for examples.
Verified assets
GitHub and npm contain the same verified tarball bytes. Public registry integrity and a fresh-cache CLI installation were checked after publication.
- Source commit:
9ba05bf61abcc00b1cf7a3bfcf48e70a74b1594d. - Package SHA-256:
149d1c40c2fc17abdd3291cdff8f6934d1b7ef5c8b456322c6f8d3d119207e05. - Assets:
agent-tcdh-0.1.2.tgz,release.json, andSHA256SUMS. - Release workflow: all native-platform, container, and exact-artifact checks passed.
Compatibility and verification scope
The minimum Node.js version remains 24. SQLite schema version 2, portable snapshot format version 1, HTTP/MCP/A2A contracts, and existing registration data remain compatible. Original full-definition update and deletion commands retain their existing behavior. Invalid UTF-8 snapshot files are now rejected rather than silently replacing malformed bytes.
Native CI covers Linux x64, macOS ARM64/x64, and Windows x64 with regression and isolated production-package checks; independent container CI verifies the Linux runtime and persistence. Release preparation verifies the exact candidate tarball, its manifest/checksums, installed CLI, discovery protocols, management/comparison workflows, and restart persistence.
Client profiles are verified as generated configuration and actual bridge invocations through the MCP SDK. These checks do not establish new native model executions for every client. Earlier public-provider and real-agent evidence retains its original dates and scope; external calls and model runs remain opt-in.
The hub continues to supply metadata. Consumer-side protocol support, selection, credentials, permissions, and execution remain necessary. Registry comparisons are advisory paginated observations; actual imports retain their own conflict transaction and replacement semantics. Disabling a registration changes default discovery visibility and does not revoke provider permissions or cancel existing work.
AgentTCDH v0.1.1
AgentTCDH v0.1.1
This patch release prepares npm republication after account migration and updates repository metadata and documentation to jiind/agent-tcdh. MCP metadata, the A2A Agent Card, and OpenAPI advertise version 0.1.1. Runtime behavior and the discovery/direct-execution architecture are unchanged.
The previous npm package was withdrawn. npm does not allow reuse of a published package/version pair, so registry republication uses 0.1.1. Entire-package removal also imposes a 24-hour publication delay. GitHub releases remain independently installable. See the npm unpublish policy.
Install from GitHub
Requires Node.js 24 or newer. Install the built release tarball:
npm install --global https://github.com/jiind/agent-tcdh/releases/download/v0.1.1/agent-tcdh-0.1.1.tgz
agent-tcdh --help
agent-tcdh serveThe default hub URL is http://127.0.0.1:3000, and the default database is ~/.agent-tcdh/registry.sqlite. Configure authentication through shell environment variables as described in the reference.
npm publication
Version 0.1.1 is published to the npm registry. Use:
npx --yes agent-tcdh@0.1.1 --help
npx --yes agent-tcdh@0.1.1 serveVerification and compatibility
The release workflow runs native regression and isolated package checks on Linux x64, macOS ARM64/x64, and Windows x64, plus Linux container checks. It then installs and exercises the exact GitHub tarball before publication. External provider calls and real model runs remain opt-in.
SHA256SUMS covers the tarball and release.json; the manifest binds the artifact to its version, tag, source commit, and SHA-256. Download all three assets and check them with sha256sum --check SHA256SUMS on Linux, shasum -a 256 --check SHA256SUMS on macOS, or Get-FileHash -Algorithm SHA256 on PowerShell.
SQLite schema version 2 and portable snapshot format version 1 are unchanged. Existing registries and snapshots can be used with this patch release.
AgentTCDH v0.1.0
npm registry notice (2026-10-28):
agent-tcdh@0.1.0was withdrawn during account migration and cannot be republished at the same version. This GitHub tarball remains available. See v0.1.1 for the replacement package and its npm publication status.
AgentTCDH v0.1.0
Register MCP servers and A2A agents in one shared registry. Consumers discover capabilities and connection details through MCP, A2A, or HTTP, then call their selected targets directly.
This first release includes persistent registration management, CLI administration, remote metadata import/refresh/check, search and pagination, separate read/admin tokens, conditional updates, JSON backups, OpenAPI documentation, and a local three-target demo.
Install
Requires Node.js 24 or newer. The release includes a built, installable npm tarball; GitHub's automatic source archives require a build.
npm install --global https://github.com/jiind/agent-tcdh/releases/download/v0.1.0/agent-tcdh-0.1.0.tgz
agent-tcdh --help
agent-tcdh serveAfter the npm package is published, the equivalent registry commands are:
npx --yes agent-tcdh@0.1.0 --help
npx --yes agent-tcdh@0.1.0 serveThe default listener is http://127.0.0.1:3000; the default SQLite database is ~/.agent-tcdh/registry.sqlite. Configure shell environment variables for authentication and deployment as described in the reference.
Verification and assets
- Native regression and isolated production-package installation checks cover Linux x64, macOS ARM64/x64, and Windows x64. Linux container checks cover non-root execution, health, protocols, and persistence.
- Release automation reruns those checks for the tag, then installs and exercises the exact downloadable tarball.
SHA256SUMScovers the tarball andrelease.json. The manifest records version, tag, full source commit, and package SHA-256. Download all three assets and runsha256sum --check SHA256SUMSon Linux,shasum -a 256 --check SHA256SUMSon macOS, or compareGet-FileHash -Algorithm SHA256output on PowerShell.- Public MCP calls, actual agent selection, and Gemini/Jev adapter calls are recorded separately in the verification reports. They remain opt-in and are not run by release CI.
Scope
The hub discovers targets and returns metadata. Consumers own selection, MCP/A2A clients, credentials, and execution permissions. Dynamic native tool mounting depends on the client. This release does not proxy target calls or run an AI planner. Protocol compatibility does not guarantee support in every commercial agent.
The SQLite schema is version 2 and portable snapshot format is version 1. This is an initial 0.x release; future versions may change APIs. Export registrations before upgrading.