release: prepare Socket v10.0.1

CONTRIBUTING.md

@@ -65,13 +65,19 @@ A root change is ready for review when:
 
 ### Runtime Config
 
-The root superproject uses a small `uv` environment for maintainer tooling:
+The root superproject uses one `uv` environment for root and monorepo-owned
+child maintainer tooling:
 
 ```bash
 uv sync --dev
 ```
 
-If a root or child-repo workflow depends on Python quality tooling, declare that tooling in the relevant repo's `pyproject.toml` dev dependencies rather than assuming a machine-global install. Treat `pytest`, `ruff`, and `mypy` as the normal Python maintainer baseline when the repo's shipped validation surface uses them.
+Declare Python quality tooling in the root `pyproject.toml` dev dependencies
+rather than creating child environments or assuming a machine-global install.
+Treat `pytest`, `ruff`, and `mypy` as the normal Python maintainer baseline when
+the shipped validation surface uses them. Root validation redirects tool caches
+to `.codex/.cache/` and disables bytecode writes so checks do not recreate
+generated state inside plugin payloads.
 
 At the `socket` root, run `uv run mypy` without a path argument. The root mypy config intentionally checks root maintainer scripts, root tests, and package-shaped child maintainer code instead of crawling every standalone skill `scripts/` directory as one Python module namespace.
 
@@ -249,7 +255,10 @@ and final marketplace refresh. See
 for the complete contract. Do not invoke the internal Python modules or create
 a direct-main shortcut.
 
-If the changed surface also introduces or expands Python-backed repo checks, add the required tools to the repo-local `uv` dev group and document the corresponding `uv run pytest`, `uv run ruff check .`, and `uv run mypy` commands where that repo's contributors will actually look.
+If the changed surface also introduces or expands Python-backed repo checks,
+add the required tools to the root `uv` dev group and add the focused child
+command to `scripts/validate_socket.py` instead of creating a child
+`pyproject.toml`, lockfile, environment, or cache root.
 
 When editing docs, also review the rendered Markdown structure and cross-links for the files you changed.
 

README.md

@@ -169,7 +169,10 @@ Current Socket catalog shape:
 - `network-protocol-skills`: modern networking and application-protocol workflows for transport selection, HTTP/3 and QUIC planning, Media over QUIC draft-aware guidance, WebRTC signaling/media/data-channel work, and protocol diagnostics with stack-plugin handoffs
 - `professional-skills`: career and professional workflow guidance, starting with Dice job search and its bundled read-only remote MCP configuration
 - `python-skills`: Python runtime and tooling workflows, including local-first agent services, FastAPI and FastMCP service maintenance, and pytest-based testing; see the [Python skills expansion plan](./docs/maintainers/python-skills-plugin-plan.md) for maintainer details
-- `repository-skills`: routed Git and GitHub collaboration, README, CONTRIBUTING, AGENTS, API, ROADMAP, repository settings, protected-main release, and Codex GUI worktree workflow guidance; its portable repository and documentation workflows are available from the Hermes skill tap
+- `repository-skills`: routed Git and GitHub collaboration, README,
+  CONTRIBUTING, AGENTS, ROADMAP, repository settings, protected-main release,
+  and Codex GUI worktree workflow guidance; its portable repository and
+  documentation workflows are available from the Hermes skill tap
 - `reverse-engineering-skills`: artifact triage, preservation, exact-build comparison, decompiler review, Apple Mach-O/runtime/signing/Apple Silicon/dyld/dynamic/kernel research, Cutter/Rizin, Malimite, Ghidra, Hopper, .NET, Unity and IL2CPP, and reproducible security evidence workflows
 - `server-side-jvm`: server-side JVM, Java, Scala, Google ADK agent-service, Gradle, Maven, SBT, and testing workflow guidance, with future Clojure support planned
 - `server-side-swift`: canonical-workspace service components, Vapor, Leaf-rendered websites and HTML email, Hummingbird, persistence, OpenAPI/RPC, SwiftNIO, observability, auth, app sync, Soto-first AWS integration, native macOS/Homebrew local development, and GitHub-only OCI/Fly.io deployment guidance plus the source-bundled `server-swift-steward` custom-agent definition

ROADMAP.md

@@ -1190,7 +1190,9 @@ and test/production deployments for GitHub Actions.
 - [x] Add `game-dev-skills:game-porting-toolkit-workflow` to choose stable GPTK 3 evaluation/shader-conversion work or beta-sensitive GPTK 4 source-port work, then load Apple’s upstream GPTK 4 skills instead of duplicating their corpus.
 - [x] Add `game-dev-skills:metalfx-game-rendering-workflow`, `metal-asset-streaming-workflow`, and `metal-neural-rendering-workflow` for native MetalFX integration, GPU asset residency/streaming, and carefully gated experimental neural rendering.
 - [x] Overhaul `agent-portability-skills` so its docs, tests, generated bootstrap content, and sync audit logic target Codex/OpenAI plus the open `.agents/skills` discovery mirror only. Remove stale expectations for retired child maintainer docs such as reality-audit and install-surface docs, and keep the wording away from unsupported non-Codex or generic multi-agent surfaces.
-- [x] Consolidate README, CONTRIBUTING, AGENTS, API, coordinated docs, and ROADMAP maintenance workflows into `repository-skills` so repository operations and repository documentation have one owner.
+- [x] Consolidate README, CONTRIBUTING, AGENTS, coordinated docs, and ROADMAP
+  maintenance workflows into `repository-skills` so repository operations and
+  repository documentation have one owner.
 - [x] Add a first `agent-engineering-skills:design-agent-automation-workflow` planning skill for agent and automation design. It chooses between Codex app automations, `codex exec`, Codex subagents, OpenAI Agents SDK services, LangGraph graphs, Hermes-specific workflows, or no automation yet while delegating stack-specific implementation to the owning plugin.
 - [x] Added `agent-engineering-skills:design-agent-eval-workflow` for agent, skill, prompt, and automation eval planning, and skewed automation guidance toward safe full automation with exact escalation gates instead of broad human review.
 - [x] Replaced the legacy Apple app guidance and sync routes with the unified `bootstrap-xcode-workspace` workflow and its managed `just align` contract.
@@ -1286,7 +1288,9 @@ and test/production deployments for GitHub Actions.
 - Loosened coordinated Codex subagent guidance so skills preserve OpenAI's explicit-trigger model while allowing narrower workflow guidance, such as Codex Security repository-wide scans, to ask for and use subagents when the task depends on parallel file-pass review.
 - Added coordinated Codex subagent guidance across `agent-portability-skills` and `agent-engineering-skills`, grounding skill wording in OpenAI's current explicit-trigger `subagents` model while keeping the root docs clear about why the pass belongs in `socket`.
 - Added `repository-skills:codex-gui-worktree-workflow` as the general Codex GUI worktree-first planning surface, while keeping SwiftPM, Xcode, Vapor, Hummingbird, and server-side Swift local environment templates inside their stack-specific plugins.
-- Prepared the `v6.1.0` minor release by adding the `maintain-project-api` productivity skill and keeping the monorepo-owned child docs, tests, and shared version surfaces aligned.
+- Prepared the `v6.1.0` minor release by expanding repository documentation
+  maintenance and keeping the monorepo-owned child docs, tests, and shared
+  version surfaces aligned.
 - Added explicit `standard` and `subtrees` release-mode guidance, including the pull-only `SpeakSwiftlyServer` rule for `socket` subtree sync.
 - Published `apple-dev-skills` `v6.0.11` after adding direct regression coverage for SwiftPM-generated `.swiftpm/xcode/package.xcworkspace` classification and synced the released child state back into `socket`.
 - Prepared the shared `v6.0.11` patch release after fixing `repository-skills:maintain-project-repo` release-helper regressions for initial PR check discovery and approval-only review handling.

docs/maintainers/automation-suitability.md

@@ -152,7 +152,6 @@ as the default Socket maintainer automation runtime.
 | --- | --- | --- |
 | `explain-code-slice` | Codex app automation, subagent read phase, or code-owned read phase | It is read-only and explanation-focused. Good for batch reports, but it should not mutate repos. |
 | `maintain-project-agents` | `codex exec` for one repo; code-owned service for policy rollout | It changes durable agent instructions, so apply mode should be branch-and-PR gated. App automation is good for drift reports. |
-| `maintain-project-api` | `codex exec` for one repo; subagents for read-heavy evidence; code-owned service for API-doc inventory | It must avoid invented endpoints and credentials. Best run with repo-grounded evidence and PR review. |
 | `maintain-project-contributing` | `codex exec` for one repo; code-owned service for standardization campaigns | It owns contributor workflow. Good candidate for automated apply after check-only evidence. |
 | `maintain-project-readme` | `codex exec` for one repo; code-owned service for product-doc sweep | It keeps README product-focused and hands contributor details to `CONTRIBUTING.md`, which makes it safer for repeated repo-wide application. |
 | `maintain-project-repo` | `codex exec` first; code-owned service for coordinated rollout | It installs managed scripts and CI wrappers. It is deterministic, but the write surface is broad enough that every repo should get a PR. |