v0.4.0-draft.1: Real owned use and native recovery

Real Owned Use, Native Recovery, and the Full Manuscript

v0.4.0-draft.1 is a benchmark and evidence prerelease. The Spec and core wire
revision are unchanged; this is not a standards endorsement or product launch.

Actual Results

The deployed model produced six report candidates in the preserved amended
read-only study. Two met the frozen task contract and same-project source review;
four oversized candidates remain failures. This continuation does not rerun the
model, shorten failed answers or relax their grade.

The two eligible reports were delivered to
one dedicated owned issue,
using Octokit and GitHub's official pinned MCP server. Six distinct controlled
faults test current revocation, narrowing, real process kills, acknowledgment
timeout and actual stdio disconnect.

• 20 fresh workers: 8 initial executions, 4 read-only recoveries, 8 duplicate probes.
• 5 native comment calls and 5 objects: 2 ordinary reports and 3 synthetic controls.
• Both current-policy denials send nothing.
• Three delivered-but-unacknowledged effects recover through reads, without resend.
• The pre-send crash retains unknown; absence of evidence is not permission to retry.
• All 8 duplicate probes make no new native comment call.
• 21 journals, 283 records and 78 historical source entries reconstruct successfully.
• Six anonymous GETs match the issue and five exact comment commitments.

The supervisor span is 52.437 seconds including fresh-worker startup, shadow
preparation and networking. Earlier issue creation/setup are separate. These
unequal tasks and fixed-order shadows do not support a latency superiority
claim. The earlier matched offline comparison's 3.97% protocol overhead remains
reported, not replaced by a fast-path-only timing.

Read and Reproduce

• 43-page, 9-figure manuscript PDF, with semantics, algorithms, conditional invariants, counterexamples, baselines, costs, failures and five appendices.
• Readable manuscript.
• Results and exact evidence index.
• Versioned no-send reproduction guide.
• Local verification and manuscript checks.
• Clean-bundle verification, including the local OPA download failure.

Attached source-history bundles preserve the historical blobs needed for replay.
GitHub's automatic source ZIP is not enough for history-dependent reconstruction.
Use the full public clones or the two attached bundles, verify SHA256SUMS,
then install the locked dependencies. Replay needs no model key, provider login
or OSuite account. Do not execute new live writes on the existing evidence issue.

Verification and Scope

Release source: 6d4f3c358ca5f68040a1416d751328e9aab041f5.
Original live execution source: f93b1cfcbf2c2665b4acc7c5dc8fb92d1ba8d6b6.
Spec pin: a9b86f4b529a5e330c2a9bf1b8c4c259a7b36e40.

All 1,623 local software methods pass, with no failures/skips; both
Linux and macOS CI jobs
pass on the release commit. These are software checks, not 1,623 independent
customer workloads. The complete paper was rendered and visually checked.

Both source bundles were cloned into a clean directory and the owned-write
replay, arithmetic audit and two old field replays passed. The local default
OPA download failed; the continuation used an already available binary only
after checking its exact pinned hash. This is not a successful fresh local
binary download. The separate CI installation steps passed.

This is actual same-project use of real GitHub infrastructure, not independent
human evaluation or customer production. Faults were deliberately induced.
Current-content reconciliation is conditional, not global exactly-once delivery,
atomic remote revocation or observation of all notification/webhook descendants.

The first pre-reservation failure, four task-budget failures, old releases and
raw measurements remain available. No Studio/Hook modification, new Azure
resource, protected collaboration/customer data, invitation or formal journal
submission is included.

Public Download Check

All ten attached files, including the checksum manifest, were downloaded
without GitHub credentials at 14:23:20--14:23:35 UTC on 19 October 2026.
Every response was HTTP 200 and every file matched its local SHA-256.
The downloaded manifest also verifies all nine payload files.

An earlier direct CLI attempt timed out. The successful check explicitly used
the machine's already configured system proxy, without changing network
settings or supplying a GitHub login. An additional anonymous API download of
the PDF matched the same hash. These observations demonstrate the published
bytes are publicly retrievable under the stated route, not universal network
availability. No earlier asset, raw result or source tag was replaced.