Skip to content

fix(ci): gate CLI changes on relocated acceptance - #837

Merged
roodboi merged 3 commits into
nextfrom
fix/relocated-acceptance-pr-gate
Nov 14, 2026
Merged

roodboi merged 3 commits into
nextfrom
fix/relocated-acceptance-pr-gate

Conversation

@roodboi

@roodboi roodboi commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

A lifecycle change such as #810 can write under HOME or change the refusal envelope without touching the compiler crate. Light PR policy previously removed the Config compiler job, so its relocated CLI contracts were exercised only after merge.

Ready PRs changing CLI source (src/, root index.ts, packages/cli/) now retain the existing Linux x64 Config compiler lane, including the release build, eight relocated CLI scripts and release-install acceptance. The planner and independent inline boundary both enforce it, including with ci:mac and older trusted base policy. Protected acceptance-script changes already select full tiers. Drafts stay light; unrelated test/docs PRs keep their smaller plan. The required test fan-in now rejects failure, cancellation or an unexpected skip of any selected compiler host. Full native tiers therefore wait for the selected Mac/Intel compiler lanes too.

PR and integration evidence flow

Keep the existing next concurrency policy: an active run completes, only one pending run is retained, and new pushes may replace the pending run. Only PR events cancel active runs. The workflow comment, verification guide and CI docs now record the lead rule: after one batch merges, no further merge until a next run completes, unless the batch verifier ran the same checks on the combined tree. Splitting job concurrency would complicate matching evidence without guaranteeing a checkpoint between batches. No next run was rerun or cancelled; the freeze on 5002cf8 remains in force.

Cost: 0 added default macOS minutes per CLI PR, plus one existing Linux x64 compiler job. On Linux with Bun 1.4.4/Rust 1.97.1, the eight relocated scripts passed in 59.5 s, CLI build in 0.7 s and compiler preparation in 41.9 s with cached dependencies (102.1 s combined). This is component timing: the whole hosted lane also includes setup, schema, transport/unit and release-install checks. The latter needs passwordless sandbox setup on the local host and was left for hosted CI. The lead separately measured about 80 s for all nine scripts on Mac once the release exists.

Validation: final-plan regression names the existing src/lib/activity-log.ts HOME-writing path and actual command/backend/entry paths. The inline boundary is tested against old/tampered base policy, including ci:mac; shell fan-in tests exercise both selected and unselected compiler outcomes. Removing either guard independently in isolated copies exposes the missing Linux host. Focused planner/scope/fan-in/wiring tests, root typecheck/check/privacy, actionlint and docs checks pass. Persistent second-family Claude review CLEAN (rounds 55–57). Current-head hosted checks and Codex review pending.

HACK-2240. Based on next 5002cf8; no production source change. No manual Mac dispatch. This PR changes protected CI inputs, so its own hosted run automatically selects full tiers; the light-PR regression is established by the planner and independent shell tests. Lead owns merge.


Show it working
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

@vercel

vercel Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
hack-docs Ready Ready Preview Nov 14, 2026 11:51am UTC

Request Review

@roodboi

roodboi commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@linear-code

linear-code Bot commented Nov 14, 2026

Copy link
Copy Markdown

HACK-2240

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 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-14T12:03:11.386529Z 2c3b39d Manual request
🔒 Security Review ✅ Completed 2026-11-14T12:06:41.874001Z 2c3b39d Manual request
ℹ️ 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.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 96bd80c64d

ℹ️ 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

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 96bd80c64d

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@roodboi

roodboi commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Fixed hosted shard 5 environment-isolation finding in a314c2d. New real CLI-entry probes made the whole-file scan detect the existing Bash draft-fan-in fixture copying process.env. The fixture now passes only its explicit gate inputs; no scanner exception or assertion change. Local guard, selector, trusted-policy and shard regressions: 194 pass /1253 assertions; privacy and changed-file lint pass. Persistent reviewer round 59 CLEAN. No next run rerun/cancel/merge. @codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: a314c2d242

ℹ️ 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

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: a314c2d242

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

roodboi commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Ready for lead: a314c2d

Ready CLI-source PRs now retain the Linux x64 Config compiler acceptance lane. The planner and independent shell boundary both cover HOME-writing lifecycle changes (src/lib/activity-log.ts, commands/backends/entries), including ci:mac and old trusted base policy. The required test fan-in rejects selected compiler failure/cancellation/unexpected skip. All-source selection avoids a brittle shared-helper list. No further push after this note.

Current-head run43584876562: both Linux compiler acceptance lanes, Linux Candidate, all five Linux unit shards (including corrected shard5 environment guard), Docker shards/fan-in, lifetime, models and docs passed. Local194 guard/planner/trusted-policy/shard tests1253assertions, earlier scope/wiring tests, root gates, actionlint and docs checks pass; removing either policy rule independently exposes omission in negative controls.

Cost:0 additional default Mac minutes, one Linux x64 lane. Measured local8relocated scripts59.5s +CLIbuild0.7s +compilerprep41.9s cached=102.1s components. Actual current-head hosted x64 compiler lane230s including setup; its transport/relocated/release acceptance step131s. Hosted release-install check passed, closing the local sandbox-prerequisite gap.

Keep existing non-cancelling next group (onlyPR events cancel active runs), with the lead's documented rule: after a batch, wait for a completed next run unless the batch verifier ran the same checks on the combined tree. GitHub can replace pending runs, so concurrency alone does not enforce that checkpoint.

Review status: persistent second-family CLEAN (55–57,59); current-head Codex no findings; CLEAR at a314c2d242, zero unresolved threads/change requests. All bot comments read. Pending hosted Mac evidence: compiler, Candidate and unit shards1/8–3/8; required test fan-in not complete. Ready for lead Mac batch with pending evidence disclosed. Own protected-input CI selects full tiers automatically; no manual Mac dispatch. GitHub MERGEABLE; next1f761ac56 changes no authored path here. No named job failure at this head, no known-flake rerun, no next run rerun/cancel/merge.

@roodboi

roodboi commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

The lead Mac timeout is addressed in 2c3b39d: the old single test built 18 repositories under one five-second timeout; now eight tests each build one repository (six independent path cases, one ci:mac case, one draft case). No timeout was raised. Existing path/host assertions remain, with policy=base also asserted in the Mac mode. Added explicit shell and planner regression coverage for scripts/lib/native-plan-home.ts through the protected scripts rule. Local guard/policy/selector run: 150 pass,814assertions; individual new boundary cases67–80ms on Linux. Mac timing needs the lead recheck. Persistent reviewer60 CLEAN. @codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: 2c3b39dc5e

ℹ️ 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".

roodboi commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Ready for lead: 2c3b39d — Mac recheck requested.

This supersedes the a314c2d readiness note after the lead's reproducible Mac timeout. The old single test created 18 Git repositories under one five-second timeout. It now creates eight repositories across eight tests: one for each of the same six path cases, one ci:mac case, and one draft case. Every test retains the default five-second timeout. No file-wide or individual timeout was raised, and path/host assertions remain intact.

The shared scripts/lib/native-plan-home.ts from #836 is already covered by the protected scripts/* rule. Explicit regressions now verify it through both the actual workflow shell and the planner, with requiresWorkflowFull asserted so deleted-input fallback cannot mask coverage.

Local guard/policy/selector checks: 150 passed, 814 assertions; each new boundary case took 67–80 ms on Linux. Lint/privacy passed. Same persistent second-family reviewer: CLEAN, round 60. CLEAR at 2c3b39dc5e: no unresolved bot threads or change requests. Current-head Codex was requested and is still running.

Mac timing is not qualified by these Linux measurements; please recheck this head in the Mac batch. New current-head Actions run 43591953429 is queued. The prior head's Linux acceptance evidence remains historical; it is not claimed as a new-head CI pass. GitHub says MERGEABLE against next 1f761ac with no authored-path conflicts. No further pushes after this note. #832 is untouched and retains the lead's Mac pass. No next rerun/cancel/merge and no manual Mac dispatch. Task scratch cleaned; validation evidence retained.

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 2c3b39dc5e

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@roodboi
roodboi merged commit 5e93148 into next Nov 14, 2026
30 checks passed
@roodboi
roodboi deleted the fix/relocated-acceptance-pr-gate branch November 14, 2026 14:34
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