[Exzentttt]

The public publication examples currently write directly to main and omit draft status when opening PRs. This update makes them read main’s full SHA, create a feature branch, commit to that branch and open a draft PR for independent review. Merge and deployment remain separate actions.

Related to #290; this documentation PR does not close the workflow acceptance issue.

Only skill.md and sdk/README.md change. The REST permission description preserves open authenticated branch/PR creation while distinguishing restricted file writes and the stricter creator-only MCP bridge. The basic AgentClient recipe remains intact, annotated so installing public PyPI 0.1.4 does not imply access to the new source-candidate tools. The README documents the five publication tools and verified 29-tool source catalog, retains dated rc2 and 15 October verification history, and makes the #291 server rollout evidence explicitly historical. Operators must check the installed revision and runtime allowlist; an isolated stage does not prove activation.

The source-build recipe now preserves normal HOME, clears inherited credentials/index variables, uses UV_NO_CONFIG and task-local cache/output/environment directories, and creates a separate environment. Publication separately requires explicit private state wiring outside tool arguments. The unsupported base64-writing option is corrected to match the existing UTF-8 proxy implementation. No SDK version, dependency, installer, backend or runtime configuration changes.

Validation:

• Executed the exact final README build/install recipe in a fresh Python 3.12 environment without credentials. Core imported from its site-packages with MCP absent; all 25 installed SDK module files matched source. After installing the extra, MCP 1.30.0 registered 29 tools and rejected both removed hosted-only tools. The registry probe made zero platform/provider HTTP requests.
• Final wheel metadata and sdist README match the final reviewed README. Normal HOME was preserved.
• Documentation contract checks cover all five feature-file write examples, both draft PR examples, the main/full-SHA prerequisite order, unchanged basic AgentClient recipe and immutable deployment examples. The existing canonical onboarding documentation test passed.
• Offline link checks: 12 passed, 21 remote links excluded, zero errors. New same-repository GitHub README anchors were resolved against the local source. A broken-link mutation produced exit 2 and was restored.
• Independent review approved the final two-file tree. Staged and post-commit documentation quality gates passed.

This evidence concerns documentation and isolated package installation. It does not establish a live publication workflow, runtime activation, provider access or deployment of the served guide. No package upload, platform deployment or skill-mount switch is included.

[Exzentttt]

Installed and independently verified on production on 2 November 2026, 14:31 UTC.

Both read-only backend document binds now serve the exact reviewed skill from merge a64905e55c1422b554c980fdc639c431acf82a38. The accounting backend image remains sha256:cbb281ca76dab00cb2cc9bac9d5a6c72f9e0dfaeb89b58e8d6309fb2d3cc6342. Fresh verification preserved the other 20 containers, all nine volumes, other mounts and semantic network bindings; deployment and serving remained enabled. No worker, launcher, frontend, Caddy or migration change was performed.

The canonical public skill returned HTTP 200 with SHA256 d6b10693343197883c1069a158e4cbe8efaa8c7e94369a8944f4a1a788db19ae. Its /health returned 200. Chromium on agentspore.ru received healthy JSON and the updated plain-text guide: SHA256 2d13a0a7be3b670b4b7c226dfac90a77b5d1fa9141883b2d671e9315d180759b exactly matches the reviewed source after replacing its 25 https://agentspore.com origins with https://agentspore.ru; no other content transformation is needed to explain the difference.

Observed limit: Python requests to the Russian domain returned Cloudflare 403 from two network locations while Chromium succeeded. This is not reported as successful scripted access, and no edge-security setting was changed. The canonical .com agent endpoint passed.

The instruction now describes feature branches, full-SHA readback, draft PRs, actual REST authorization and UTF-8 content, plus the five source-candidate publication MCP tools. PyPI publication and a complete live service publication workflow remain separate, unclaimed acceptance points; #290 stays open.