Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions DOCUMENTATION_INDEX.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Documentation Index — mcp-warden

Last Updated: 2026-10-22
Last Updated: 2026-11-06

Master index of every document in this repository. The `docs/` files are the
**security contract and source of truth** for all algorithms; the three core docs
Expand All @@ -12,7 +12,7 @@ describe and visualize the implementation that satisfies that contract.

| # | Doc | Purpose |
|---|-----|---------|
| 1 | [`README.md`](README.md) | Project overview, install, the pin/check CI demo (full walkthrough archived to [`docs/PIN_CHECK_DEMO.md`](docs/PIN_CHECK_DEMO.md) to hold the 500-line core-doc limit), CLI reference (incl. v0.3 `lock rotate`, DSE-1530 `lock sign`, DSE-1539 `--max-pages` + redacted offline `diff` viewer), GitHub Action usage section (Issue #18), **pre-commit hook section (Issue #22)** |
| 1 | [`README.md`](README.md) | Project overview, install, the pin/check CI demo (full walkthrough in [`docs/PIN_CHECK_DEMO.md`](docs/PIN_CHECK_DEMO.md)), CLI reference (incl. v0.3 `lock rotate`, DSE-1530 `lock sign`, DSE-1539 `--max-pages` + redacted offline `diff` viewer), GitHub Action usage section (Issue #18), **pre-commit hook section (Issue #22)** |
| 2 | [`SYSTEM_CONTEXT_DIAGRAM.md`](SYSTEM_CONTEXT_DIAGRAM.md) | System context + pin/check sequence (mermaid); trust boundary; `conclave` as dev-time reviewer only; composite GitHub Action + **pre-commit hook** as consumer delivery vehicles |
| 3 | [`DOCUMENTATION_INDEX.md`](DOCUMENTATION_INDEX.md) | This file |

Expand Down Expand Up @@ -306,3 +306,9 @@ review/signature CLI. Tests are `tests/test_artifact_trust.py`,
| `tests/fixtures/poison_server.py` | **(v0.2)** result-poisoning fixture server (ANSI/secret-echo/exfil/inject/clean tools) |
| `tests/fixtures/crash_server.py` · `listchange_server.py` · `clean_listchange.warden.lock` | **(v0.3)** raw-stdio lifecycle fixtures: crash-mid-call (`-32002`) and `tools/list_changed` rug-pull + its pinned clean lock |
| `tests/fixtures/fault_guard_launcher.py` | **(#21)** test-only launcher that monkeypatches ONE inspection function (`inspect_result` / `evaluate_call` / `diverges_from_lock` / `_hash_live_tools`) to raise inside the spawned guard child, then runs the real CLI — drives the `--strict` terminate-site tests without any test branch in production code; `FAULT_SECRET` plants a secret for the redaction test |

## Version history

| Date | Change |
|------|--------|
| 2026-11-06 | Recorded TheDataExperts PyPI ownership, Active organization billing, normal company publisher and removal of the obsolete personal publisher; linked successful authentication-only run 42224199909. Account-wide token revoked; project-only manual fallback retained. No upload today; 2.2.0 unchanged and next normal release upload/provenance proof outstanding. |
7 changes: 6 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# mcp-warden

Last Updated: 2026-10-22
Last Updated: 2026-11-06

[![CI](https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/workflows/integrity-gate.yml/badge.svg)](https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/workflows/integrity-gate.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
Expand All @@ -19,6 +19,11 @@ Older locks stay readable, but require review and re-pinning for this coverage.
Hints are server claims, not proof of safety, and schemas do not certify content. Release
operators can check production OIDC without uploading via [`RELEASING.md`](RELEASING.md).

`mcp-warden-cli` is owned by the [TheDataExperts PyPI organization](https://pypi.org/org/TheDataExperts/).
The company-repository publisher passed an authentication-only check on 2026-11-06;
no package was uploaded and PyPI remains at 2.2.0. The next normal release must
still prove OIDC upload and provenance; see the [publishing status](RELEASING.md#ownership-and-publishing-status--2026-11-06).

The proposed next direction is a protocol-neutral **Warden**: human-approved tool versions and bounded actions, with untrusted inputs kept separate from authority.
The [upgrade plan and checkpoint proposal](docs/plans/2026-10-02-tool-integrity-upgrade.md)
maps prompts, retrieval, code execution, and serverless adapters to existing Agent
Expand Down
38 changes: 27 additions & 11 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,28 @@ The workflow uses **OIDC Trusted Publishing**, without a stored GitHub upload to
The repo variable `PYPI_TRUSTED_PUBLISHER=true` permits an attempt; it does not prove
that a matching PyPI publisher exists. Verify the exchange before cutting a new release.

### Ownership and publishing status — 2026-11-06

Both `conclave-cli` and `mcp-warden-cli` now belong to the
[TheDataExperts PyPI organization](https://pypi.org/org/TheDataExperts/),
transferred from `z3usalmighte` direct ownership. Organization billing is Active;
Ernest (`z3usalmighte`) remains its sole human owner. Both projects have a normal
Trusted Publisher for their respective `DataScience-EngineeringExperts` repository,
`release.yml`, with a blank environment matching the workflows. No pending
publishers remain in the inspected account.

The company-repository publisher was registered before the obsolete
`ernestprovo23` publisher was removed. [Verification run 42224199909](https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/42224199909)
succeeded at `42e08c505eb28f82b01d3fa81a7696c56f6e6383`: PyPI accepted the OIDC
exchange; build, signing and upload jobs were skipped. This establishes authentication,
not project upload permission or successful release publication.

The account-wide upload token was revoked. A `mcp-warden-cli`-only manual fallback
is retained pending the next normal release's successful OIDC upload and provenance
verification. It is not a workflow fallback. No upload or release was performed on
2026-11-06; the published version remains **2.2.0**. Keep the next-release proof
outstanding until section 2 confirms the new version and attestations.

### New projects only — pending publisher

1. Log in to <https://pypi.org> as the account that will own `mcp-warden-cli`.
Expand Down Expand Up @@ -160,17 +182,11 @@ The same exchange error occurred on the prior 1.2.0 release. The authorized manu
[PyPI 2.0.0](https://pypi.org/project/mcp-warden-cli/2.0.0/). That recovery proves
publication, not that OIDC automation was repaired.

After the publisher is aligned and authentication succeeds, rerun only the failed
job from the original release run, using its retained build artifacts:

```bash
gh run rerun 36960647544 --failed
```

Do not rebuild/re-sign/replace the released assets as a repair attempt. If the
original artifacts expired, stop and plan a fix-forward release. Success means
OIDC authentication passes and the existing immutable files are handled by
`skip-existing`; verify the public wheel/sdist hashes remain unchanged.
The 2026-11-06 authentication-only check above supersedes the earlier unknown
publisher-alignment status. The old 2.0.0 run is historical evidence, not the next
verification target. Do not rebuild, re-sign, re-upload or rerun that release as
part of this closeout. Prove end-to-end OIDC upload on the next normal release,
then verify its new PyPI files and provenance under section 2.

### (Optional) TestPyPI dry-run publisher

Expand Down
8 changes: 6 additions & 2 deletions SYSTEM_CONTEXT_DIAGRAM.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# mcp-warden — System Context Diagram

Last Updated: 2026-10-22
Last Updated: 2026-11-06

**CLI 2.0.0 / schema level 4** extends capture/lock/check to complete tool annotations and output
schemas, with structural output drift and Python/TypeScript parity. The existing
Expand Down Expand Up @@ -101,7 +101,11 @@ logic) plus a separate informational provenance section. It never prints raw
> Minting can change PyPI pending-publisher records; it is not universally read-only.
> Successful exchange is not proof of project upload permission. CLI 2.0.0's
> failed OIDC exchange was recovered with an authorized manual upload of the signed bytes;
> publisher alignment must be verified independently. See [`RELEASING.md`](RELEASING.md).
> the company-repository publisher subsequently passed the 2026-11-06
> authentication-only check ([run 42224199909](https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/42224199909)).
> `mcp-warden-cli` now belongs to the [TheDataExperts PyPI organization](https://pypi.org/org/TheDataExperts/).
> No upload occurred; PyPI remains at 2.2.0. End-to-end OIDC upload and provenance
> still need proof on the next normal release. See [`RELEASING.md`](RELEASING.md).

---

Expand Down
Loading