Skip to content

Document current-attempt report ownership for the 1.5.0 pair - #194

Merged
luisleo526 merged 2 commits into
mainfrom
px/native-attempt-docs-20261009
Oct 9, 2026
Merged

luisleo526 merged 2 commits into
mainfrom
px/native-attempt-docs-20261009

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

What this documents

Reports belong to the current engine attempt. This change states that contract for the transpiler's users, under the planned 1.5.0 entry, beside the diagnostic notes already filed there:

  • a run that the engine refuses before it begins yields an empty report, not the report of an earlier run on the same handle;
  • a run that started and then failed keeps its partial report, unchanged;
  • stream snapshots follow the same ownership rule, stated explicitly.

The behaviour itself is the engine fix that landed on the engine's main branch; nothing in the transpiler changes.

Scope

Three Markdown files only: CHANGELOG.md, README.md and docs/PUBLIC_CONTRACT.md (116 additions, 4 deletions). Every non-Markdown file equals main. No emitted source, runtime, package or version change; no release claim: the entry stays under 1.5.0 — Unreleased.

Evidence

  • Documentation-only gate recorded for this exact head (three Markdown files, no sweep needed).
  • An independent review of the exact head: no blocking finding.
  • No tests or builds were needed for a documentation-only change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ko17oHtRco8iZ9vJptBAj8

luisleo526 and others added 2 commits October 9, 2026 17:49
Add "A report belongs to the call that returned it" to the public contract,
a pointer in the README's run section and an Unreleased changelog note.

A call the engine refuses without beginning gets the empty report, never an
earlier run's rows; a run that began and then failed keeps its partial rows;
the explicit stream snapshot keeps the owner's rows; recorded outputs keep
their own record of the last run that began. Callers read the error text, the
error code and the run status, because a refusal before the engine admits the
begin leaves the status at its earlier value. A batch or reentrant begin over a
live stream latches Failed and a repeated stream begin does not; a configure
time calendar failure leaves the run-number high-water where a failure inside
the begin has already moved it.

The text is framed as the contract of an engine fix that is not yet released:
it names no release number and states that engine v1.4.0 does not carry it.
Markdown only; no source, fixture, version, lock or workflow file changes.

Rebased onto main 6c8eadb (#193), which added the 1.5.0 diagnostic notes. The
changelog note now sits under its own "Planned 1.4.0-line patch — Unreleased"
heading after main's unchanged "1.5.0 — Unreleased" section, and its opening is
scoped to this documentation change: it adds no Python, JSON, diagnostic or
emitted-C++ change, keeps the 1.5.0 diagnostics separate and names no tag, date
or version. The contract's availability paragraph now says the report fix
itself changes neither the generated C++ nor the transpiler's Python and JSON
contract, so it does not contradict the "since 1.5.0" text beside it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The report-ownership notes were drafted as a planned 1.4.0-line patch. The
paired engine's report fix is planned for 1.5.0, so the notes now sit in a
Documentation subsection of the 1.5.0 entry, and the entry's opening names that
scope. The codegen change stays diagnostics only. Only CHANGELOG.md changes:
README.md and docs/PUBLIC_CONTRACT.md are byte-identical to the reviewed commit
531755a.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
@luisleo526
luisleo526 merged commit 15294eb into main Oct 9, 2026
5 checks passed
@luisleo526
luisleo526 deleted the px/native-attempt-docs-20261009 branch October 9, 2026 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant