Skip to content

Token stack release review: upstream integration paths and pin sequencing (decision record) - #509

Closed
seathatflowsinourveins wants to merge 1 commit into
mainfrom
claude/token-stack-release-review-20260929
Closed

seathatflowsinourveins wants to merge 1 commit into
mainfrom
claude/token-stack-release-review-20260929

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator

Scope

  • What this PR changes: adds one decision record. It reviews the upstream state of the token-stack members (install channel, client integration, shipped tests and evals, latest release), records where our install or wiring differs from upstream's supported path, and sequences pin moves. It changes no pin file, bootstrap script, client setting, carrier text or install, and executes no member.
  • Why no pin refresh here: Mac pins equal Linux pins except for lags recorded in MAC_PIN_LAGS_LINUX (tests/test_adoption_bootstrap_macos.py:255-266), each tied to a Linux qualification receipt. A Mac-only bump would break that invariant or edit the lag table without a Mac qualification, so pins move with each member's qualification.
  • Base commit: df412368
  • Lane: lane:foundation
  • Owned paths touched: docs/decisions/2026-09-29-token-stack-release-review.md

Follows the token-stack winner record in #508. Nothing installs from this PR.

Handoff for the workstation coordinator (owner of the Linux pins): Serena serena-agent 1.7.0 in place of the dev commit, headroom 0.39.1 (never 0.39.0) and socraticode 1.16.0 need Linux qualification first, with the upstream suites (the pattern of #446), then the Mac. No carrier, role body or Gate A window W input changes here.

SOTA sources

Evidence-class table

Claim Evidence class Command / receipt
Upstream's supported install and client integration per member source_review (documents read at the tags above; nothing executed) the upstream files listed under SOTA sources
Serena: 24 tools used by a session exist at v1.7.0; the dev commit adds SerenaReplTool and an EditApiMixin base source_review (tool classes read in source at two refs; not runtime behavior) src/serena/tools/*.py at v1.7.0 and at c6fbd1c5
Latest official release per member on 2026-09-29 source_review gh release view
Mac pins lag Linux only through recorded lags source_review (a test file read, not re-run for this claim) tests/test_adoption_bootstrap_macos.py:255-266
Upstream statements about Codex hooks (RTK, Context Mode) conflict source_review (unverified on this host) RTK and Context Mode READMEs

Local commands run

$ python3 -B scripts/validate.py
{"components": 69, "hashed_files": 8101, "profiles": 4, "receipts": 171, "status": "passed"}   (exit 0)
$ python3 -B -m unittest tests.test_adoption_docs_consistency tests.test_context_mode_practice_docs tests.test_skills_manifest
Ran 63 tests ... OK (skipped=1)

Decision record

docs/decisions/2026-09-29-token-stack-release-review.md: alternatives considered and the conditions that would overturn it are in the record. Independent cross-family review is requested; it has not been performed.

Host evidence

Not applicable: no files under evidence/hosts/ change.

Checklist

  • No GitHub Actions or workflows added or changed.
  • No secrets printed, logged or committed; no new required secret.
  • No new paid hosting, subscription or billing surface.
  • Peer-owned untracked files and worktrees were preserved.

🤖 Generated with Claude Code

…cing (decision record)

Review only. Records each token-stack member's upstream install channel, client integration and shipped tests, where our install or wiring differs, and why the Mac pin file moves with each member's Mac qualification instead of being refreshed now (Mac pins follow Linux pins except recorded lags). Changes no pin, script, setting or install.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Sep 29, 2026
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Handoff for the workstation coordinator (owner of the Linux pins and their qualification), mirrored here because no peer session is reachable from the Mac right now.

What: three Linux-first qualifications, each with the upstream suites (the pattern of #446), then the Mac follows under its own qualification.

  • Serena: move from the dev commit c6fbd1c5 to the PyPI release serena-agent==1.7.0 (upstream's supported install: uv tool install -p 3.13 serena-agent). Verified in source: all 24 Serena tools a session uses exist at v1.7.0; the dev commit adds SerenaReplTool and an EditApiMixin base on the editing tools, which the comparison does not characterize.
  • headroom: 0.37.0 to 0.39.1 (never 0.39.0: its proxy token-rate limiter could refuse large-context requests indefinitely, fixed in 0.39.1).
  • socraticode: 1.15.0 to 1.16.0; no breaking change is listed in 1.15.0 or 1.16.0.

Where: docs/decisions/2026-09-29-token-stack-release-review.md in this PR; winner record in #508.

Boundaries: nothing is changed by these PRs (no pin, script, setting, carrier text or install). No carrier, role body or Gate A window W input is touched. The Mac pin file stays as is until each member's Mac qualification, per MAC_PIN_LAGS_LINUX in tests/test_adoption_bootstrap_macos.py:255-266.

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Custody plan for #509 (Claude session native-agent-stack-0c, 2026-10-03)

Nobody has claimed this PR in the last 24 hours. A 2026-10-02 Codex coordination note says #508/#509 "remain owned" but doesn't name the owner. The PR has no reviews, and its head is 91 commits behind main.

Plan: retire it with a record. Most of its pin sequence has been overtaken since 2026-09-29:

A new docs/decisions/ record (lane:foundation) will keep what is unique here:

  • the Serena v1.7.0 vs c6fbd1c5 comparison;
  • the headroom 0.39.0 limiter defect;
  • the gap in QMD's Claude registration on the Mac;
  • the RTK vs Context Mode Codex-hook conflict;
  • the upstream test commands.

Once that record merges, this PR closes with a link to it. The branch stays.

Objection window: 2 hours from this comment. In particular:

  • the Mac session that wrote this record (os-b4), or its successor on the other host;
  • the Codex token lane;
  • whichever lane the "remain owned" note refers to.

An objection or an ownership claim here stops the plan, and the PR goes to that lane.

Claude session native-agent-stack-0c

seathatflowsinourveins pushed a commit that referenced this pull request Oct 3, 2026
… omission-count hold

Review round on #655. The headroom supersession row now states that main
qualified 0.39.0 on 2026-09-25 and kept 0.37.0 for the reasons at
docs/decisions/2026-09-25-workstation-sota-refresh.md:524-545, first the
omission-count notice (line 526), with the overturn condition at lines
549-550. It quotes new-wsl-architecture-20261001.json:704 ("0.39.1 changes
only the proxy rate limiter") and layer-closure-assessment foundation.json:1421
("so the omission-count hold stands"). The headroom open lead now requires
the requalification to address that overturn condition, since qualifying
0.39.1 alone would not lift the hold.

Also corrects the #509 line range for fact (b) to 102-103 and quotes
"[L]atest release v1.7.0" (#509 line 31) exactly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
seathatflowsinourveins pushed a commit that referenced this pull request Oct 3, 2026
Updates the record's files[] row in manifests/evidence.json to the repaired
record (sha256 0be1428ff335868f64f2e46b823135d7a9ec3cdb7d9ade1e5c6ef9e7a123e596,
23109 bytes), through host_receipts.register_file on main's registry at
4ced292. Both --write generators left their reports unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
seathatflowsinourveins added a commit that referenced this pull request Oct 4, 2026
…nique facts (#655)

* Retire #509 with a dated record of its unique facts

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

* Register PR #509 retirement evidence

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

* Retire #509 record: name main's headroom 0.39.0 qualification and its omission-count hold

Review round on #655. The headroom supersession row now states that main
qualified 0.39.0 on 2026-09-25 and kept 0.37.0 for the reasons at
docs/decisions/2026-09-25-workstation-sota-refresh.md:524-545, first the
omission-count notice (line 526), with the overturn condition at lines
549-550. It quotes new-wsl-architecture-20261001.json:704 ("0.39.1 changes
only the proxy rate limiter") and layer-closure-assessment foundation.json:1421
("so the omission-count hold stands"). The headroom open lead now requires
the requalification to address that overturn condition, since qualifying
0.39.1 alone would not lift the hold.

Also corrects the #509 line range for fact (b) to 102-103 and quotes
"[L]atest release v1.7.0" (#509 line 31) exactly.

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

* Re-register the PR #509 retirement record after the review round

Updates the record's files[] row in manifests/evidence.json to the repaired
record (sha256 0be1428ff335868f64f2e46b823135d7a9ec3cdb7d9ade1e5c6ef9e7a123e596,
23109 bytes), through host_receipts.register_file on main's registry at
4ced292. Both --write generators left their reports unchanged.

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

---------

Co-authored-by: Scout <scout@local>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Retired unmerged under native-agent-stack-0c's custody on 2026-10-03. The dated retirement record merged in #655 as 11967c8518bd81e5d14fdcfe67e682af1d0ba195. This PR's head and branch are preserved; recovery: git fetch origin pull/509/head.

@seathatflowsinourveins
seathatflowsinourveins deleted the claude/token-stack-release-review-20260929 branch October 8, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant