Context Circuit CLI 2.1.0

Context Circuit CLI 2.1.0

A workspace can now be published from, and install its CLI from, somewhere other
than the public repository.

Install from a chosen registry

The bundled installers accept --source github|gitlab with --repo and
--api (-Source, -Repo, -Api on Windows), or the environment variables
CONTEXT_CIRCUIT_SOURCE, CONTEXT_CIRCUIT_REPO and CONTEXT_CIRCUIT_API.
Passing none of them resolves the public GitHub release exactly as before.

A gitlab registry reads the release through the GitLab API and downloads each
asset from the generic package registry, authenticating with a personal or
project access token. It requires a token: unlike a public GitHub release there
is no anonymous download path to fall back to, so the installer says that
plainly instead of failing later against a 404.

Workspaces record the registry they came from

workspace.yaml accepts an optional cli_registry naming the source,
repository and api a workspace installs from:

cli_registry:
  source: gitlab
  repository: acme/context-circuit-source
  api: https://gitlab.example.com/api/v4

A publishing pipeline is told its own address by the forge running it, and that
knowledge reaches a developer's machine only if it is written down. The cc-cli
skill reads this key before installing and passes the three values through;
a workspace without the key installs from the default registry.

The key is validated when the workspace is read — an unknown source, a gitlab
source without an api, or an api the installer would refuse for not being
HTTPS are all reported rather than carried. Initialization preserves it: where
a workspace came from is not part of the seed data that initializing replaces.

---

Built at commit 6c0e801e964c271f40a2f1c5f6dcc35a5d565e4c.

Apache-2.0; the archive carries the license. The workspace template is 0BSD.