Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / temporal-agent-harness

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observed

The nexus-mcp extra cannot resolve from public PyPI alone as observed. Nothing changed in the window; this is newly verified prior posture. The unqualified temporal-nexus-mcp requirement is in wheel metadata since 0.3.0 (originally with a Python >=3.13 marker). The project comments describe checkout-only workspace resolution; the local path source does not travel in built metadata. Public PyPI JSON and simple endpoints returned 404 in the recorded checks. The extra cannot resolve from public PyPI alone as observed. Its unqualified requirement would trust whatever compatible distribution a configured index supplies, if one became available. No malicious publication or dependency-confusion attack was observed. A 404 does not establish whether the name is owned, reserved, blocked or available. The example uses uv sync --extra nexus-mcp from a checkout where the workspace points at its local package.

Channel: preview-or-beta (published wheel metadata). Half: defect. Date: 2026-10-03 (verified at 0.6.0; present since 0.3.0, 2026-09-11).

Operator consequence: Use the documented checkout/workspace path for Nexus MCP, or verify a trusted private index explicitly. Do not expect a public-PyPI-only install of the extra to resolve. Inspect the source and hash of any temporal-nexus-mcp resolution in your lock. Removal of the extra from public metadata or an authenticated project distribution would settle the packaging gap.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observed

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Temporal Agent Harness
    tagged commit file2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedtemporal-community/temporal-agent-harness / pyproject.toml#L91-L108tagged commit file2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedtemporal-community/temporal-agent-harness / nexus/mcp/pyproject.toml#L1-L9tagged commit file2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedtemporal-community/temporal-agent-harness / examples/nexus_hello/README.md#L197-L200package registry2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedpypi.org/project/temporal-agent-harness/0.6.0/commit2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedgithub.com/temporal-community/temporal-agent-harness/commit/d2e7abc74d28d2248f8659cf577b438a96706ee4package registry2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedpypi.org/pypi/temporal-nexus-mcp/jsonpackage registry2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observedpypi.org/simple/temporal-nexus-mcp/

Versioned source: run artifact