- CONN-CADDY-MCP2
- CONN-CADDY-MCP-CONNECTOR-CONTENT2
- CONN-CADDY-MCP-SDK-CENTRALIZATION3
- Requirementsall slices in all specs7
- Requirements not donenot VERIFIED6
- Specs not donewhole specs only3
Each spec shows its requirement count. Panel J lists every record.
Requirements (7)
Specs (3)
Each bar shows one state against all records of the same kind.
Percentages count current rows. Done means VERIFIED.
| State | Definition |
|---|---|
| SPECIFIED | The requirement is written. No code for it is on the default branch. |
| LANDED | A commit that carries its ID in a Spec trailer is on the default branch. |
| VERIFIED | It is LANDED and a test bound to its ID exists. |
A spec state is the lowest state of its rows. Done means VERIFIED.
Invalid state: 0
| Spec / title | Req. | Landed | Done | Spec state | Code references |
|---|---|---|---|---|---|
| CONN-CADDY-MCPCONN-CADDY-MCP — Connector identity and release metadata | 2 | 2/2 | 0 | LANDED | spec.md documentation: file exists; coverage not verified `requirements.md` documentation: file exists; coverage not verified `status.json` implementation: file exists; coverage not verified plan.md documentation: file exists; coverage not verified test-spec.md documentation: file exists; coverage not verified tests/test_config_confirm.py test: file exists; coverage not verified |
| CONN-CADDY-MCP-CONNECTOR-CONTENTCONN-CADDY-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | 2 | 1/2 | 0 | SPECIFIED | spec.md documentation: file exists; coverage not verified plan.md documentation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified test-spec.md documentation: file exists; coverage not verified |
| CONN-CADDY-MCP-SDK-CENTRALIZATIONCONN-CADDY-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in caddy-mcp | 3 | 1/3 | 1 | SPECIFIED | caddy_mcp/api/api_client_base.py implementation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified `requirements.md` documentation: file exists; coverage not verified `status.json` implementation: file exists; coverage not verified plan.md documentation: file exists; coverage not verified test-spec.md documentation: file exists; coverage not verified |
Landed counts LANDED and VERIFIED requirements. Done counts VERIFIED requirements only.
The spec state comes from the spec status file only.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/caddy-mcp / Unassigned (3)
CONN-CADDY-MCP: no plan diagram declared.
CONN-CADDY-MCP-CONNECTOR-CONTENT: no plan diagram declared.
CONN-CADDY-MCP-SDK-CENTRALIZATION: no plan diagram declared.
Depends on means a declared prerequisite. Extends and references do not imply prerequisite order. Shared code never creates dependencies. External targets are source declarations, not verified delivery.
Knuckles-Team/caddy-mcp / Unassigned
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-CADDY-MCP | No relationships declared; dependencies unknown | ||
| CONN-CADDY-MCP-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
| CONN-CADDY-MCP-SDK-CENTRALIZATION | No relationships declared; dependencies unknown | ||
Issues
0 open at capture.
Pull Requests
0 open at capture.
The build reads GitHub one time. This page makes no live API requests.
Each status file gives one spec row. Each requirement gives one more row. A record without a valid state shows INVALID. Expand a Definition to read the canonical requirement and verification text.
All documented records (10 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-CADDY-MCP CONN-CADDY-MCP — Connector identity and release metadata | spec | None | LANDED | No recorded commit/test evidence |
| CONN-CADDY-MCP-R001 Connector reports its released version Definition — CONN-CADDY-MCP / CONN-CADDY-MCP — Connector identity and release metadataCanonical requirement and verification source**Connector reports its released version.** `caddy_mcp.__version__` equals the released `pyproject.toml` version and the bump configuration updates both. Caller chain: the `caddy-mcp` console script (pyproject.toml, scion_sdk.cli:serve) loads `caddy_mcp:connector` (caddy_mcp/__init__.py) whose Api is caddy_mcp/api_client.py::Api, and `__version__ = _v("caddy-mcp")` at caddy_mcp/api_client.py:8 reads the installed package metadata; tests/test_version.py does not exist yet (planned). Shape: caddy_mcp/api_client.py::__version__ already comes from importlib.metadata.version("caddy-mcp"), so it follows the pyproject.toml version of 2.3.9 with no second copy; the planned tests/test_version.py compares the two and no bump configuration exists to update. | `tests/test_version.py::test_reported_version_matches_the_released_package` | requirement | CONN-CADDY-MCP | LANDED | 0e1ad813a056 43792d34c369 ae0b9aab5f7d |
| CONN-CADDY-MCP-R002 Live-config writes require confirmation Definition — CONN-CADDY-MCP / CONN-CADDY-MCP — Connector identity and release metadataCanonical requirement and verification source**Live-config writes require confirmation.** `caddy_load_config`, `caddy_put_config`, `caddy_patch_config`, `caddy_put_id`, `caddy_patch_id`, `caddy_post_id`, `caddy_post_config` and its alias `caddy_set_config` change the live proxy config, so each is a destructive tool that takes a `confirm` parameter, like `caddy_stop_server`. Caller chain: the `caddy-mcp` console script serves `caddy_mcp:connector`, whose Api methods `load_config`, `put_config`, `patch_config`, `put_id`, `patch_id`, `post_id`, `post_config` and `set_config` in caddy_mcp/api/api_client_config.py carry `__http_method__ = "DELETE"`, so the SDK tool surface adds `confirm` and the destructive hint. Shape: with an elicitation-capable client the call asks for confirmation; with a stdio, no-auth or non-eliciting client a call without `confirm=true` returns the typed refusal `{cancelled: true, operation, reason}` whose reason says to repeat the call with confirm=true, never hangs and never reaches Caddy; a call with `confirm=true` runs on stdio and on HTTP. | `tests/test_config_confirm.py::test_stdio_no_auth_refuses_without_confirm_and_never_calls_caddy`, `tests/test_config_confirm.py::test_stdio_no_auth_succeeds_with_confirm_true`, `tests/test_config_confirm.py::test_http_refuses_without_confirm_then_succeeds_with_it` | requirement | CONN-CADDY-MCP | LANDED | 4084a0d47d11 5ad05abeeb59 |
| CONN-CADDY-MCP-CONNECTOR-CONTENT CONN-CADDY-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-CADDY-MCP-CONNECTOR-CONTENT-R001 Default content Definition — CONN-CADDY-MCP-CONNECTOR-CONTENT / CONN-CADDY-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `caddy-mcp` as the single `scion_sdk.connector` entry point. The server lists the packaged `skill://` and `ontology://` resources and the packaged prompts with no `content=` argument. Proving test: `tests/test_default_content_surfaces.py`. Caller chain: the `caddy-mcp` console script (pyproject.toml, scion_sdk.cli:serve) loads the `scion_sdk.connector` entry point `caddy_mcp:connector` -> caddy_mcp/__init__.py::connector (Connector with no content= argument) -> the SDK default content registration serves skill://, ontology:// and prompts. Shape: new tests/test_default_content_surfaces.py builds the server from caddy_mcp.connector and lists resources and prompts, over the packaged caddy_mcp/skills, caddy_mcp/ontology and caddy_mcp/prompts. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. Planned test: `tests/test_default_content_surfaces.py::test_default_content_surfaces_list_skills_ontology_prompts`. | requirement | CONN-CADDY-MCP-CONNECTOR-CONTENT | LANDED | 62ce16ce8227 df6f7272b8dd |
| CONN-CADDY-MCP-CONNECTOR-CONTENT-R002 Declare access contracts for the competency reads of caddy-mcp Definition — CONN-CADDY-MCP-CONNECTOR-CONTENT / CONN-CADDY-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Declare access contracts for the competency reads of caddy-mcp.** Subsystem: connector `caddy-mcp`. Caller: the connector's existing read tool, called by arbora through `fleet.call`. Declare in `caddy_mcp/ontology/access_contracts.ttl` one `ac:AccessContract` per entity. Entities: entity `route` (class infra:ProxyRoute, key `id`, columns routeHostname, upstreamAddress). Each row sets `ac:classIri`, `ac:sourceId`, `ac:entity`, `ac:keyField`, `ac:accessKind` `mcp_tool`, `ac:operation` (the existing tool name) and `ac:pagination`. Column names equal the ontology property local names. Follow the access contracts file of the container-manager-mcp connector (`access_contracts.ttl` under its `ontology` directory). Save one recorded response per entity in `tests/recordings/<entity>.json`. Medulla copies these into its competency fixtures. The consumer is the medulla table row MEDULLA-CQ-CONN-R086. Caller chain: arbora fleet.call -> the registered `caddy_mcp_reverse_proxy` tool (caddy_mcp/mcp/mcp_config.py::register_config_tools:54, action get_reverse_proxy_upstreams) -> caddy_mcp/api/api_client_config.py::Api.get_reverse_proxy_upstreams; caddy_mcp/ontology/access_contracts.ttl is planned and does not exist yet. Shape: new caddy_mcp/ontology/access_contracts.ttl with one ac:AccessContract for entity route over the ontology in caddy_mcp/ontology/caddy.ttl, recordings in tests/recordings/route.json, and the certification helper used by the container_manager_mcp access contracts test. | Test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified` (L2) runs the connector ontology certification and validates each recording against its contract. | requirement | CONN-CADDY-MCP-CONNECTOR-CONTENT | SPECIFIED | No recorded commit/test evidence |
| CONN-CADDY-MCP-SDK-CENTRALIZATION CONN-CADDY-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in caddy-mcp | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-CADDY-MCP-SDK-CENTRALIZATION-R001 Requests use the governed SDK client Definition — CONN-CADDY-MCP-SDK-CENTRALIZATION / CONN-CADDY-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in caddy-mcpCanonical requirement and verification source**Requests use the governed SDK client.** caddy-mcp must send every vendor request through the SDK governed HTTP client with its resolved TLS profile and SDK auth. It must not build its own session. This row follows `SCION-CENTRALIZED-CAPABILITIES-R001`, `SCION-CENTRALIZED-CAPABILITIES-R003`, `SCION-CENTRALIZED-CAPABILITIES-R008`. Caller chain: arbora fleet.call -> `caddy_mcp_config` or `caddy_mcp_reverse_proxy` tool (caddy_mcp/mcp/mcp_config.py:60) -> caddy_mcp/auth.py::get_client -> caddy_mcp/api_client.py::Api -> caddy_mcp/api/api_client_base.py::ApiClientBase.request. Shape: ApiClientBase.__init__ in caddy_mcp/api/api_client_base.py builds the session with scion_sdk.http.client.create_http_client, HttpClientOptions, resolve_tls_profile("caddy") and scion_sdk.auth.static.BearerAuth or httpx.BasicAuth. | A unit test shows the API client holds an httpx client and a request carries the configured credential through a mock transport Test: `tests/test_sdk_centralization.py::test_request_goes_through_the_governed_client`. | requirement | CONN-CADDY-MCP-SDK-CENTRALIZATION | VERIFIED | 0e1ad813a056 tests/test_sdk_centralization.py:27 |
| CONN-CADDY-MCP-SDK-CENTRALIZATION-R002 SDK floor and dependency set Definition — CONN-CADDY-MCP-SDK-CENTRALIZATION / CONN-CADDY-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in caddy-mcpCanonical requirement and verification source**SDK floor and dependency set.** The package must require the current scion-sdk floor and must not pin requests or httpx while nothing imports them directly. Optional drivers come from SDK extras. This row follows `SCION-CENTRALIZED-CAPABILITIES-R040`, `SCION-CENTRALIZED-CAPABILITIES-R001`. Caller chain: dependency resolution of pyproject.toml (dependencies = scion-sdk[mcp]) for the `caddy-mcp` console script and the `caddy_mcp:connector` entry point; no runtime code path. Shape: pyproject.toml dependencies hold only scion-sdk[mcp] with the current floor and no requests or httpx pin; caddy_mcp imports httpx only through the SDK client types, and tests read the dependency list with tomllib. | pyproject.toml shows the floor and no unused requests pin Test: `tests/test_sdk_centralization.py::test_dependencies_have_no_unused_requests_pin`. | requirement | CONN-CADDY-MCP-SDK-CENTRALIZATION | SPECIFIED | tests/test_sdk_centralization.py:58 |
| CONN-CADDY-MCP-SDK-CENTRALIZATION-R003 Production wiring and hot path Definition — CONN-CADDY-MCP-SDK-CENTRALIZATION / CONN-CADDY-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in caddy-mcpCanonical requirement and verification source**Production wiring and hot path.** `ApiClientBase.__init__` in `caddy_mcp/api/api_client_base.py` calls `create_http_client`, and every domain client reaches it through `request`. A transient 503 is retried by the SDK policy. This row follows `SCION-CENTRALIZED-CAPABILITIES-R001`, `SCION-CENTRALIZED-CAPABILITIES-R003`, `SCION-CENTRALIZED-CAPABILITIES-R008`. Caller chain: arbora fleet.call -> `caddy_mcp_config` tool (caddy_mcp/mcp/mcp_config.py:60) -> caddy_mcp/api/api_client_config.py::Api methods -> caddy_mcp/api/api_client_base.py::ApiClientBase.request -> self._session built by create_http_client in __init__. Shape: ApiClientBase.__init__ calls create_http_client and request() calls self._session.request, so the SDK retry policy handles a 503; reuse the _client helper with httpx.MockTransport in tests/test_sdk_centralization.py. | A test builds the client with a mock transport, sees a 503 then a 200, and gets one result Test: `tests/test_sdk_centralization.py::test_transient_status_is_retried_by_the_sdk_client`. | requirement | CONN-CADDY-MCP-SDK-CENTRALIZATION | SPECIFIED | tests/test_sdk_centralization.py:27 tests/test_sdk_centralization.py:43 |