Repository navigation
docs: the 1.6.0 release (changelog, current pair, HPO note) - #399
Merged
Merged
Conversation
Prepare the final 1.6.0 release documentation dated 2026-10-17, paired with pineforge-codegen 1.6.0 and the matching pineforge-hpo release for selected-window contract revision 1.3. CHANGELOG.md adds the 1.6.0 — 2026-10-17 entry above 1.6.0-rc.1 — 2026-10-14, carrying forward the release-candidate entry's substance and naming the six documentation and test-only changes merged since v1.6.0-rc.1 (#390, #393, #394, #395, #396, #397). README.md updates the current-release block and the codegen command-block pointer to 1.6.0 and adds the v1.6.0 bullet to the Releases section. The current-release block's 1.5.0 sentence from 4c78f39 ("The release notes cover recorded outputs, the call-scoped report rule and the test inputs' move to a private repository") is replaced on purpose by the 1.6.0 sentence that lists what 1.6.0 covers; that 1.5.0 summary stays in the Releases list (the v1.5.0 bullet) and in CHANGELOG.md's 1.5.0 entry. docs/pages/public-contract.md adds the 1.6.0 paragraph after the 1.5.0 paragraph and updates the same-version pairing line to 1.6.0.
…value-ownership wording) The paired-HPO line no longer claims HPO support for selected-window revision 1.3; HPO 1.6.0 does not implement selected windows (docs/return-stats.md:9 in pineforge-hpo). The landed follow-ups #396/#397 are said to be checked against their own deliberate bugs, and the figures remain the candidate's. README.md and docker/README.md replace "complete value ownership with" by "value ownership through", the wording of the 1.6.0-rc.1 changelog entry, since no completeness proof was run. The changelog's no-code-change sentence names the docker/README.md rewording. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
luisleo526
marked this pull request as ready for review
October 17, 2026 02:02
luisleo526
added a commit
that referenced
this pull request
Oct 17, 2026
… not 'complete' (#400) docs/pages/report-schema.md said that revision 1.3 means "complete value ownership with" the four value-failure codes. That sentence came in with 868aa65 (#388). No completeness proof has been run (EN-115), so the published API docs claimed more than the evidence supports. The sentence now says "covering value ownership through", the wording of the 1.6.0 notes (CHANGELOG, README.md, docker/README.md, #399). It replaces the #388 phrase "meaning complete value ownership with". Docs only; no code, test or harness change. Co-authored-by: CORE-TOP <[email protected]> Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation for the final 1.6.0 release, paired with codegen 1.6.0. The tree ships as main (ea209c1):
v1.6.0-rc.1(04607c1) plus the docs/test-only PRs #390 and #393 to #397. No file undersrc/,include/,cmake/,docker/orrunner/changed after the rc tag. The release workflow bumps VERSION and tags.1.6.0 — 2026-10-17entry. It carries the rc.1 entry's claims unchanged, with no new capability claim; it records that the two planned assertion follow-ups landed (tests: assert the quantity-grid overflow fallback in test_value_admission_arith #396, tests: assert that a failed report leaves one whole JSON document on stdout #397) and lists the docs/test-only changes since the rc.#398 is not part of 1.6.0.
Draft until its gating read is clean.
🤖 Generated with Claude Code