bot-bottle

Author	SHA1	Message	Date
didericis-claude	8f6148d571	docs(orchestrator): tighten auth-provisioning wording to concrete services test / integration-docker (pull_request) Successful in 18s Details tracker-policy-pr / check-pr (pull_request) Successful in 21s Details test / integration-firecracker (pull_request) Successful in 3m51s Details test / unit (pull_request) Failing after 11m53s Details test / coverage (pull_request) Has been skipped Details test / publish-infra (pull_request) Has been skipped Details Address review on #482: drop the generic "credential boundary" framing in the PRD and docstrings and talk about the specific services — the orchestrator holds the control-plane key; the host controller (#468) gets a separate key the orchestrator never holds, so the orchestrator can't mint the credentials it uses to talk to the host controller that owns its lifecycle. Lead with that concrete win. No code behaviour change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-26 01:32:53 +00:00
didericis-claude	45f3cefbc5	refactor(orchestrator): uniform control-plane auth provisioning per trust domain Hoist control-plane auth provisioning out of the per-backend launchers into one shared contract, parameterized per trust domain (#476). Every blocking finding in PR #471 was the same integration-bug class: each launcher re-derived, by hand, how to generate the signing key, scope it to the orchestrator, mint the gateway JWT, and keep the host key canonical. Introduces `trust_domain.py`: * `TrustDomain` — one credential boundary (host-canonical key file + role set + env vars). `mint`/`verify` are scoped to the domain's roles, so a future host-controller domain (#468) uses its own key/verifier/roles rather than a `host` role on the control plane's frozenset (which the orchestrator key could then forge). * `ControlPlaneProvisioning` — the single seam answering the four invariants: host-canonical key, split key-vs-token credential, CLI token valid across co-running backends, and fail-closed (no open mode) for any co-located topology. * `Topology` — the backend declares what it is; the default is co-located + fail-closed, so a backend need not redeclare it. The `Orchestrator` ABC gets `control_plane_key()` (fail-closed) and routes `mint_gateway_token()` through the contract; docker/macOS/firecracker orchestrators, the server (verify), and the host CLI client (mint cli) all go through the domain instead of reading the host key directly. `orchestrator_auth` gains an optional `roles=` arg (default unchanged) so a domain scopes its own role set; `paths.host_signing_key(filename)` generalizes host_orchestrator_token. Adds unit coverage for the domain boundary + provisioning invariants and a PRD capturing the durable rationale. No change to the auth primitive's HMAC, the plane split, or the server's documented open-mode fallback. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Closes #476	2026-07-26 01:32:53 +00:00
Quality Badge Bot	0e70d26af4	chore: update quality badges - Coverage: 83% - Core coverage: 94% [skip ci]	2026-07-25 23:45:18 +00:00
didericis-codex	f2d8158742	Merge pull request 'fix(supervise): get bot-bottle.db off the data plane (supervise + egress proposals over RPC)' (#471 ) from fix/db-off-data-plane-469 into main test / integration-docker (push) Successful in 35s Details test / unit (push) Successful in 49s Details Update Quality Badges / update-badges (push) Successful in 50s Details lint / lint (push) Successful in 57s Details test / integration-firecracker (push) Successful in 5m10s Details test / coverage (push) Successful in 16s Details test / publish-infra (push) Successful in 2m18s Details	2026-07-25 19:44:20 -04:00

1 changed files with 1 additions and 1 deletions

									
										README.md
									
		+1
		-1
	
												View File
												
				@@ -5,7 +5,7 @@

				# bot-bottle

				[![test](https://gitea.dideric.is/didericis/bot-bottle/actions/workflows/test.yml/badge.svg?branch=main)](https://gitea.dideric.is/didericis/bot-bottle/actions?workflow=test.yml)

				[![coverage](https://img.shields.io/badge/coverage-84%25-brightgreen)](https://coverage.readthedocs.io/)

				[![coverage](https://img.shields.io/badge/coverage-83%25-brightgreen)](https://coverage.readthedocs.io/)

				[![core coverage](https://img.shields.io/badge/core%20coverage-94%25-brightgreen)](https://gitea.dideric.is/didericis/bot-bottle/src/branch/main/docs/decisions/0004-coverage-policy.md)

				**Problem:** Developer wants to run a coding agent without supervision, but they don't want a prompt injected or misbehaving agent wrecking their environment or exfiltrating sensitive data.

Compare commits

4 Commits

784e49239d .. 8f6148d571

Compare commits

4 Commits 784e49239d .. 8f6148d571

4 Commits

784e49239d .. 8f6148d571