docs(devlog): record the 2.58.0 release evidence

[lidge-jun]

Summary

Records what the 2.58.0 release actually did, step by step, with the run ids and commits that prove each step. Closes the train unit opened in #4909.

It also writes down three things this release taught, because each one cost real time and none of them is obvious from the code: a green pull request is not a green merge result when two branches touch the same capped file, dispatching a stale ref runs that ref's CI definition rather than the current one, and rebasing a stacked child silently drops anything that lived only inside its merge commits.

The native control stack section states what shipped behind default-off flags and the three conditions that remain before recommending activation.

Documentation only: one new file under devlog/_plan/260918_2580_release_train/.

Verification

Hosted CI on this head. The heavy legs are filtered out by the changes job because the diff is documentation only.

Every claim in the document names its evidence — run ids, commit SHAs, the publish line, and the transparency-log index — so the file can be checked against the repository and the Actions history rather than taken on trust.

No local suite, typecheck, build, or install was run.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults — this records a completed release and adds no code.

Summary by CodeRabbit

• Documentation
  • Added release-train documentation for version 2.58.0, covering validation, promotion, publishing, and preview rollout steps.
  • Documented post-release lessons related to merge validation, stale references, and rebasing.
  • Recorded the native control stack’s behavior, remaining activation conditions, and registry propagation status.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-17T18:27:46.323599Z	7842429	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 9ee199d0-a0c7-4eb3-a295-c12e1a8d48bd

📥 Commits

Reviewing files that changed from the base of the PR and between 4655d32 and 7842429.

📒 Files selected for processing (1)

• devlog/_plan/260918_2580_release_train/040_release.md

---

📝 Walkthrough

Walkthrough

The release plan documents the 2.58.0 release sequence, three operational lessons, the shipped native control stack contract, remaining activation conditions, and registry propagation status.

Changes

Release train documentation

Layer / File(s)	Summary
Release sequence and evidence devlog/_plan/260918_2580_release_train/040_release.md	Lines 1–19 document the fourteen-step 2.58.0 release sequence, including promotion, regression, publishing, and evidence records.
Operational lessons and activation conditions devlog/_plan/260918_2580_release_train/040_release.md	Lines 20–61 record three release-process lessons, the native control stack contract, and three conditions remaining before activation.
Registry propagation status devlog/_plan/260918_2580_release_train/040_release.md	Lines 63–71 record the pending package verification, the observed E404 response, the latest version, and the instruction not to republish.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[lidge-jun]

리뷰 · 우선순위 77 / 80

이 PR은 지금 dev 끝(4655d32f88, package 2.59.0, tip #4916) 위에, 이미 끝난 2.58.0 출시 열차의 증거 기록만 남깁니다. 바뀌는 파일은 하나뿐입니다. devlog/_plan/260918_2580_release_train/040_release.md (+72 / −0). 코드·설정·워크플로는 건드리지 않습니다. 베이스는 dev이고, 헤드 브랜치는 codex/260918-2580-release-evidence입니다. #4909가 열어 둔 열차 유닛(000_roadmap.md)의 마지막 칸을 실제로 채우는 문서입니다.

문서가 말하는 순서는 현재 저장소와 맞습니다. 프리즈 후보 5061f2c956 → dev 버전 올림 #4916/4655d32f88 → main 승격 #4915/6fe4cd0de8 → 태그 v2.58.0이 그 커밋을 가리킴 → preview 승격 #4917/48e1ddba0b. release.yml 런 35257765967은 성공이고 headSha도 6fe4cd0de8입니다. dev-version-bump 런 35253998264도 성공입니다. 출시가 이미 끝난 뒤의 증거 문서라서, types.ts/config.ts 분리 캠페인과도 충돌하지 않고, 리베이스 대신 닫을 대상도 아닙니다.

본문에 적힌 세 가지 교훈(초록 PR ≠ 초록 머지 결과, 오래된 ref dispatch는 그 ref의 CI 정의를 탄다, 스택 자식 rebase가 머지 커밋 안쪽만의 변경을 조용히 버림)과 네이티브 컨트롤 스택 기본-off·활성화 전 조건 세 줄은, 이번 열차에서 실제로 시간을 잡아먹은 이야기와 맞습니다. npm 전파가 아직 pending일 수 있으니 재발행하지 말라는 경고도 출시 직후 문서에 어울립니다.

라인 표 — devlog/_plan/260918_2580_release_train/040_release.md
라인 13 - Full-platform regression 행이 런 35247708168을 ‘Windows·Linux·gates 등은 green, macOS capacity cancellation만 비-green’이라고 요약합니다. 실제 job을 보면 Windows 9/9·Linux 4/4·gates·docs·keyring·npm-global·docker smoke는 맞지만, 전체 conclusion은 cancelled이고 집계 job ci는 failure입니다. macOS 1/2는 success, macos control·macos 2/2만 cancelled입니다. 큰 거짓은 아니지만 ‘비-green = macOS cancellation뿐’ 문장은 한 단계 더 촘촘히 쓰는 편이 증거 문서답습니다.
라인 1~3 - 제목이 ‘Published’인데, 같은 폴더의 000_roadmap.md 첫머리는 아직 ‘Open’입니다. 이 PR이 열차 유닛을 닫는다면 roadmap 상태 한 줄을 같이 닫을지, 아니면 040만으로 충분하다고 볼지 정해야 합니다.
경로 040_release.md - 문서만 추가·머지 가능(MERGEABLE)·documentation 라벨. 잘못된 브랜치나 날조 SHA는 보이지 않습니다.

메인테이너의 판단이 필요한 지점

• 라인 13 요약을 지금처럼 두고 머지할지, 아니면 overall cancelled / 집계 ci failure / macOS 1/2 success를 한 문장으로 명시할지.
• 000_roadmap.md의 ‘Open’을 이 PR에서 ‘Closed/Published’로 같이 고칠지, 후속 한 줄 PR로 둘지.
• registry verification=pending / E404 관찰을 발표 전에 한 번 더 읽을지(문서 자체는 재발행 금지로 이미 막아 둠).

너의 추천
증거 SHA·태그·주요 런 ID가 저장소와 맞고, 범위도 문서 한 파일이라 dev에 그대로 머지해도 됩니다. 가능하면 라인 13에 overall conclusion과 macOS 1/2 success만 한 줄 보강한 뒤 머지하고, roadmap ‘Open’ 닫기는 같은 PR에 넣거나 바로 이어서 처리하세요. 중복·분리 캠페인 무효화 대상 아닙니다.

이 댓글은 grok-bot이 작성했습니다

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78424292eb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move the completed release train to _fin

This entry declares the release published and the commit closes the train, but the unit remains under _plan and its roadmap still says Open. That misclassifies completed work as active; record any final registry result, update the status, and move the whole 260918_2580_release_train directory to devlog/_fin/.

AGENTS.md reference: AGENTS.md:L102-L105

Useful? React with 👍 / 👎.