Skip to content

docs: macOS lanes CHANGELOG entry to Unreleased; BUDGET_KIB wording - #557

Merged
afflom merged 1 commit into
release/v0.4from
docs/changelog-macos-lanes
Nov 16, 2026
Merged

afflom merged 1 commit into
release/v0.4from
docs/changelog-macos-lanes

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Member

Two doc-only fixes, with no code or behaviour change:


Generated by Claude Code

The #550 merge placed its CHANGELOG entry under 0.4.3, which it did not
ship in. The BUDGET_KIB comment claimed more than a measured pair; it is
a threshold chosen for one slot below 20 GiB (review on #554).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3QVAsEzzaQPMzJnNz1

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bounded source review clear at7a9b999d, sole parent actual949cb261. The complete two-file delta moves the macOS-lanes entry from0.4.3 to Unreleased and removes the unsupported 'more than a measured pair' claim. This resolves the wording finding from #554 review5912237599. BUDGET_KIB remains10GiB; executable behavior and workflow are unchanged. The divisor remains a planning threshold, not a measured peak or memory guarantee.

No runtime checks or completed gates were repeated for these prose changes. Existing final-head CI43773941485 is queued and repro43773941427 passed; this is source clearance, not final acceptance or merge authorization. Preserve final qualification and actual merged-tree equality. Receipt /workspace/work/pr557-7a9b-doc-repair-review-20261116.json; SHA256310aafdfda267ed11de0a56ba83e33ea8c0b55e70b7753f615fdca23b32f9777. All existing STOP boundaries remain.

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completed CI 43773941485, attempt 1, is credited: 71 jobs and all 831 executed steps succeeded; three Intel jobs were skipped. Repro 43773941427 passed its one job and seven steps. The new plan log binds checked merge e4543eb to tree 0fdbe319, exactly equal to this head’s tree. The prior two-file documentation source review remains applicable; no runtime checks or producer work were repeated.

Full platform acceptance remains unresolved because Intel work was skipped. Existing owner: supply applicable input-bound Intel evidence or resolve the scope against the standing full-acceptance requirement, then retain actual merged-tree equality after any landing. A green overall result and clean mergeability do not remove that requirement. No merge, retry or STOP waiver is initiated here.

Receipt: /workspace/work/pr557-7a9b-terminal-gate-audit-20261116.json; SHA256 f8c33fb6ce0e2bc05dfec1974309c89dc5717662953d0865bd4eea4eb93227b2.

afflom commented Nov 16, 2026

Copy link
Copy Markdown
Member Author

Intel scope follows the same disposition as #554 (comment 6902033970): under the owner's 2026-11-14 decision on #535, ordinary ready PRs into a line skip Intel, and the merge push runs it on the merged tree. This diff is prose only. #557 is on hold until #507 lands, and I'll keep the merged tree equal to the gated tree.


Generated by Claude Code

@afflom
afflom merged commit dfc1791 into release/v0.4 Nov 16, 2026
75 checks passed
@afflom
afflom deleted the docs/changelog-macos-lanes branch November 16, 2026 05:02
afflom pushed a commit that referenced this pull request Nov 16, 2026

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

External landing recorded at 05:02:28Z: actual dfc1791 has parents 4afb850 (#507 actual) + reviewed 7a9b999. Its tree 189b9dcd differs from the previously checked/head tree 0fdbe319 because it includes the #507 composition. Relative to 4afb850, the merge adds only the reviewed two-file documentation repair.

Prior 71-job/831-step credit with three Intel skips remains scoped to 7a9b; it does not qualify the new whole tree. Actual repro 43807672989 reports success; actual CI 43807673006 remains pending. Existing owner retains final composition and Intel qualification. Preserve the separate missing-print artifact diagnosis and passing execution evidence; no reconstruction, inventory waiver or automatic retry is requested.

Receipt: /workspace/work/pr557-dfc-external-actual-audit-20261116.json; SHA256 2e4d4b761152901f1968ea1084c7532e288c04e8a8b0f3fc437fc9c42e12cd36. All standing STOP boundaries remain.

humuhumu33 added a commit that referenced this pull request Nov 16, 2026
…arrays branch

PF-26 and the arrays both move the language-1.2 identity from the 0.4.3 base;
the combined tree's ID, b78cb38d…, replaces each side's in the constant, the
locks and the records, and the register is 499 IDs: PF-26 joined the line as
its 498th, SM-39 is the 499th. A conflicted generated projection takes the
line's side, and one only this branch named is dropped, for regeneration to
write.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actual dfc1791 qualification is now credited: CI 43807673006 attempt 1 completed with all 77 jobs and 878 steps successful, zero skips. The single new plan log checks out dfc1791 exactly; its recorded tree is 189b9dcd. This includes Intel construction, lower/validate/moves/print execution, and successful complete Intel inventory/execution-receipt verification. Actual repro 43807672989 attempt 1 passed its one job and seven steps. This resolves the pending actual-tree/Intel qualification noted in review 5915453709 for dfc only.

Current release/v0.4 is 0541025, a different commit: this receipt does not qualify it. The earlier 7a9b result and missing-print artifact diagnosis retain their historical scope; no canceled/cross-attempt aggregation or artifact reconstruction is used. Existing owner remains responsible for current-tree qualification and delivery. #543 actual forward failure on .git/index.lock, #468 obligations, all #316 frozen fields/receipts, #431/old TC03, R25 STOP and future #338/#438/#541 holds remain unchanged. No rerun, build, merge, closure or STOP waiver is requested.

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.

2 participants