[Pigbibi]

AI assistance

Claude Code, model Opus 5.5 (native box job, single writer).

What changed

Registers the merged #1166 commit c0ac5848b8af983d4f857e465c6ff64009b0957f (the S2 Desk N1 live flip) as a dedicated, fail-closed reviewed-main release source in deploy-strategy-switch-console.yml. This follows the same pattern as the S1 source 1618b248 (#1134). Every prior source definition is unchanged.

• Selector (Select reviewed historical main source): pins the exact source and these blobs:

  • sole parent af897f8b;
  • tree a7b327c0;
  • v2 map blob 281002ea;
  • Worker blob bbe906c5;
  • the reviewed fix(digest): show scoped Binance wallet valuation #1126 reader test f590e43d from its own tree. Nothing is composed onto it.

  The run must use the main ref, frontend release mode, no secret or profile sync, and receiver checks retained. CONTROL must equal the run SHA and differ from SOURCE, and SOURCE must be an ancestor of CONTROL.

• Overlay: the selected head must equal its tree, and the rebuilt map must equal the pinned blob, with no staged, unstaged or untracked delta. It is bound to this source input.

• Publisher: it uses the current reviewed-main path:

  • the active version is the sole configuration donor;
  • the upload is version-pinned;
  • a separate concurrency witness is kept;
  • module, migration and configuration checks run;
  • activation is 100%.

• Tests (tests/console_deploy_safety_validation.mjs):

  • real-Git identity: five pins, ancestry and a new map generation. The map has 45 assets, keeps the S1 delivery guard and carries the N1 switch-strategies projection. The Worker keeps the S1 producer field and serves the N1 routes;
  • accepted-source call order;
  • mode, ref and unknown-source rejection before any Git call;
  • wrong parent, tree, map, Worker or reader test, object, ancestry or CONTROL (including the S1 entry Worker and map);
  • no cross-acceptance with 1618b248;
  • overlay tampering;
  • publisher witness and drift cases.

What ships with this source: since the published S1 source 1618b248, main gained 25 commits. They are the two S2 PRs (#1150, #1166), the runtime_support module-extraction refactor wave (#1137–#1165), two digest fixes (#1135, #1157) and governance pins. There is no dependency, lockfile or wrangler change; only the test:operations scripts changed. Bundling the source Worker graph locally gives one 2.9 MB module (the workflow limit is 10 MiB).

How verified

• node tests/console_deploy_safety_validation.mjs: PASS. Source cases went from 269 to 304 and overlay cases from 54 to 66, with 257 isolated release cases.
• Fail-before:
  • Against the workflow on main: AssertionError: invalid_frontend_release_mode.
  • With only the Worker pin removed: AssertionError: rev-parse c0ac5848…:web/strategy-switch-console/worker.js.
  • With the source removed from the overlay: S2 Desk N1 overlay must validate exact pins: {}.
  • With the source removed from the publisher allowlist: frontend_release_stopped … pre_upload_active.
• Every Node test that reads this workflow passes: binance_receiver_deploy_acceptance_validation, console_946_backend_workflow.test, console_catalog_release_validation, console_deploy_safety_validation, console_version_comparator_validation, website_release_combination_validation.
• Python workflow tests (test_console_config_compare, test_runtime_settings, test_ux1_deploy_workflow): 211 passed, 1 skipped.
• git diff --check: clean.

Why

#1166 produced a new immutable frontend bundle (map 281002ea) and Worker blob. The deploy workflow only publishes explicitly registered sources, so this source must be registered before the already-authorized S2 console publish.

Risk

• Tier: release workflow registration (CI/deploy path). Only an exact, pinned main-history source is added, and every other source path is unchanged.
• No Secret or profile sync, no new permission, no migration (the publisher still rejects candidate migrations) and no change to write routes.
• Merging this does not deploy anything. A deploy still needs a separate manual workflow_dispatch with this exact source_sha.

[chatgpt-codex-connector]

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-14T04:08:23.089797Z	050cad3	Draft marked ready
🔒 Security Review	✅ Completed 2026-11-14T04:10:24.619115Z	050cad3	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.