Skip to content

[stack 1/8] ci: harden verification and release compatibility - #1158

Open
sethkarten wants to merge 7 commits into
mainfrom
stack/external-01-verification
Open

[stack 1/8] ci: harden verification and release compatibility#1158
sethkarten wants to merge 7 commits into
mainfrom
stack/external-01-verification

Conversation

@sethkarten

@sethkarten sethkarten commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Stack 1/8 — ci: harden verification and release compatibility

Active review snapshot — do not merge yet. The complete stack is open for architecture/design review, while final cumulative audit, CI, Cursor Bug Bot, and Macroscope findings are being remediated. Branches will be force-updated after validation.

Base: main
Review order: merge only after the preceding stack layer is accepted. This PR is not intended to merge independently out of order.

Stack navigation

  1. #1158 — ci: harden verification and release compatibility
  2. #1159 — fix(security): harden session and autonomous execution boundaries
  3. #1160 — fix(coding-agent): make persisted state crash-safe
  4. #1161 — fix(daemon): fence worker and supervisor lifecycle state
  5. #1162 — fix(coding-agent): repair queued and archived session lifecycle
  6. #1163 — fix(coding-agent): complete Windows kernel and daemon startup
  7. #1164 — fix(providers): harden MCP OAuth and Codex transports
  8. #1165 — fix(runtime): bound transcript and autonomous recovery

Summary

  • Gate PRs and releases on the locked Python runtime suite across Python 3.10–3.14.
  • Verify the complete emitted node-only provider bundle closure, including Bedrock.
  • Support npm 12 remote-dependency policy with accurate interactive consent and a real local-HTTP regression.

Validation

Provenance

  • Authored independently from upstream/main using issue reports and PR descriptions/comments only.
  • No external contributor branch, diff, commit, implementation code, or test code was fetched, inspected, copied, or reused.
  • The implementation and regression tests in this stack are maintainer-owned.

Linked-item disposition

Fixed on merge

Independently superseded pull requests

Partial/distinct overlap — remains open

Related reports — no closure claim

Distinct follow-up — remains open

Reviewer notes

  • Please review this layer against its immediate stack base, not against main, to avoid cumulative duplicate diffs.
  • No merge is requested; the complete stack is being left for human review.

This was referenced Aug 10, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit a1d2e83. Configure here.

Comment thread install.sh
Check npm's global bin directory with:

npm bin -g
echo "$(npm prefix -g)/bin"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

PATH hint expands too early

Medium Severity

The PATH recovery hint uses an unquoted heredoc, so $(npm prefix -g) runs while the installer prints the message instead of remaining a command for the user. That replaces the intended npm bin -g substitute with an already-expanded echo "/some/path" line, which makes the “check with” instructions misleading right when the binary is missing from PATH.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a1d2e83. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant