Skip to content

fix: clarify version and plan recovery guidance - #132

Merged
PatrickSys merged 1 commit into
mainfrom
fix/stranger-frictions-20261107
Nov 7, 2026
Merged

PatrickSys merged 1 commit into
mainfrom
fix/stranger-frictions-20261107

Conversation

@PatrickSys

@PatrickSys PatrickSys commented Nov 7, 2026 •

Copy link
Copy Markdown
Owner

health labels a plan without its matching *-SUMMARY.md as stale and recommends execution, even when the plan has not been approved. This keeps the warning, describes the missing record without guessing whether work has started, and directs the user through work-progress to check approval and the next action. The design table now agrees.

The README setup note distinguishes npm latest from unreleased GitHub main and shows how to check the published version and the version being run. Review focus: missing-summary recovery must check approval first, and setup must distinguish published and unreleased instructions.

Validation: both regressions failed before repair. The local Windows suite initially passed 29/30 files; the missing-tag module passed 19/19 after fetching its required tags. Final local health/surface checks pass (84 and 17 tests; one existing local-framework fixture skip). Separately, GitHub CI passes a clean full 30-file suite and the packed workflow check. The exact tarball was exercised on a fresh docsify clone and the blocked 0.35.3 workspace; undo restored the disposable clone clean. This does not establish a completed consumer feature. The separate proof-staleness check still reports one pre-existing orphaned historical commit; proof runners are unchanged.

Keep missing execution summaries visible while directing users through
progress and approval checks. Explain published npm versus repository
workflow versions at setup and align the warning's design description.

Trial session: 01a1b345-3bb3-7712-88c7-8fc5a7361d6b

Agent: codex-cli PB
@vercel

vercel Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
workspine Ready Ready Preview Nov 7, 2026 12:34am UTC

@PatrickSys
PatrickSys marked this pull request as ready for review November 7, 2026 00:49
@PatrickSys
PatrickSys merged commit c084694 into main Nov 7, 2026
4 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-07T00:50:08.655343Z b36ee5c Draft marked ready
ℹ️ 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.

This branch was successfully deployed

1 active deployment
Preview — b36ee5ca Deployed Nov 7, 2026 by vercel[bot]
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